Reset MBR to non-boot status

  • Thread starter Thread starter Don
  • Start date Start date
D

Don

I have a 320gig disk drive with that had a Linux distro on it. I did a
comprehensive Windows 7 NTFS format thinking it world rewrite the MBR
because I want to use it as a data diak. But it still looking for the
GRUB2 boot loader. How can I fix this so the disk is non-bootable? Any
software out there to make this task easier?

Appreciate any assistance you can give.
 
Don said:
I have a 320gig disk drive with that had a Linux distro on it. I did a
comprehensive Windows 7 NTFS format thinking it world rewrite the MBR
because I want to use it as a data diak. But it still looking for the
GRUB2 boot loader. How can I fix this so the disk is non-bootable? Any
software out there to make this task easier?

Appreciate any assistance you can give.

I don't have a Windows install disk like this article describes, so I
can't confirm the Windows Installer/ Repair your computer/ Repair
console/ Command prompt - bootrec.exe /fixmbr

http://www.ehow.com/how_7809500_clear-master-boot-record.html How to
Clear a Master Boot Record

There is another much longer article that tells why to not use fdisk /mbr

http://www.cknow.com/cms/vtutor/fdisk-mbr.html FDISK /MBR is often
suggested as a solution for fixing a virus attack. The simple advice
is: Just Don't Do It!


There are other articles discussing fixmbr, linux tools, and super fdisk.
 
I have a 320gig disk drive with that had a Linux distro on it. I did a
comprehensive Windows 7 NTFS format thinking it world rewrite the MBR
because I want to use it as a data diak. But it still looking for the
GRUB2 boot loader. How can I fix this so the disk is non-bootable? Any
software out there to make this task easier?

Appreciate any assistance you can give.

I use exclusively an old DOS boot CD with FDISK /MBR. But my choice
of arbitration is SBM - Smart Boot Manager 3.7.1 --

http://btmgr.sourceforge.net/

I pulled its primary executable (may require compilation otherwise),
along with a DPMI memory access utility to first run if it reports
back with a runtime error, from the last of the olden DOS-based HIREN
discs series.

All a bit dated and harder to find among minor convolutions into the
world of computing, although given limited resources and options
presented in a commercial arena outside a dedicated following for
*NIX, I wouldn't have it any other way.

Invariably SBM treats me right, but viruses and rootkits don't scare
me because I wouldn't touch anything with your 10' pole I first
haven't tested, researched, and ultimately trust. (It's usually
hardware advances and supportive interfaces that drive a nail into
those coffins.)
 
Back
Top