In linux.debian.user, you wrote: > > Well, after several attempts at re-running LILO, it still didn't get any > further. So, needing my PC in some kind of working order I set about > repairing the Win2000 boot sector... And got exactly the same as my > post-Linux install boot attempts. In the end (after running round the room > panicking quite a lot) I found out about, and ran FIXMBR from the Windows > recovery disks. It worked (easing my heart condition somewhat!) > > So.... it appears LILO is doing something nasty with my disk's MBR. Any > suggestions where I could go from here? Are there other Linux boot programs > I could try? Do you need any technical details about my system to help? > (I'm a bit of a newbie when it comes to system type stuff). > > In case it's this, here's my lilo.conf (with comments taken out): > > lba32 > boot=/dev/hda > root=/dev/hdd1 > install=/boot/boot-menu.b > map=/boot/map > delay=20 > vga=normal > default=Linux > image=/vmlinuz > label=Linux > read-only > image=/vmlinuz.old > label=LinuxOLD > read-only > optional
One way to play around with this without wrecking the mbr is to do this on a floppy. change the boot line to 'boot=/dev/fd0' so that it writes to a floppy. Put a floppy in the drive and run /sbin/lilo. Then boot with that floppy in. This is not the same as a rescue or boot floppy - the kernel will not be on the floppy - just LILO will be there. I personally prefer to use the image that is in /boot for the image line, but yours should work if /vmlinuz is a symlink to the real kernel in /boot. There was a post about disk geometry. It's possible that LILO is not reading the geometry on /dev/hdd correctly. That post told you how to check it. You can specify the geometry in lilo.conf if that is the problem. At any rate while you are testing this, if you use the floppy instead of writing to the mbr, it will save you that trouble. There is also GRUB which can be put on a floppy as well. Anita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
