How to remove LILO from mbr

[Glp1del]

I was having problems using Lizard to install Caldera OpenLinux 2.2, because my system has a V3 video card (Resolution problem) so I decided to try the LISA installation program. Somehow I put LILO in the MBR. How do I remove that from there so that the system will boot. Also, I can no longer use fdisk to remove the partions from the d drive where linux is suppose to go. Partiion magic (Caldera version) also cannot remove the partions from that drive.

Thanks in advance

Glp1del

[Geoff]

fdisk /mbr will remove LILO from the master boot record.

Why can't you remove the partitions? I can't see any reason why a partition would be "locked" in place, you can *always* delete a partition if you really want to http://discussions.linuxplanet.com//wink.gif

Caldera probably won't let you remove them because they're already mounted. Now that I think about it, maybe Caldera has set the linux partition bootable. In that case go into fdisk and set the active partition to your normal C:\ (the one that windows boots off). If the linux partition is the "active" or "bootable" partition and you change it then you might not need fdisk /mbr either (if the situation is what I just described then fdisk /mbr won't do anything anyway!)

[Glp1del]

The problem with Fdisk was that it would not open. I would type fdisk from the c:/windows prompt and it would just hang. I fixed it by trying to install linux again with LISA. At one point it allows you to repartition the HDD. At this point I could use Fdisk to remove the linux partitions. I then rebooted the system and did Fdisk /mbr and now things are fixed. Well almost still cannot load working version of linux onto the system, but still working at it.

BTW is it normal for the install to read parport_pc FAIL during first linux boot up??

Glp1del

[Cable]

You cannot run FDISK from inside Windows, FDISK needs exclusive access to the hard drive.

Two things to get around this:

#1 Use MS-DOS Mode, then run FDISK

#2 Boot off an Emergancy Startup Disk that gets to an A: prompt then run FDISK from that startup disk

[Glp1del]

In essence, by re-installing I was running off of a boot disk and at that point Fdisk did work properly. I did not know that about running fdisk from inside of windows.

Thanks,

Glp1del