This is a guess based on your description of what happens. It almost sounds like you may have, at one point, had this line in your lilo.conf file...
boot=/dev/hda1 ....and the rest of the file was the same as it is now. That would have installed lilo in the boot sector of /dev/hda1, and it may still be there, even though you have since installed Lilo in the MBR (/dev/hda). So when you choose win95, it turns things over to the Lilo boot sector in /dev/hda1 which then gives you the same menu. Linux would still boot normally in that case, but choosing win95 would keep looping you back to the same boot sector in /dev/hda1, and give you the menu again. Have you tried booting from a Win95 floppy disk and see if you can access that partition from a DOS prompt? Because if what I'm suggesting did happen, your Win95 boot record is overwritten with Lilo, and you won't be able to access your C drive. Actually, I hope I'm wrong for your sake. Tom Martin Waller wrote: > > Help me! > > I have win95 on /dev/hda1 with extended partition /dev/hda2 <hda5>. > Debian on /dev/hdb1, /dev/hdc1=swap, /dev/hdc2=/usr/local. > > lilo.conf= > > boot=/dev/hda > map=/boot/map > install=/boot/boot.b > read-only > prompt > timeout=100 > vga=normal > image=/vmlinuz > root=/dev/hdb1 > label=linux > other=/dev/hda1 > label=win95 > table=/dev/hda > > Typing win95 at LILO prompt, it syas 'Loading win95' then goes right back to > lilo prompt, no error messages. > The linux section works OK. > > What's the problem? (slink). >
