[GLLUG] LILO.conf help?

[impact]

I'm trying to get multiple Linux distros installed so I can play with 
them/learn more.  However I'm having some trouble getting my lilo.conf 
to play nicely.
I really dont know where to start to explain.
I have Mandrake 10 Official installed.  Decided to add a Slackware 10 as 
another option.  I booted the Slackware install, installed it, 
everything went fine.  Installed lilo to the root partition of Slackware 
(because I already had one for Mandrake, and figured I'd just edit that 
one).  The entire time I was installing Slackware, I was referencing my 
HD as hdd, during the slackware install, my drives were:
hda = cdrom
hdb1 = swap partition
hdb2 = storage folder (/shared)
hdc1 = /home (shared between distros)
hdd1 = /boot (from mandrake, was sharing... bad idea?)
hdd3 = / (for slackware)
hdd5 = unmounted (/ for mandrake)
However when I booted back into Mandrake to edit my /etc/lilo.conf, all 
the HDs were odd... Mandrake and lilo.conf were referencing them as hde, 
hdf, hdg, hdh (a 4 letter shift?)
Here is my original /etc/lilo.conf:
# File generated by DrakX/drakboot
# WARNING: do not forget to run lilo after modifying this file

boot=/dev/hdf
map=/boot/map
default="linux"
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
disk=/dev/hdf bios=0x80
image=/boot/vmlinuz
    label="linux"
    root=/dev/hdh5
    initrd=/boot/initrd.img
    append="devfs=mount acpi=ht resume=/dev/hdf1 splash=silent"
    vga=788
    read-only
image=/boot/vmlinuz
    label="linux-nonfb"
    root=/dev/hdh5
    initrd=/boot/initrd.img
    append="devfs=mount acpi=ht resume=/dev/hdf1"
    read-only
image=/boot/vmlinuz-2.6.3-7mdk
    label="263-7"
    root=/dev/hdh5
    initrd=/boot/initrd-2.6.3-7mdk.img
    append="devfs=mount acpi=ht resume=/dev/hdf1 splash=silent"
    read-only
image=/boot/vmlinuz
    label="failsafe"
    root=/dev/hdh5
    initrd=/boot/initrd.img
    append="failsafe acpi=ht resume=/dev/hdf1 devfs=nomount"
    read-only
--------------------------------------------
I figured I would leave it be, and add another image to it (for 
Slackware).. I added
image=/boot/vmlinuz
    label="slackware"
    root=/dev/hdh3
    read only
----------------------------------
using hdh3 (because everything else referenced it with an hdh with no 
problems.  I also changed the label of "linux" to "mandrake", and the 
default to "mandrake".  Well.. It wouldn't boot "mandrake" after that.  
Gave me a "Kernel Panick" and said it couldn't mount it.  However the 
other images (originals) worked fine, used the "263-7" to get back here 
to type up an email...

Anyone have any hints as to what im doing wrong?  Anyone see my problem?

Eagerly awaiting a response,
Dan Sherman