LILO "99" problem

**marachon** · 01-10-2004, 12:42 AM

I receive this error when my BIOS autodetects my disk drives. If I manually detect the drives and save them, I no longer get L 99 99 99...

**Snaps** · 01-10-2004, 04:52 PM

I'm new to this, so I don't know how to change the translation to LBA or manually detect drives... I've got win xp pro and mandrake 9.2 on 2 different hdd using LILO to boot. The HDD are set as master and are on primary IDE channels (I have 4). Any follow-up would be greatly appreciated!

**Lazarus** · 04-13-2004, 11:45 PM

Originally Posted by Snaps

I'm new to this, so I don't know how to change the translation to LBA or manually detect drives... I've got win xp pro and mandrake 9.2 on 2 different hdd using LILO to boot. The HDD are set as master and are on primary IDE channels (I have 4). Any follow-up would be greatly appreciated!

To fix the L 99 99 99... all you need to do is change your mbr boot sector to the partition/drive with windows, or to the boot loader you are using. If you run, for say, the windows 98 cd and boot to dos and run fdisk /mbr and set it to the boot loader drive then everything will work fine. You can also use a system boot disk that has dos and fdisk on it.

**DimGR** · 04-14-2004, 04:10 AM

Originally Posted by Wylkroe

I managed to fix my lilo 99 problem by downloading the 1st debian ISO image made a disk and booted to it typed linux and it brought me to the beggining configuration to install linux. As it ran me through the opitions I told it to accept the existing partitions swap etc... then it took me to the LILO configuration it reconfigured LILO with the OS's on my system including my knoppix HD install. Took the CD out and rebooted Lilo appeared with both my WinXP install and Linux.

Without the L 99 99 99 99 99 99 99 99 99. Phew. As for how to fix lilo without the Debian CD I do not know I am just a newbie. Just be careful when it comes to the Partition part you want to use your existing partitions "DO NOT ERASE AND RECREATE THEM!"

the 999999999999999999 error means that your windows MBR was overwritten or deleted. Simply using the recovery console from a windows CD type fixmbr

**fgrep** · 05-07-2004, 09:42 PM

The "lilo 99" problem occurs, wen mbr damaged.
this often happens if you set the main disk to a partition not the device.

so if you set in lilo.conf somthing like boot=/dev/hda6 you'll get this error.
set boot=/dev/hda instead and run lilo again
or run lilo with -M /dev/hda with same effect.

fgrep