There are more and more users installing 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 (hereafter referred to as Win7), if the boot file Bootmgr or BCD boot There is a problem with the configuration, which often leads to the inaccessibility of both systems. 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:bootbcd” start the configuration file and list 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 File
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 the different types of boot records is the difference in loading the boot file, such as the NT60 record, 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 the BCD, Bootmgr can start the 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) Will cause all systems to fail to 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, multiple system startup failure will result.
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.
Note: This article uses the C drive to install WinXP plus D drive to install Win7 dual system installation as an example, in order to facilitate maintenance, I also install WinPE system on the E drive.
Combat: Multiple systems are started separately
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. Since the startup file cannot be started simply by copying the startup file, the copy is completed. The system startup is also configured. The following describes how to perform specific operations for different systems.
Part I.Implementation of WinXP independent startup
We know that WinXP is started by "C:NTLDR", for users who install Win7 after WinXP, we only need to change the hard disk master boot 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 all" The prompt for 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).
Part II. Implement Win7 independent startup
After completing the above operation, restart the system and enter WinXP, and cut the entire directory of “C:bootmgr” file, “C:boot”, to the root directory of the D disk. Then run the downloaded “bcdtool.exe”, click “ Launch Configuration & Rarr; Open ”, open the “d:bootbcd” configuration file. Select “Edit → Delete Startup Project> to delete all the original startup projects. Then select “Edit →New Vista Startup Project", select the new project, double-click the <quo;device” item in the right pane, and change it to <quo;partITion=D:” (drive letter according to Win7 Change the specific partition of the installation), “description" (start menu display name) changed to “Windows 7”.
After the above startup file is moved and configured, as long as we can load “D:bootmgr”, Win7 can be booted from the D drive (Bootmgr loading needs to be configured with XRLDR).
Part III. Implement WinPE independent startup
Because Win7 startup often needs to be repaired by WinPE, in order to facilitate the maintenance of Win7 system, we can also manually install WinPE system on local hard disk. Just prepare the Win7 installation CD, open the CD and copy all the files except the files directory.install.wim” to the E disk to complete the installation.
Final setting ——Multi-system unified management
After completing the configuration of the above three systems, now enter WinXP system, run the downloaded XRLDR, click “Install/Configure” enter the configuration interface. In the interface preview, select “ the first operating system & rdquo;, in turn, the following settings:
1. Start mode single-select "Start from file", start file select NTLDR (for starting WinXP, start Win7 and WinPE chooses Bootmgr).
2. Start the partition to select the first partition (that is, the partition where WinXP is located, other systems are selected according to the specific partition).
3. System type selection <;NTLDR/BOOTMGR”, and check “ activate to activate the primary partition when starting.
4. Change the menu text to "windows xp", and then click "Generate" (font, color, font size, etc.) according to your preferences. Other parameters take the default settings.
5. Operation as above, set the startup configuration of Win7 and Win PE systems in turn, and finally click “Write to disk” to complete the change to the master boot record.
OK, now just restart the computer, we can choose the system you like in the boot multi-boot menu to enter (the next time you start the system selected by default, the default boot system can be set in XRLDR).
The above three systems are started independently. For example, after selecting Win7, click “Open Computer Management & Rarr; Storage & Rarr; Disk Management”, and you can see that the partition where Win7 is located is both the system partition and the boot partition, indicating its Booting does not depend on the first partition.
Tip: What is the system partition, boot partition? According to the Microsoft help documentation, the system partition refers to the partition containing the hardware-specific files required to load Windows (such as Bootmgr), the system partition can (not necessarily) and boot partition the same. A boot partition is a partition that contains the Windows operating system and its supporting files. In the case of the traditional WinXP+Win7, its system partition is the first partition for Win7 (because the specific files required to load Windows such as Bootmgr and Boot boot directory are in the partition), the boot partition is the second partition (because the Windows operating system directory) In the partition). Here, the system partition and the boot partition are combined to indicate that the partition contains system files and boot files, which indicates that the system is autonomously and independently started.
After the above transformation, we have realized the independent startup of WinXP, Win7, WinPE three systems, which brings great convenience to our daily maintenance. For example, before the transformation, the Bootmgr file was deleted by mistake. After restarting, it is impossible to start multiple systems. Now, you can enter the WinXP system. You can fix the startup problem of Win7 system by copying Bootmgr to D disk on other computers. Similarly, if Win7's BCD menu fails, we can also enter WinPE and use the Bcdboot command for quick fixes.
Even a computer master, often encounters multiple system startup failures, and once it fails to start, it can be time consuming and labor intensive to maintain. This paper provides a different approach for multi-system maintenance. It is independently booted by XRLDR to realize independent startup of each system. If you have installed multiple systems and have experienced excessive system startup failures, then try the methods described in this article to greatly reduce your maintenance work!