How to fix Windows 7 startup items in XP

XP and win7 dual-system, reinstall XP without affecting the win7 Method

During the transition period, it is usually necessary to install a dual system. I chose the classic XP and win7rtm as the dual system, which are located on two disks respectively. Yesterday, we were going to install vc60 in xp. We found that there was a problem with that XP. It seems that the system must be reinstalled, but we all know that the order for installing multiple systems in Windows systems is from low-level to advanced. Otherwise, the system may fail to boot normally. But I am reluctant to reinstall win7. I read many posts online, but most of the methods are backup or something, which is very troublesome. Finally, I was lucky enough to find a small tool that could easily solve this problem. The Tool Name Is bcdautofix. From then on, you can boldly reinstall XP, and then run this tool under XP to fix the win7 boot. I hope you will like it. The following is a small tool attached:
 

 

Application Scope:
1. format or ghost active partition (drive C), reinstall the system, and then add the Vista/2008/win7 boot menu to fix other partitions.

2. Install 2008/XP/2000 on Vista/2003/win7 and then add the repair menu for the original Vista/2008/win7 boot menu.
Simplify the simplest solution for installing 2008/XP/2000/2003 after Vista/2000/win7: 2003/XP/CD boot directly to other partitions, and then run this program to fix it.

3. Fix other faults caused by BCD.
3-A: Windows Recovery Environment
3-B: the 3D boot screen of win7/2008r2 is lost due to BCD (it becomes the Start Screen of the Vista scroll bar)
3-C: Startup menu selection page garbled by BCD
3-D: add the Windows Recovery environment menu to Vista/2008. Use this menu to create a recovery folder in the system drive letter, and then add sources/boot to the CD or the installer. wim (whether this file is renamed as winre. wim at Will) and boot/boot. two SDI files are copied to the recovery folder and then run this program to automatically add the files.
3-E. Menu loss for unknown reasons
3-f. Rare forced repair of BCD. phenomenon: In Vista/2008/win7 --
The "Boot" column is blank after msconfig is run
An error occurred while running commands such as bcdedit and BCD at the command prompt as the administrator.
The default Operating System and waiting time cannot be configured in the "Start and fault recovery" Window of the system attribute.

Note: Such a fault generally does not affect the original system, but may cause other software to be unable to automatically add a new menu based on BCD management. Therefore, you have to decide whether to force the repair.

Usage:
Runs directly without installing software. It can run on 32-bit and 64-bit systems or winpe systems. The program searches for the system in the form of drive letters, so make sure that the system points you want to add are hidden drive letters.

You can add the repair Vista/2008/win7 boot menu, or add the repair 2000/XP/2003 boot menu if conditions are met. For example, you can run the Vista boot menu to add other partitions in XP to automatically generate the Windows XP + Vista multi-system boot menu, in Vista, the Startup menu for adding XP needs to meet the three required boot files of XP (ntldr/ntdetect.com/boot.ini) if an active partition exists and the active partition is not hidden, the drive letter is added. (If the XP menu does not meet the conditions and cannot be added, for example, the XP menu already exists in the original multi-system menu, does not affect existing XP boot menu items ).

After the program runs correctly, if the original bcd startup configuration exists, it will be backed up under C:/AutoFix and named bcdbackup1. After multiple runs, the number will be accumulated. c:/AutoFix under AutoFix. log is the program running record file. record File Content is for reference only.

Partial update description
090416 update: added support for traditional Chinese systems
090417 (v1.0.0): fixed some procedures and changed the version to V1.0.
090616 (v1.0.3): slightly corrected/changed the packaging method
090711 (v1.0.4): fixed the bug that the runtime in 2000/XP/2003 is not applicable to the range of 3-f detection, and added support for the USB flash drive PE, pack 2000/XP/2003 boot files for users who need them.
090716 (v1.0.5): fixed a small error in running v1.0.4 in PE.

The 2000/XP/2003 boot menu cannot be automatically repaired:
Because the program focuses on automation, and can be fixed when the Vista/2008/win7 boot file is lost. because the program should consider as many possibilities as possible, rather than increasing startup failure after running.
If you have any expert friends who can help me solve the following problems, I hope to give them some advice.
When the 2000/XP/2003 Startup File is lost and the win7 system running the program hides the active partition, the program cannot copy boot files of 2000/XP/2003 to the hidden drive letter active partition (in fact, this can determine whether the active partition is hidden drive letter and prompt the user to add a drive letter for the hidden partition) run this program again to fix the 2000/XP/2003 Startup menu)
The biggest difficulty lies in determining the value of RDISK (x) Partition (x) in Boot. ini.
Manual judgment of this value is simple (manual judgment can be found:Http://bbs.pcbeta.com/viewthread.php? Tid = 435850), It is difficult to automatically determine the value.
If you can handle these two cases (or automatically generate boot. ini only accurately), the program can automatically repair the 2000/XP/2003 boot menu.
Run in XP:

Download (39.87 KB)

 

Download (69.3 KB)

Run in win7: