LILO and Slackware 7.1

[*Lo*Tek*]

I have encountered this problem even when I was still using Slackware 4.0...

During the Linux install process, it asks the user where LILO would be loaded... usually, I select the option to load LILO in the MBR... Later on, if I wanted to remove LILO, I would just call "fdisk /mbr" in Win9x, and LILO is gone... I've tried it with Red Hat and Mandrake, and I haven't encountered any problems with it...

However, when I'm using Slackware, after calling "fdisk /mbr", my system would not boot anymore to Win9x and it appears that the partition table was trashed...

has anyone out there encountered this same thing? what could be its cause?

thanks in advance!

[WeDeliver]

Yes, if you fdisk the mbr, you destroy Windows boot record as well. I have, however, blown away LILO and it still booted to Windows, I cannot explain.

[ansivirus]

The reason for this is the Lilo install via Slackware must "WRITE" the MBR in a different than normal format. the "fdisk /mbr" command in Windows attempts to rebuild the mbr... all it does is write a generic mbr... If the MBR was all fubared to begin with fdisk /mbr will not know a generic mbr for it and not do anything productive.. That is why you would have that problem.

-ansivirus