When Linux and Windows multi-system coexistence, the boot process is relatively complicated. And it is easy to cause some error concepts. For example, I often see some netizens asked: "I want to guide XXX Linux, should I use LILO, GRUB, or NT OS Loader?" In fact, common Linux boot channels, only boot floppy, lilo, grub, and in the MS-DOS environment Use loadin.exe guided. NT OS Loader is not able to boot Linux. Everyone "So-called" When booting Linux with NT OS Loader, the middle is through LILO or GRUB. In Another Word, if your Linux installation does not have the bootstrap, but it is intended to be guided by a floppy disk, you can't guide this Linux with NT OS Loader. The process of booting Linux with NT OS Loader should be like this: NT OS Loader-> Grub (or Lilo) -> Linux. This process is implemented by: 1, GRUB or LILO is installed on the MBR or a partition of the boot sector to successfully guide Linux. 2, use the DD command to read the installed grub or lilo and write on a file in Linux, which is equivalent to Grub or Lilo, and then removes GRUB or LILO is cleared, You can also use this file to achieve the same boot process as before with the NT OS Loader. 3. Modify Boot.ini Let NT OS Loader boot the GRUB or LILO you just read. As for this Grub that is guided by NT OS Loader, you can do something, fully see your own configuration, you can make him guided any supported systems or additional boot programs by modifying the menu.lst file. You can let him guide only one Linux and set the default time to 0, resulting in NT OS Loader direct directing Linux's illusion. It is also possible to guide N systems from Linux to UNIX, BSD to discharge long system lists. I have even let NT OS Loader and GRUB will be circulated with each other. At this point, NT OS Loader and GRUB are flat, and they can guide each other, but the support of the system is their own skills. NT OS Loader leaves GRUB Don't want to boot Linux / UNIX / BSD; and GRUB is very strong, it is impossible to bypass NT OS Loader to direct MS's NT4 / 2000 / XP / Server 2003 direct boot. But the system concept like MS-DOS, Windows9x / ME is blurred. To be popular, this type of Microsoft's early system can be directly guided by NT OS Loader or directly guided by GRUB. If you have only one MS-DOS / 9X / ME on your machine, GRUB is installed when there is no NT OS Loader, and GRUB will direct this system directly. And if you have NT OS Loader when you get GRUB, then GRUB will boot this system through NT OS Loader. It can even be such that Windows 9X / ME / MS-DOS on the GRUB -> hard disk 2 on the hard disk 1 on the hard disk 1 on the hard disk 1. (Symbol -> Expressed direct boot) There are still some points to pay attention.
1, Grub theory can guide NT OS Loader on the same or different hard drives, but it is not possible to guide GRUB on different hard drives with NT OS Loader. The grub on different hard drives refers to this grub installed on a hard disk different from NT OS Load before being filed by DD. 2, GRUB and GRUB can be directly guided directly (but the number of intermediates can be directly overflow, even if the intermediate pass NT OS Loader is indirectly guided, GRUB's requirements seem to be higher than NT OS Loader.) However, it is not possible between NT OS Loader and NT OS Loader. Only two NT OS Loader can only be connected via GRUB. Make it indirectly to direct each other. And the two NT OS Loaders thus incorporated each other, even if the number of times each other is more, there will be no errors. 3. One Linux on the same machine can be guided by different N GRUB. But an NT system cannot be guided by two NT OS Loader. M $ may do it later, let NT core system is installed on the default NT OS Loader (can be binding across the hard disk). At the end of the installation, you can only use this NT OS Loader to guide him. Any attempt to guide this NT system from other NT OS Loader will be rejected by an error that cannot be found. 4, NT OS Loader on the hard disk 1 on the grub -> MS-DOS on the hard disk 2 on the hard disk 1. When using this guidance method, if the last booted MS-DOS is installed with Windows3.x, the MS-DOS will start normally, but Windows3.x will not be able to enter the file due to the prompt. The solution is to put a NT OS Loader in the hard disk 2. It will be successfully launched as follows: NT OS Loader on the hard disk 1 on the GRUB 1 on the hard disk 1 on the hard disk 2 on the hard disk 2 MS-DOS -> Enter Windows3.x. However, there is still a few in the country that can be used in Windows3.x. Everyone is listening to it. Finally, for users who want Windows and Linux coexist on two hard drives, give the following boot recommendations: First, it is recommended to put all Windows on a hard drive, all Linux placed on another hard drive. If otherwise, some of the following recommendations may not be implemented. 1. Use Linux Excessive Use Windows Types You can use the GRUB to make a bootstrap, so you don't have to care about each bootstrap installation. Because GRUB is to eat all hard drives. (1) Put all Windows first. (2) Place the linux again, put the Linux with the GRUB version you want to place in the final installation. (3) Install the GRUB on the MBR of the Linux disk when installing the last Linux. After this is turned on, you can choose: 1. Select any Linux system in the GRUB menu. 2. Enter the NT OS Loader menu to select any Windows system. 2. Use the type of Windows exe for Linux such available NT OS Loader to make a host boot program. However, since NT OS Loader does not support direct other bootstraps across hard drives, GRUB must be installed in the Windows disk. (1) When the partition is in the last multi-partition in the Windows plate, the partition size is 512 bytes in theory. In fact, the general habits are divided into a few M (too small, not supported). Format into FAT and EXT can be. (2) After installing all systems in the order in "1,".
