grub maybe causing kernel boot problems?

[Guest augustwest]

i have these partitions (in this order) on my notebook, ntfs, exteded[fat32, rieserfs, swap, rieserfs] and grub in the mbr. when i added the fat32 i of course had to change all of the numbers and such for grub. my original mandrake kernel 2.4.19-16mdk is booting fine. i want to use a 2.4.20-rc2-ac3 but cant get it too boot that prolly is another post entirely. anyway the menu.lst lines i am posting below is the one in question.

 

i18n (hd0,5)/boot/grub/messages

keytable (hd0,5)/boot/us.klt

 

they did look like this after installation, i didnt change them after i added the fat32 part, but everything worked fine.

 

i18n (hd0,4)/boot/grub/messages

keytable (hd0,4)/boot/us.klt

 

i recently just changed them but there was no effect. i changed them trying to get my new kernel to boot. getting a bit desperate. what should those lines look like?

[bvc]

Here's what mine looks like

timeout 3

#color black/cyan yellow/cyan

color light-gray/blue red/blue

i18n (hd0,5)/boot/grub/messages

keytable (hd0,5)/boot/us.klt

default 4

 

title linux

kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 devfs=mount hdd=ide-scsi quiet vga=788

initrd (hd0,5)/boot/initrd.img

 

title failsafe

kernel (hd0,5)/boot/vmlinuz-2.4.19-16 root=/dev/hda6 devfs=nomount hdd=ide-scsi failsafe vga=788

initrd (hd0,5)/boot/initrd-2.4.19-16.img

 

title win98

root (hd0,0)

unhide (hd0,0)

hide (hd1,1)

makeactive

chainloader +1

 

title Game

root (hd1,1)

#rootnoverify (hd0,0)

unhide (hd1,1)

hide (hd0,0)

map (hd0) (hd1)

map (hd1) (hd0)

makeactive

chainloader +1

 

title My9.0

kernel (hd0,5)/boot/vmlinuz-2.4.19-16 root=/dev/hda6 devfs=mount hdd=ide-scsi quiet vga=788

initrd (hd0,5)/boot/initrd-2.4.19-16.img

 

title floppy

root (fd0)

chainloader +1

Notice the "My9.0" points to a diff kernel(vmlinuz-2.4.19-16) unlike the default "linux" which points to vmlinuz which is a symlink to 2.4.19-16mdk in /boot.

 

I'm not exactly sure what you're asking.