M
Martin
I have just replaced my primary slave drive, which I use for file backups
and drive images, with a higher capacity drive, and now can't run Drive
Image. With the old, smaller drive there is no problem. I get 2 error
messages with the new one: " #91 - Disk Manager detected on Drive 1, but is
not running.", and " #87 - Unable to initialize the engine." Neither of
these is listed in the Drive Image help files.
I haven't been able to find anything I can recognize as Disk Manager on
drive 1, the primary master; whether it's running or not, or how it ties
in with the Drive Image program. No help from Powerquest because it's an
old version. I downloaded a utility called ezsig.exe that I think was
supposed to correct the problem, but it didn't.
Any ideas on why the new, larger drive has this problem when the old one
doesn't, and any suggested fixes would be appreciated.
Marty
and drive images, with a higher capacity drive, and now can't run Drive
Image. With the old, smaller drive there is no problem. I get 2 error
messages with the new one: " #91 - Disk Manager detected on Drive 1, but is
not running.", and " #87 - Unable to initialize the engine." Neither of
these is listed in the Drive Image help files.
I haven't been able to find anything I can recognize as Disk Manager on
drive 1, the primary master; whether it's running or not, or how it ties
in with the Drive Image program. No help from Powerquest because it's an
old version. I downloaded a utility called ezsig.exe that I think was
supposed to correct the problem, but it didn't.
Any ideas on why the new, larger drive has this problem when the old one
doesn't, and any suggested fixes would be appreciated.
Marty