I just reinstalled Slackware 9.1 and this time after configuring the bootloader, it says it had an error and I need to boot up with my boot disk until I get it figured out. Well, I don't see where it messed up. I asked it to install to the MBR just like before. My setup is /dev/hda1=WindowsXP(NTFTS), /dev/hdb1(NTFS, /dev/hdb2(linux swap), /dev/hdb3(ext2)

Here's my lilo.conf :

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb3
label = Slackware-2.4.22
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda
label = WindowsXP
table = /dev/hda1
# DOS bootable partition config ends

If you boot into your install now, does it still give you the error? Sometimes it goes away after you are out of the installer.
One obvious error is in the WindowsXP entry, other = /dev/hda should have the 1 on it
other = /dev/hda1 if that is the correct partition.

No, I only got the error during the initial install of Lilo while installing Slackware. Now I've messed around with it a bit and now it's skipping the Windows partition all together. At first it was booting right into Windows. Now it's booting right into Linux. Do you think I need to reinstall Lilo somehow?
Here's my lilo.conf now

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global sectionlba32
# Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/hda
#compact # faster, but won't work on all systems. prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x256 vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb3
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = WindowsXP
table = /dev/hda
# DOS bootable partition config ends

You need to remove the # on the timeout line. Then run lilo as root. The timeout will give you a chance to pick winblows or slack.

Actually, I just ran "liloconfig" and reinstalled on my root disk instead of my MBR. All is well now. But I see what you were talking about there, ringwraith. Oopsy.

Thanks guys!