Maxtor HDD and Drive Image 2002: error 91.

[blade0r]

Hello everybody,
I recently purchased a 120 GB Maxtor HDD to use it in combination with my
actual Western Digital one.
The WD disk has got two partitions, C: (containing the OS) and E: (this is
an extended partition).
The new Maxtor disk only contains one primary partition, D:.
Both of the disks are connected to the primary IDE channel (the WD one as
master and the Maxtor one as slave).
I partitioned and formatted the Maxtor HDD using MaxBlast 3, which - I read
on Google - can represent a problem, if it installs the DDO.
So, following the suggestions read in other groups, I booted the PC using
the MaxBlast 3 CD and I examined the current partition.
I discovered the DDO is not currently installed onto my HDD, in fact the
option is greyed out on the MaxBlast 3 panel.
By the way, the program returns me that error anyhow, even if I boot the
computer using the Drive Image 2002 floppy disks.
If MaxBlast 3 didn't install the DDO, I wonder why does Drive Image show
that error message.
Is there a way to fix the issue without having to repartition and reformat
the HDD?
Best regards.

 

[Joep]

fdisk/mbr or fdisk/cmbr n, where n is disk number if the signature is not on
first disk. MBRtool from www.diydatarecovery.nl can be used to back up the
mbr prior to modifying it with Fdisk.

 

[blade0r]

fdisk/mbr or fdisk/cmbr n, where n is disk number if the signature is
not on first disk. MBRtool from www.diydatarecovery.nl can be used to
back up the mbr prior to modifying it with Fdisk.

Hello Joep,
thank you so much for your reply.
I guessed FDISK was not compatible with NTFS formatted disks or was I wrong?
What's the difference between the first and the second switch?
Best regards.

 

[Joep]

Hi,

Fdisk/mbr or /cmbr doesn't have anything to do with NTFS, FAT or whatever,
it strictly modifies the MBR

Fdisk/mbr -> re-writes boot code in MBR on physical drive 80h

Fdisk/cmbr n -> allows you to specify a physical on which operation should
be performed, where n is the drive (count zero based). So for example to
rewrite boot code on the 3rd physical hard disk: fdisk /cmbr 3 [enter]

Kind regards,
Joep

--
D I Y D a t a R e c o v e r y . N L - Data & Disaster Recovery Tools

http://www.diydatarecovery.nl
http://www.diydatarecovery.com

Please include previous correspondence!

DiskPatch - MBR, Partition, boot sector repair and recovery.
iRecover - FAT, FAT32 and NTFS data recovery.
MBRtool - Freeware MBR backup and restore.

 

[blade0r]

Hi,

Fdisk/mbr or /cmbr doesn't have anything to do with NTFS, FAT or
whatever, it strictly modifies the MBR

Fdisk/mbr -> re-writes boot code in MBR on physical drive 80h

Fdisk/cmbr n -> allows you to specify a physical on which operation
should be performed, where n is the drive (count zero based). So for
example to rewrite boot code on the 3rd physical hard disk: fdisk
/cmbr 3 [enter]

Kind regards,
Joep

Joep, I don't really know how to thank you.
I really appreciate your suggestions.
I have one last question: is this operation intrusive or not?
In other words, is it simply advisable or necessary to back-up the data on
the HDD?
Do you know where I can get the latest FDISK version?
Thank you for your time.
Best regards.

 

[Joep]

--
D I Y D a t a R e c o v e r y . N L - Data & Disaster Recovery Tools

http://www.diydatarecovery.nl
http://www.diydatarecovery.com

Please include previous correspondence!

DiskPatch - MBR, Partition, boot sector repair and recovery.
iRecover - FAT, FAT32 and NTFS data recovery.
MBRtool - Freeware MBR backup and restore.

Hi,

Fdisk/mbr or /cmbr doesn't have anything to do with NTFS, FAT or
whatever, it strictly modifies the MBR

Fdisk/mbr -> re-writes boot code in MBR on physical drive 80h

Fdisk/cmbr n -> allows you to specify a physical on which operation
should be performed, where n is the drive (count zero based). So for
example to rewrite boot code on the 3rd physical hard disk: fdisk
/cmbr 3 [enter]

Kind regards,
Joep

Joep, I don't really know how to thank you.
I really appreciate your suggestions.
I have one last question: is this operation intrusive or not?

In other words, is it simply advisable or necessary to back-up the data on
the HDD?

I'd always suggest to backup the MBR first, MBRtool from our website
(www.diydatarecovery.nl) can be used to accomplish this.

Do you know where I can get the latest FDISK version?

Any win98 rescue diskette will do (www.bootdisk.com has loads). BTW, MBRtool
can also refresh the boot code (like fdisk/mbr & fdisk /cmbr)

 

[blade0r]

Thank you once again, Joep.
There's only one thing that I didn't understand: you said the number of the
drive is count zero based.
That means I have to substitute the 'n' with 1 for the first drive, 2 for
the second and so on.
How do I make myself sure the drive I need to fix is the second one?
Because it's configured as slave on the first IDE channel?
So, do I assume the master is drive number 1?
Best regards.

 

[Joep]

My mistake .. it is one based (Fdisk /cmbr).

MBRtool is zero based.

 

[blade0r]

My mistake .. it is one based (Fdisk /cmbr).

MBRtool is zero based.

So, the first disk is 1 with FDISK and 0 with MBRtool, is that right?
Moreover, how do I know if the HDD I need to repair is actually # 1 or 2?
Best regards and thank you for your professional support.