Tried to install 9.2 today, alongside existing 9.1 and XP. (Wanted to check if modem drivers would work for 9.2, which they don't). Foolishly assumed I could install 9.2 onto some spare disk space (stole some of the XP partition), and modify LILO entries using MDK control centre to add boot option for 9.1

The result is that 9.2 works, and XP works, but 9.1 shows multiple errors and won't boot. The first problem was that the new partition for 9.2 had altered all the exisiting partition numbers, editing etc/fstab of 9.1 cured that.

Now it appears that every load step that calls up the kernel version fails, it seems to be looking for 9.2 kernel version modules, and obviously can't find them on the 9.1 partition.

I'm almost resigned to reloading 9.1, but if anybody could offer any pointers to sorting out this problem by less drastic means I would be very grateful.
Thanks,
Jerry

check out you lilo.conf in the 9.2 installation (I take it that this was used when installing lilo into the MBR). If the entry for 9.1 has a vmlinuz entry pointing to the 9.2 kernel, it won't work. Basically, all the entry for 9.1 have to consistent with each other. Vmlinuz pointing to the 9.1 kernel and the right root partition has to be specified.
If this is too vague, post your lilo.conf and the setup you have (separate boot partition(s)?)

Do you have a boot floppy for 9.1? I know that is not a solution but a
work around in case you need data off of 9.1. I have apparently done
something similar on my dual boot redhat9/mdk9.1 system. If I boot
RH9 from lilo, it will boot up but modprobe doesn't find modules.dep.
If I use my RH9 boot floppy everything is fine. Cat lilo.conf shows that my vmlinuz
entry is pointing to initrd-2.4.21-0.13 mdk.img. I messed it up when I edited
and ran lilo from mdk9.1. I haven't tried to fix it yet but it shouldn't be a problem.