I don't know if this will help or not, but here it is anyway.. When I first mess around with multi boot, I mucked up the MBR as well.
One solution was to boot up the system with a DOS bootup disk, and runt "fdisk /mbr". That will put DOS back in control however. Use this method if you use loadlin to boot up Linux from DOS. The other solution that I know of is to boot the system up with a Linux boot up disk (do you see a patern here?). Then fix up /etc/lilo.conf or whatever else you need for the system to boot and then run /sbin/lilo, and hopefully everything will be sweet. I don't think that reinstalling is necessary for messing up the MBR. MB. Lane Lester [EMAIL PROTECTED] wrote: > For several hours I've been without a system that would boot to any > OS. My goal was to move Corel Linux's lilo from the MBR to its boot > partition so that I could add Debian and control everything with Win > NT's boot manager. > > I thought I had a procedure figured out that would work... I was > wrong. I won't bore you with a procedure that didn't work; suffice it > to say that I was left with a system that, at boot time, would just > stream "0x01" continuously up the screen. > > I reinstalled Windows NT in hopes of restoring the MBR (MBR) where I > figured the problem was. I hadn't used NT in so long that there would > be no loss in reinstalling. But that didn't fix the problem; I still > couldn't boot. > > So I bit the bullet and reinstalled Corel Linux from scratch, and at > least now I can run both it and Win 98 again. But that leaves me once > again under the domination of Corel Linux's lilo with no way to add > another Linux.
