I have Lilo on slack 9.1. Its installed on the Root (hda5). & i use the the NT Loader to load the LILO Prompt.

I have compiled my kernel 2.6 & made an entry in the LILO.conf. Then I ran Lilo once & it gave me a msg
# added Linux *
DOS
new2.6

"new2.6 was the newer entry
Though it gave me the msg i still cant see any changes made to the LILO prompt in actuall.

No matter wot i do in my lilo.conf the Changes Dont Reflect on the LILO prompt.

Tell me what possibly can be Wrong

Thx

Can you post your lilo.conf and the output of "ls -al /boot/" ? Did you have this problem with the 2.4.22 kernel? Have you been able to successfully boot both partitions in the past?

Without seeing the config it appears that you have added the new kernel and also left the old one in there.

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi"
boot = /dev/hda5
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal

#other = /dev/hda1
# label = DOS
#table = /dev/hda
# DOS bootable partition config ends
# Linux bootable partition config begins

image = /boot/vmlinuz-acpi-2.4.22
root = /dev/hda5
label = Linux
read-only

image = /boot/2.6kern
root = /dev/hda5
label = neKernel
read-only


# Linux bootable partition config ends
--------------------------------------------------------------
U can see the "DOS" Portion Commented out on it. but to my Surprise it is Still Visible on the Prompt
when i run Lilo it Gives me

root@scavan1:~# lilo
Added Linux *
Added neKernel
---------------------------------
yeah i added the new Kernel & also left the Older one as an Option to LOAD if the New One Fails with a PAnic. nothing new in that====

the Point is no matter i do to my LILO.conf -- when i Run Lilo the Msg says Added but it never gets Reflected to the Original Boot Record of LILO

The lilo.conf that you listed, what is the full path for it? I wonder if you have 2 of them in different spots or varied names.

I just noticed you referring to LILO.conf. Lilo reads /etc/lilo.conf not /etc/LILO.conf.

lol -- i dont Disagree to ur assumption .. it Can be Possible.. this is the /etc/lilo.conf

Could the windows boot loader be loading a partition other than /dev/hda5. Do you have any other linux distros? I never have used the windows boot loader so can not help with that.

And I know it may be nitpicking, but you *are* running /sbin/lilo and not just lilo, right? Not sure if it matters ... I've always used /sbin/lilo and not had any problems .... just my $.02

lilo & /sbin/lilo is just exactly the smae. Still i have tried both-- just checked that there is no Place on My Slack where there is a lilo.conf other than the ONE /etc/lilo.conf

Can I see the soft links in /boot? Just gimme a "ls -al /boot/" and I'll be happy.

After running lilo did you make a 512 byte file and copy it to your windows partition and make sure the NT boot.ini file is pointing to the right file?

e.g.

# to copy file
dd if=/dev/hda5 of=/root/boot.lnx bs=512 count=1

#copy file to floppy
mcopy /root/boot.lnx a:

# then do the windows stuff


I've had better luck setting lilo.conf to boot from floppy, then copying the first 512 bytes from /dev/fd0, but it ought to work either way.

u Caught me there RIGHT my Freind -- the thing just dint Strike into my mind..
yeah i have to Rip the 512 bytes of the Boot sector again-- everytime i update LILO since im not using thge LILO image to boot & not the Actual lilo

Thx alot for Closing this Thread