lilo after kernel update

[liubeto]

Hi everyone there, I`ve got a problem configuring /etc/lilo.conf after kernel update. I worked with default slackaware 11 kernel - 2.4.33.3, but I had a lot of problems with skype and decide to move to 2.6.17.13 kernel. I took it from the slacks dvd /extra folder. Everything went good, I added the new kernel in lilo.conf, but after rebooting I couldn`t boot windows (on /dev/hda1, lilo is install in mbr of /dev/hdb, linux is install in /dev/hdb2). I had tryed reinstalling lilo, unfortunately there wasn`t any change. Here is my lilo.conf :

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hdb
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x32k
vga = 790
# 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
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.33.3
root = /dev/hdb2
label = Linux-2.4.33.3
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
image = /boot/vmlinuz-generic-2.6.17.13
initrd = /boot/initrd.gz
root = /dev/hdb2
label = Linux-2.6.17.13
read-only

Hope someone can help me. Thanks in advance!

[rcgreen]

try changing boot=/dev/hdb to boot=/dev/hda

This will install LILO onto the Master boot record of the
primary master hard drive. By default, this is the drive that
the BIOS wants to boot from. Any other configuration
requires a workaround. I'm assuming that LILO is the only
bootloader.

[liubeto]

Ok, I forgot to say that everytime I want to boot using lilo, I change my BIOS boot order (first hdb, if you want lilo or just windows on hda mbr), I don`t think that if I install it on hda mbr it will work, because before kernel update everything was working. Today I found another solution, I try to point
other=/dev/hda
without the 1 , and It works, I think about the idea to write
other=/dev/hda0
I`m not sure, but I think this points to MBR of the hda, which is only windows(MBR) and works fine. Thanks for help.