Had a NAM II v3.0 copper with a hard drive that was starting to make some pre-dying sounds, everything was still working fine though. Decided to ghost the drive onto a spare drive that I had laying around the shop (working pull from a NAM II v3.0 fiber that was upgraded to 4.0 ... exact same model of drive) before it decided to die completely. Did a backup of the sekur file and then proceeded to image... unfortunately I went the wrong way around and copied the fiber NAM drive over onto the copper one. Figured there should not be an issue (aside from having to redo all the prompts) so tried to boot up. Boots ok all the way into OS/2, but the voicemail never seemed to initialize. Then remembered to copy the backed- up sekur file back into the system... but still no initialization. Took a closer look while the system is booting and the DVC drivers seem to get loaded ok, with the exception of one (the 3rd of 4 I believe) which gives the following error "D/xxx Device Driver version 2.22 VOXB0 Board type does not match config file". I did not have a monitor connected to the system when it was working, so I don't know if that error is the problem, or if it is "normal" to get that error (for what it's worth I have tried putting a NAM V4 drive, [also out of a fiber NAM] in the system and do get the same error).
I don't believe there should be an issue between fiber/copper drives, because they ship with both sets of drivers enabled... but if that really is the case I'm at a total loss to figure out why it's not working.
Anyway, that's the background... anybody have any ideas? Could it somehow be a keycoding issue, even though I have restored the old capabilities file?
Cheers,
>>>>> Mike <<<<<
P.S. Important rule #1... when copying data between two drives (especially two that look/are identical), put a big brightly colored label on the one you don't want to overwrite
I don't believe there should be an issue between fiber/copper drives, because they ship with both sets of drivers enabled... but if that really is the case I'm at a total loss to figure out why it's not working.
Anyway, that's the background... anybody have any ideas? Could it somehow be a keycoding issue, even though I have restored the old capabilities file?
Cheers,
>>>>> Mike <<<<<
P.S. Important rule #1... when copying data between two drives (especially two that look/are identical), put a big brightly colored label on the one you don't want to overwrite
