1. Successful Multiboot setup when NT Loader owns the Master Boot Record
There seem to be many questions on this and related topics. There is
a good solution based on the program called "bootpart" and techniques
developed by Gilles Vollant. See the Web page at
Using an earlier version of bootpart, I was able to set up multi-boot
NT, Linux, BeOS, and OS/2. Gilles has a FAQ that discusses the
multiboot problem and the method for including LILO for booting. For
Linux, booting is handled by NT Loader; the boot block is placed in the
Linux root partition, NOT in the MBR. Gilles also has a handy routine
for fixing NT's MBR if it gets screwed up.
Booting multiple MS operating systems or OS/2 presents special problems,
which Gilles also discusses in detail. Because of the MS-invented
MONSTROSITY of active, inactive, hidden, primary, virtual HD
partitions, everyone suffers. In particular, all these OSs require a C:
and ONLY ONE MAY BE ACTIVE AT A TIME. I don't THINK the
NT Loader changes a partition to active when it needs to be booted, For
this reason, I set up an OS/2 Boot partition as one of the things loaded
from the NT Loader menu. This knows how to change partitions back
and forth from active to inactive, so I could boot OS/2 after coming out
of NT, and vice versa.
Last night I did a re-install of Linux on my system. During the
told it to write the boot sector in the /root partition. Then I ran
and created a boot sector image of Linux's disk for NT Loader. It took
about 10 minutes, and it works great!
2. limiting multiple logins by same user
3. RH5.0+NT Server 4.0 + Win95 boot problem
4. Direct sockets in linux
5. Samba 1.9.18p7 Win NT 4.0 SERVER, Master Browser Problem
6. 3ware Raid
7. PCI-bus with Linux 0.99?
8. Master Boot Record Error
9. killing the master boot record
10. master boot record
11. Problem is Master boot record
12. Killed Master Boot Record with Dr Dos.