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.

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

Martin wrote:
> 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.
>
> 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

There is another thread regarding this topic.
Read it below, because Joep suggested a possible way to fix the issue.
I didn't try his solution yet, because I don't have access to my PC.
Good luck.

--
Preferirei essere chiamato genio di male...