Have not had your problem Laurent as my kit is too old but think I can
help. Terminology is often confusing here. I got an ooooold Slackware
distribution from a demo CD from 1996 or sometime and that had lots of
documentation about LILO that came with it in .tex format in the
/usr/doc/lilo directory (sym. link to /usr/lib/lilo on mine), using the
makefile makes .dvis and then dvips makes Postscript that I viewed with
Ghostview in X. It was really interesting, nicely laid out and
helpful. Can poss. email to you if needed.
Basically MBR is just one of the different types of boot sector. They
are all a bit like the one you get on the first sector of a floppy (even
"blank" or "data" floppies have one but it usually does nothing but
print the message "Non system disk" and hang). Most (all?) partitions
on a HD have a boot sector, also the disk itself has one. This last one
is the MBR. Many of these boot sectors also contain a partition table
in their second half on top of the bootable code in the first half.
Different OSes have different stuff in the boot sectors. The DOS MBR
code looks to its partition table and looks for the active partition
then loads that partition's boot sector and executes it. This is why if
you have left the "normal" DOS MBR on your main drive you have to use
either DOS or Linux fdisk to change the active flag if you want to "boot
from another partition".
So basically the MBR is only relevant on your main disk but if it's a
DOS MBR then it can't boot something on the second hard disk which is
where lilo comes in. As I understand it you've got Linux somewhere on
your main disk and Windows 95 somewhere on your second disk? If this is
the case then leave the DOS MBR on the main drive and have it boot lilo
on your linux partition. Then configure lilo to either boot Linux or
Win95 from the 2nd drive. It will be irrelevant what is on the MBR of
the second drive. If you are paranoid and want to set it back anyway
then proceed as Steve suggested then when Windows 95 is running from the
second drive you should be able to use FDISK /MBR to replace the DOS MBR
on that disk. I haven't tried this myself though because my second
drive contains only my WinNT with 100% NTFS so I can't do it!
> I had the same problem, and will try Steve's solution.
> But before reading, I've made a mistake: I put a MBR
> on /dev/hdb and instructed the BIOS to boot on drive D:
> It doesn't work. How to remove this MBR? install-mbr
> man page is mute on the topic. Do I have something
> to tell to the BIOS?
> Thank you for any hint.