LILO deletion??

Psyco26 · 01-04-2007, 04:34 PM

Hi im just trying to delete the LILO conf because i want to reinstall slacks, but the thing is after deleting, the swap and linux from /dev/sda2 and /dev/sd3 and reboot I still get to choose how to boot, on /dev/sda1 ive got Win xp installed, if that helps you, ive tried to do fdisk /mbr when booting with the slacks cd but get Unable to open /mbr, gratefull for all help, or if you need more feedback please dont hesitate and i will post anything needed.

stress_junkie · 01-04-2007, 05:05 PM

There is no need to get rid of LILO on the hd MBR. Just reinstall Slackware or any other operating system. It will take care of the boot loader during the installation.

Psyco26 · 01-04-2007, 05:08 PM

Thank m8 will try it out....

Psyco26 · 01-05-2007, 07:27 AM

Nope that dosent work, when I get the Slacks and windows to choose between on boot, it crashes in the middle telling me the kernel is not correct or something, well anyways it dosent work, and lets say i wanted to try some other dist that dosent run under LILO just GRUB still wanna know how to delete the lilo conf from the mbr, thx again for all help.

malo_umoran · 01-05-2007, 08:13 AM

check "man lilo" ... there is everything you need to uninstall lilo.

M.

onebuck · 01-05-2007, 08:16 AM

Quote:

Originally Posted by Psyco26

Nope that dosent work, when I get the Slacks and windows to choose between on boot, it crashes in the middle telling me the kernel is not correct or something, well anyways it dosent work, and lets say i wanted to try some other dist that dosent run under LILO just GRUB still wanna know how to delete the lilo conf from the mbr, thx again for all help.

Hi,

If you want to just get rid of the lilo bootloader and restore to the ntloader for windows then you can use the the windows fixmbr.

This command is only available from the recovery console for windows xp.

If you want to rewrite a new lilo to the mbr then use the install cd to boot. Then edit your /etc/lilo.conf after mounting the installed system you wish to work on. If you want to write the lilo for the said system, just chroot to that system and do your lilo command.

Psyco26 · 01-05-2007, 08:35 AM

Yes but the problem is i messed up and deleted both sda2 and sda3 that were for the linux and linux swap, and only have the sda1 partition left for windows, and ive tried to rewrite the fixmbr from the restore win cd, but then i still get slack and windows to boot from, really weird i have to say....

stress_junkie · 01-05-2007, 10:08 AM

Does your motherboard have "Protect boot sector" turned on in BIOS CMOS?

Psyco26 · 01-05-2007, 11:18 AM

That was a good question i will have to check, guess i have dual bios if im not mistaken, will check and get back to you... thx again.

onebuck · 01-06-2007, 08:16 AM

Quote:

Originally Posted by Psyco26

Yes but the problem is i messed up and deleted both sda2 and sda3 that were for the linux and linux swap, and only have the sda1 partition left for windows, and ive tried to rewrite the fixmbr from the restore win cd, but then i still get slack and windows to boot from, really weird i have to say....

Hi,

This changes everything. You can always re-install the linux. Create the new partitions and install slackware again. You will then write to the MBR during the install.

stress_junkie · 01-06-2007, 08:49 AM

Quote:

Originally Posted by gwsandvik

Hi,

This changes everything. You can always re-install the linux. Create the new partitions and install slackware again. You will then write to the MBR during the install.

That's what I said in the first response to this thread. He responded by saying that the system appeared to act the same at boot time after the Linux install as though the MBR had not changed. I have seen that behavior on systems that can truly protect the MBR of the first hard disk when the motherboard is set to "Enable virus protection" or "Protect boot sector" or whatever the option may be called on any given motherboard.

onebuck · 01-06-2007, 11:16 AM

Quote:

Originally Posted by stress_junkie

That's what I said in the first response to this thread. He responded by saying that the system appeared to act the same at boot time after the Linux install as though the MBR had not changed. I have seen that behavior on systems that can truly protect the MBR of the first hard disk when the motherboard is set to "Enable virus protection" or "Protect boot sector" or whatever the option may be called on any given motherboard.

Hi,

I missed that since I responded via the link on email.

The other thought is that the partitions could be there still. The OP could use ranish or any other disk editor to see this. If the OP had logged the table or fdisk -l output then the recovery could be possible. Worth a try unless OP resized the winxp partition. The space would be there until partitioned again or written too.