The general idea is that you copy the first sector of your native root Solaris/x86 partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.sun (inspired by c:\bootsect.dos) you can then edit the c:\boot.ini file (copy boot.ini to boot.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/Windows NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

Here's one way of doing it. Solaris/x86 requires it's partition to be active and uses it's own boot manager with it hard-coded to boot to Solaris on timeouts.

Windows NT (both the Workstation and Server) is a 32-bit Operating System. It is a preemptive, multi-tasking Operating System, which means that the Operating System controls allocation of CPU time, not the applications, stopping one application from hanging the OS. NT supports multiple CPU's giving true Multi-tasking, using symmetrical multiprocessing, meaning the processors share all tasks, as opposed to asymmetrical multiprocessing, where the OS uses one CPU and the applications another.

Solaris boot manager will be the master boot controler, but then choose partition 1 to boot NT (yes that is right, not 2). Then the NT boot manager will come to life, allowing you to select either DOS (partition 1) or NT (partition 2). Note that Solaris is the active partition.

MS Windows support is relatively recent, and still experimental; Freeciv was originally written for Unix and the X window system, and is, in fact, extremely portable across Unix versions. One option is to install a Unix variant on your PC (such as Linux) and use that. The Freeciv client is unable to open a window on your local X display. Are you running an X server at all? Maybe you need to install and run one, or switch to a Freeciv that doesn't need X; see the previous question.

Boot.ini - This is read-only system file, used to build the Boot Loader Operating System Selection menu on Intel x86-based computers Ntdetect.com - This is a hidden, read-only system file used to examine the hardware available and to build a hardware list. Ntldr starts the appropriate minifile system drivers. Minifile system drivers are built into Ntldr and can read FAT or NTFS For other operating system, Ntldr loads and runs Bootsect.dos and passes control to it.

Under UNIX, there's a PGP command line utility (pgpe) which does the encryption. However, under NT, PGP 5 is GUI based only. PGP 6.5.1 brings back the command line, but I haven't got it to work in conjunction with Soupermail yet. All is not lost though, as you can use the DOS version of PGP 5 under NT. A couple of caveats; Use an up to date version of perl. Activestate build 509 hung when calling PGP 5, build 518 seemed fine.

Which operating system you decide to use should depend on what features you need. For example, if you are already using IIS, ASP, VBScript, Windows Media, Microsoft Access, Microsoft SQL Server, or Visual InterDev, and you don't have the time to learn Unix-based solutions, you'll have to choose a Windows NT or Windows 2000-based host. Just because your desktop is Windows-based doesn't mean you should use a Windows host.

To use System Commander to dual boot both Win NT and Solaris, make these two configuration changes to System Commander: Use System Commander's local setup (Alt-s, Local config) to hide all other partitions from NT and Solaris (so they can't see each other's partitions).

Grab OS-BS [a free boot manager distributed with FreeBSD] from: ftp://ftp.freebsd.org/pub/FreeBSD/tools/osbs135.exe Or (newer) from: http://www.prz.tu-berlin.de/~wolf/os-bs.html Assuming you've already got Linux installed and enough free space for Solaris, go ahead and install the latter. Solaris then becomes the Active partition. Follow that installation with OS-BS and configure to "set startup id", which changes the Active partition on-the-fly.

You cannot create a boot disk with Windows 2000 or NT, but you can use a boot disk created by Windows 95 or 98 to recognize your NWDVDPR. Note: If your file system is NTFS, you will not be able to read data on your hard drive when using the boot disk.

Follow the instructions for the previous question substituting /dev/hdc as directed. An alternate, much-more-difficult method follows that doesn't involve the "switch drives with /boot/chain.b" trick. These are basically the steps I 'discovered' through countless failed attempts to get Solaris to boot from the secondary master. I got LILO to boot Solaris/x86 2.5.1 from the master disk of the secondary IDE. Solaris was initially installed in the primary-master disk, i.e.

Basically, the Linux LILO boot loader is used to fool solaris into thinking the slave is the master and vice versa (with the chain.b line) Add this in your Linux /etc/lilo.conf: use /dev/hdc instead of /dev/hdb if your second drive is the secondary IDE master instead of the primary IDE slave drive) Solaris had a bit of trouble because for some reason it had the default boot device as the primary HD and couldn't mount the root filesystem off of it (because it wasn't there).

You can configure your computer to start Windows 2000, Windows NT, and either Windows 95 or Windows 98. However, you cannot configure a computer to multiple boot Windows 95 and Windows 98. Both Windows 95 and Windows 98 use the same boot file. Therefore, multiple booting Windows 95 and Windows 98 at the same time is not supported. Your installations are less prone to problems if you install Windows 95 or Windows 98 before you install Windows NT and Windows 2000.