-=> WAYNE CHIRNSIDE wrote to TOM WALKER <=-

-> KH>Wayne, try an FDISK replacement called AEFDISK. Using it, I was able to
-> KH>get an older drive recognized (delete/remake MBR) after utilities like
-> KH>"Zap" and "Wipe" and "Debug"
failed to recognize it. It's shareware, but
-> KH>only a couple of quite esoteric functions (batch setups, etc.) are
-> KH>disabled. It should come up quickly in Google, but, if it doesn't, I
-> KH>could email you a copy (it's tiny, and puts FDISK to shame). For my last
-> KH>few setups, it's been my partition table tool of choice.

-> And just HOW does he get that one Included on his HP OEM Install CD so
-> it wil be Used instead of teh MS version of FDISK?????

WC> Heh.
WC> That one I'd like an answer to.
WC> MicroSloth has lost me as a user precisely for their monoplistic and
WC> paranoid activation schemes.

WC> Why must they overwrite the MBR to install their software?

For the same reason Linux takes control of the MBR. When you install
any operating system, the programers expect total control. They expect
it to be /dev/hda (C:\). Although the MBR is screwed because the disk 
is unreadable it doesn't mean the BIOS can't see it. It just can't 
boot it.  

L8r. ;)


--- MultiMail/Linux v0.46