Dual system or multi-system independent boot setting method open

system startup is a very common operation, but some users are troubled, not that he is a computer rookie but he has installed a dual system because of work, think of him There are a lot of such users, how to deal with it? More and more users install dual systems, but the startup and maintenance of multiple systems has always been a headache, such as Windows XP (hereafter referred to as WinXP) + Windows 7 users (hereinafter referred to as Win7), if there is a problem with the boot file Bootmgr or BCD boot configuration, it will often cause both systems to fail to enter. This article and everyone discuss the use of XRLDR (a lightweight multi-boot management tool) to achieve WinXP, Win7, WinPE three systems independently start the method and skills.

Understanding the basics of multi-system startup

Before using XRLDR, let's take a look at the system startup knowledge so that you can better understand and configure the startup of multiple systems. The system generally starts the program on the hard disk: boot self-test → load the hard disk master boot record (MBR) & rarr; search and activate the system boot file & rarr; load the boot configuration file & rarr; load the system core file & rarr; complete the boot.

For example, if you install Win7 dual system users on WinXP, after installing Win7, it will change the master boot record and use Bootmgr to manage multiple system boot. Its boot process is: load the NT60 master boot record after self-test, then find the boot file <;C:\\Bootmgr” and activate, then load “C:\\boot\\bcd” start the configuration file and list the multiple boot. If you select “Windows 7”, Bootmgr is configured according to the BCD startup information, and the control is given to "Winload.exe" under the Win7 system directory, and then start Win7. If you choose an older version of Windows, Bootmgr gives control to “NTLDR” and then starts WinXP (common system boot files and boot record formats are shown in the following table).

Common System Boot Files

Tip: The hard drive master boot record is not necessarily related to the specific operating system. It is a piece of code that is loaded before the operating system starts. The difference between different types of boot records is the difference in loading boot files, such as NT60 records, which will look for “C:\\Bootmgr” and load it. Bootmgr can boot either WinXP or Linux. The specific system that can be booted is determined by the system startup configuration file. For example, after the startup configuration is written to BCD, Bootmgr can start WinXP system.

From the above startup process, it can be seen that the traditional dual system boot has the following disadvantages:

1. Multiple system startup is completed through the first partition, so once the first partition fails to work properly (such as suffering from virus damage), it will lead to all systems can not start.

2. Multiple system startup files are saved in the first partition and depend on the Bootoggr single file. Once the file is mishandled (such as BCD error editing of the startup configuration file) or accidentally deleted, it will lead to multiple systems. Startup failed.

In order to solve the above-mentioned shortcomings of multi-system startup, we can modify the startup of multiple systems by ourselves. Firstly, the startup files of each system are copied to their respective partitions, and then the independent startup of each partition system is realized by XRLDR configuration, so that the multi-system startup can get rid of the dependence on the first partition and the single startup file, and the process comparison before and after the transformation is shown.

Note: This article uses WinDisk plus D disk to install Win7 dual system installation as an example. In order to facilitate maintenance, I also install WinPE system in E disk.

Actual combat: multiple systems start each

From the above introduction, you can know that the first step of transforming multiple system startup operations is to copy each system startup file to the respective partition, because the startup file is simply copied. The system cannot be started, and the system startup must be configured after the copy is completed. The following describes how to perform specific operations for different systems.

Part I. Implementation of WinXP independent startup

Everyone knows that WinXP is started by "C:\\NTLDR", for users who install Win7 after WinXP, we only need to boot the hard disk. Change the record to NT52 format. After entering WinXP, copy the downloaded "bootsect.exe" to the C drive, then start the command prompt tool and type "c:\\bootsect.exe /nt52 c:”, when the screen appears "Bootcode was successfully updated on A prompt for all targeted volumes.” indicates that the master boot record was successfully changed to NT52 format. Now restart the system will automatically load NTLDR to start WinXP (the Bootmgr boot manager interface will not appear again).

Tip: For users who install WinXP on the basis of Win7, do not use the above command to change the master boot record, otherwise there will be consequences of the inability of both systems to enter. After changing to the NT52 format, the hard disk master boot record will look for the NTLDR file in the root directory of the first partition (the NT60 format is looking for Bootmgr).