Powerquest Drive Image 2002 fails due to inactive Maxtor "Disk Manager" or DDO

[Bob Alston]

My Powerquest Drive Image 2002 fails due to inactive Maxtor "Disk
Manager" or DDO software.

I recently installed a nice new Maxtor 160 gig drive as my slave
drive. All worked fine until I started to back it up using Drive
image 2002. It complained:
"Error #91..
Disk Manager has been detected on drive 1, but disk manager is not
running......

As it turns out, the Disk Manager is apparently Maxtor's DDO software
which allows older bioses to access large hard drives. My version of
DDO is apparently on the hard disk boot sector but is not active.
This caused Drive Image to choke and abort.

Preliminary looking at Powerquest site referred me to Maxtor's site
and vice versa.

Later I saw reference to a fix available from Powerquest - to fix a
similar problem with the prior version of Maxtor's disk manager
ezsiz.exe. Below is the post incase this fixes the problem for
someone else:
http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&th=f3a256abb9a88225&rnum=5


Finally I found this message thread
http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&th=f3a256abb9a88225&rnum=5
Which provided the fix.

What I needed to do was rewrite the MBR record code - not the
partition table on the new disk - not the boot disk. FDISK won't do
that.

But Symantec Ghost's GDISK apparently will -- and did.
Couldn't figure out how to download from Symantec but found it at:
http://www.drd.dyndns.org/index2.html
Click "software" at the upper right
then click on the topmost small "folder" icon at the left.

I downloaded it and then added the gdisk.exe program to a bootable
win98 diskette I had lying around.

When running it, run gdisk w/o parms. It will tell you what
disks you have installed. You have to be careful because sometimes
the 1st disk is disk 0 and at others it is disk 1. It showed I had
disk 1 and disk 2.
So gdisk 2 /mbr resolved my problem and left my partition
table intact.

If questions you can contact me at

bobalston9 AT aol DOT com

 

[CS]

On 26 Dec 2003 16:35:12 -0800, (e-mail address removed) (Bob Alston) wrote:

You could have done the same thing using fdisk.

Boot the machine with a Win98 EBD, from the
A:> prompt type in (no quotes)

"fdisk /mbr"

That re-writes the mbr and at the same time should remove any data
overlay writes such as Disk Manager or the Maxtor DDO.

The GDISK.EXE program does the same thing.

 

[Crusty \(-: Old B@stard :-\)]

The Maxtor crap is taking up the space that Drive Image 2002 need when it
reboots to do it's thing! They both can't reside there at the same time, yet
in this case, both must. One has to go.

Suggest you create the 2 floppy set for Drive Image 2002. Then boot from
floppy 1. Put in floppy 2 when it tells you to. Go from there. Works every
time.

 

[Guest]

DI 2000 is not for xp get DI 7

 

[Pavel]

Who said anything about DI 2000? If you mean DI 2002 then you are wrong
because DI 2002 was written for WindowsXP. The only difference between DI
2002 and DI 7 is that DI 7 can backup from Windows XP and is more secure
when it comes to restore. The downside to this security is that it takes for
ever to restore. None of the 3 minute restores I am used to with DI 2002

 

[Bob Alston]

Thanks for the input guys. Unfortunately:

1) Fdisk /mbr will fix the mbr only on the book drive. That mbr is
fine. It is the code in the MBR for the slave drive I have, which
does not boot.

2) Using the DI 2002 diskette set does not resolve the problem. Tried
that.

Again, what resolved the problem was replacing the MBR code - not the
partition table - on the SLAVE drive!!!!!!!

Bob