This really isn't a Slack issue, so much as a LILO issue, but here goes. I'm trying to set up Lilo to boot to Linux by default (the system in dual boot with Win98 and Slack 9.1. LILO works fine, but it won't boot to Linux by default. I've added "default=Linux" just before the "prompt" line and "lba32" (but I'm not sure it's in the right place. I've run LILO after every change I've made, but with no luck. I had it booting to Linux by default on a previous installation, but my notes on what I did are woefully sketchy. Below is my lilo.conf. If someone could just take a look to see if I missed something, I'd be grateful. I do a lot of web design (with Quanta Plus!) and I know that sometimes it takes an objective view to find the little things that may have been missed.

Thanks for your assistance.

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda3
message = /boot/boot_message.txt
lba32
default = Linux
prompt
timeout = "1200"
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
label = Dos
table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends

Reverse the order in which you have the Linux and Windows entries in Lilo.conf.

Thusand that should mean that Linux boots first. (oh, and don't forget to run lilo before the reboot)

- or -
you could specify
in lilo.conf, then run 'lilo' as root.

Thanks, people. Unfortunately none of those suggestions seem to do it. I don't know what the problem is. It's almost like there are two distinct lilo.conf files and I'm editing the wrong one. I know this is impossible (?), but I've seen it happen with web pages before. I struggle to fix a page and realize the browser is viewing an unedited backup or something. This is why I wanted a second opinion. It's almost maddening. Fortunately for me, I'm already mad. One thing of note is that I changed the label on the "DOS" drive to "Windows98." When I run LILO, it displays "Added Linux *" "Added Windows98", so something's getting through. I'm stumped. There's got to be something up with my previously posted lilo.conf, but damned if I know what.

you'll have to set : boot=/dev/hda
otherwise it will be installed in the bootblock of hda3 instead of the mbr.

egag

I think your right "egag"

Also I think the default should be above the boot:
default = Linux
boot = /dev/hda

Otherwise I think lilo would execute the boot = /dev/hda3 before even getting to the label.

KC

Well, that was it. I knew it was something in the code. When I was prompted to install LILO, I drew a blank as to where I installed it the last time ("MBR (possibly dangerous)" sounds so ill-boding, I guess). Thanks, egag, and everyone else ,too. This forum has once again saved my sanity (oh ... wait... too late for that). All is well with my (computer) world once again. Forums rock! You people rock!

ok

egag