Lilo 99 Error, again. [RESOLVED]
 

Here's the deal, I've got winxp on my first drive, and on my second drive I have one ntfs partition, one linux partition and one swap partition.
I just finished installing Slack onto the linux partition and when I try to boot it gives me the lilo 99 error.
I'll post my lilo.conf in a minute.

To reiterate:
/dev/hda1 = WinXP
/dev/hdb1 = NTFS
/dev/hdb2 = Linux
/dev/hdb3 = Linux Swap
Thanks in advance

boot from the install cd and install LILO again...99 is an error that it didn't totally install.

You sure I need to reinstall the package?
I've reinstalled Lilo from the command line several times now.

Not the package, run lilo (just type: lilo), I guess he meant to reinstall it to MBR.
You could also run liloconfig again, choose Expert mode and install to MBR.

When booting from cd, on lilo's prompt ( where it says boot: ) use: Linux root=/dev/hdb2 and it will boot into your installed system. If you used another kernel than default (bare.i) instead of typing Linux type the name of the kernel.

Been many years since I last used lilo, but I thought L99 (presuming that's what you mean) was a geometry problem.
What does "fdisk -l" show ??.

Didn't work. Same problem.
As a note, when I run lilo it gives me a warning that the table is on a different disk. Anyone else had a problem with Winxp on one harddrive and slack on the other?

i have xp on one hd, and all my linux distros on the second, so i know it can work...but it's been awhile since i used LILO, cuz i always had problems with it. i use grub and it works flawlessly for me....you might wanna try that? i think it's in the extras on disc 3, or you can get it from here...

grub has never failed me, and i install it to the mbr.

Silly me, I hadn't checked to see if Lilo was writing to hda1's mbr.
Fixed

congrats!!! it's the little things that mess us up :)

There is a bug in lilo that if you have a USB drive mounted as /dev/sdax it thinks you are trying to install to this drive EVEN when you say lilo -v -b /dev/hda

I think it has to do with a limitation that lilo will only write to the MBR of the first drive it sees, no matter what you tell it!

If you have a USB key plugged in while you're trying to lilo, take it out, reboot, and do lilo again.

This bug may be the reason why so many people are reporting that lilo fails to install to the MBR. It may also be that lilo is getting confused with multiple HDs. I can't test this because I have only one drive. Just make sure you are giving lilo the right drive specification.