PDA

View Full Version : Need To "clean" MBR


Bob
January 6th 04, 09:17 PM
I'm using Win XP Pro. I installed a PCI Contoller card,then
a third Maxtor hard drive using MaxBlast3. So far so
good,though the new disk is now listed in Comp Manag as the
0 disk,though the three partitions I created are in fact
listed as Disk3 Volume1 (J)...--etc for the other two.
This is all by way of background for the system boots
OK,with the exception that the first screen I see deals
with a Raid Configuration utility. I though the driver for
the controller card that I used was for for no Raid (there
was one for using a Raid config).
In any case this is my real problem. I use Drive Image
2002. It now fails giving me the following Error Message:
Error 91 Disk Manager has been detected on drive %lu. The
manager is not running.
The solution Powerquest suggests is as follows:
Solution: Error 91 Disk Manager has been detected on drive %lu

If you no longer need to use Disk Manager on your hard
drive, you can fix Error 91 by removing the Disk Manager
signature from the Master Boot Record (MBR). If you are not
sure whether you still need to use Disk Manager, contact
your hard drive manufacturer. They can tell you not only if
you still need Disk Manager, but also how to repair it. If
you determine it is all right to erase the Disk Manager
signature, perform the following:
1. Create a DOS boot diskette. (You can create a DOS boot
diskette by choosing the option to "copy system files" when
you format a floppy diskette under Windows 98.)
2. Copy the FDISK utility to the boot diskette. You can
find the FDISK.EXE file in the \Windows\Command directory
on any Windows 98 machine.
3. Copy the WRPROG utility to the boot diskette. Download
the WRPROG utility from
ftp://ftp.powerquest.com/pub/utilities/. Once you download
the file, unzip it and copy the unzipped file to the boot
diskette.
4. With the boot diskette inserted in the floppy drive,
boot your computer.
5. Use WRPROG to back up head 0. IMPORTANT! If the Disk
Manager signature is on a drive other than the primary
master, you must change the drive's jumpers to make the
drive the primary master. This is necessary because WRPROG
is only able to back up the first head of the primary
master drive. The correct command line syntax for using
WRPROG to back up head 0 is: WRPROG /bak head0.dat The
reason for backing up head 0 is to provide a way to restore
its data if you discover later that you still need Disk
Manager. The head0.dat file is written by default to the
location from which you launched WRPROG (in this case, the
boot diskette). You can edit or restore this file later, if
necessary. For information on restoring the backup file to
head 0, see PowerQuest Solution777.
6. Run FDISK with the CMBR switch to clean out the Disk
Manager signature from head 0 of the primary master drive.
The correct command line syntax is: FDISK /CMBR 1 NOTE: The
number 1 signifies the primary master drive.

Problem Description:
Error 91 Disk Manager has been detected on drive %lu
Error 91

I tried this,backed up the MBR with WRPROG but the FDISK
with the CMBR switch didn't seem to be effective. I really
don't understand the syntax line. What does "1 NOTE:"
actually refer to? I tried FDISK /CMBR 1 and just FDISK
/CMBR,to no effect.
I have also used the Win XP CD to boot to the Recov
Console and tried the fixmbr command. I got to the moment
of decision,but it warned me that if I could boot normally
(which I can) that this command could wipe out the
partitions and render the system unusable. I just couln't
pull the trigger.
I'm definately in an area that I don't fully understand
but it does seem clear that what I want to accomplish is to
CLEAN out the Raid or Disk Manager reference in my MBR.
remember the system boots but I can't use Drive Image which
I really depend on.
Whew--I think writing this may be harder than solving my
problem. Have I made myself clear? Please help.
Thanks

DILIP
January 6th 04, 09:17 PM
Hi

To clear the MBR, boot from the XP cd and go into the Recovery console
(Repair). In command prompt type the following

fixmbr (new master boot record creation)
fixboot (incase you get message cannot find ntldr)
bootcfg /rebuild (incase the boot.ini is damaged)

