I am having a difficult time understanding your writing.
You mention that something failed when installing the LILO bootloader. If, for instance, the floppy was write protected or there was an input/output error while writing to the floppy (a very common occurrence), the loader on the floppy may be unusable. Some Linux installers will give you multiple chances to write the floppy to allow changing the disc, adjusting the write protection or making multiple copies. In this case, I would recommend using a generic rescue floppy or CD to boot your system and then to run lilo again to write another boot floppy.
There is such a rescue floppy on your Slackware CD:
http://ftp.heanet.ie/mirrors/ftp.sla...cue.dsk.README
http://ftp.heanet.ie/mirrors/ftp.sla...sks/rescue.dsk
http://slackware.com/book/index.php?...1710.html#LILO gives information on LILO and how to configure it.
http://slackware.com/book/index.php?source=x1776.html
The rescue floppy should have the chroot command on it which allows you to boot from the floppy and run your system to do the repairs.
http://developer.ezaurus.com/slj/doc...ds/busybox.asp Has the list of commands
<blockquote]
chroot
chroot NEWROOT [COMMAND...]
Run COMMAND with root directory set to NEWROOT.
Example:
$ ls -l /bin/ls
lrwxrwxrwx 1 root root 12 Apr 13 00:46 /bin/ls -> /BusyBox
$ mount /dev/hdc1 /mnt -t minix
$ chroot /mnt
$ ls -l /bin/ls
-rwxr-xr-x 1 root root 40816 Feb 5 07:45 /bin/ls*
[/blockquote]
You would, of course, use your own /dev/hdwhatever instead of /dev/hdc1 and the minix would be ext2, most likely. Once the chroot comand has been issued, you are running your system. You can edit /etc/lilo.conf and run /sbin/lilo or run /usr/bin/liloconfig
I hope this helps.