Alternatively, boot from a Win98 bootable floppy and type this

fdisk /mbr

--
Dilip

"Bob" > wrote in message
...
> I'm using Win XP Pro. I installed a PCI Contoller card,then
> a third Maxtor hard drive using MaxBlast3. So far so
> good,though the new disk is now listed in Comp Manag as the
> 0 disk,though the three partitions I created are in fact
> listed as Disk3 Volume1 (J)...--etc for the other two.
> This is all by way of background for the system boots
> OK,with the exception that the first screen I see deals
> with a Raid Configuration utility. I though the driver for
> the controller card that I used was for for no Raid (there
> was one for using a Raid config).
> In any case this is my real problem. I use Drive Image
> 2002. It now fails giving me the following Error Message:
> Error 91 Disk Manager has been detected on drive %lu. The
> manager is not running.
> The solution Powerquest suggests is as follows:
> Solution: Error 91 Disk Manager has been detected on drive %lu
>
> If you no longer need to use Disk Manager on your hard
> drive, you can fix Error 91 by removing the Disk Manager
> signature from the Master Boot Record (MBR). If you are not
> sure whether you still need to use Disk Manager, contact
> your hard drive manufacturer. They can tell you not only if
> you still need Disk Manager, but also how to repair it. If
> you determine it is all right to erase the Disk Manager
> signature, perform the following:
> 1. Create a DOS boot diskette. (You can create a DOS boot
> diskette by choosing the option to "copy system files" when
> you format a floppy diskette under Windows 98.)
> 2. Copy the FDISK utility to the boot diskette. You can
> find the FDISK.EXE file in the \Windows\Command directory
> on any Windows 98 machine.
> 3. Copy the WRPROG utility to the boot diskette. Download
> the WRPROG utility from
> ftp://ftp.powerquest.com/pub/utilities/. Once you download
> the file, unzip it and copy the unzipped file to the boot
> diskette.
> 4. With the boot diskette inserted in the floppy drive,
> boot your computer.
> 5. Use WRPROG to back up head 0. IMPORTANT! If the Disk
> Manager signature is on a drive other than the primary
> master, you must change the drive's jumpers to make the
> drive the primary master. This is necessary because WRPROG
> is only able to back up the first head of the primary
> master drive. The correct command line syntax for using
> WRPROG to back up head 0 is: WRPROG /bak head0.dat The
> reason for backing up head 0 is to provide a way to restore
> its data if you discover later that you still need Disk
> Manager. The head0.dat file is written by default to the
> location from which you launched WRPROG (in this case, the
> boot diskette). You can edit or restore this file later, if
> necessary. For information on restoring the backup file to
> head 0, see PowerQuest Solution777.
> 6. Run FDISK with the CMBR switch to clean out the Disk
> Manager signature from head 0 of the primary master drive.
> The correct command line syntax is: FDISK /CMBR 1 NOTE: The
> number 1 signifies the primary master drive.
>
> Problem Description:
> Error 91 Disk Manager has been detected on drive %lu
> Error 91
>
> I tried this,backed up the MBR with WRPROG but the FDISK
> with the CMBR switch didn't seem to be effective. I really
> don't understand the syntax line. What does "1 NOTE:"
> actually refer to? I tried FDISK /CMBR 1 and just FDISK
> /CMBR,to no effect.
> I have also used the Win XP CD to boot to the Recov
> Console and tried the fixmbr command. I got to the moment
> of decision,but it warned me that if I could boot normally
> (which I can) that this command could wipe out the
> partitions and render the system unusable. I just couln't
> pull the trigger.
> I'm definately in an area that I don't fully understand
> but it does seem clear that what I want to accomplish is to
> CLEAN out the Raid or Disk Manager reference in my MBR.
> remember the system boots but I can't use Drive Image which
> I really depend on.
> Whew--I think writing this may be harder than solving my
> problem. Have I made myself clear? Please help.
> Thanks
>

Google