Fix Windows 7 and Server 2008 dual system error

Editor's note: During the installation of Windows 7 RTM in Windows Server 2008, the driver will be internally linked with the existing operating system, which makes many installation work easier, but I found that one of the hardware devices can not be installed at all. See how the author solves this problem.

At present, I mainly use laptops to handle daily affairs and to demonstrate to customers. I installed Windows Server 2008 in an external eSATA driver running in multiple boot mode.

I believe that the external driver has been connected to the internals during the installation of Windows 7 RTM, so that the installation guide can detect the configuration requirements of the multi-boot mode, so that it can be configured automatically, and for this process, we There will be no intervention.

The results of this operation are very interesting. The installed part is working fine; after installing Office 2007 and Live Services, only a small number of programs are not installed and a small number of devices are not configured. At this point, I start to import old data.

The reason why the author did not immediately realize the problem is because the author first started to reload the backup data. When the author installs the DVD, the system displays the error message "Cannot find boot device".

Worse, even if I don't pop up the boot media, I don't plug in the external driver, and the system won't start at all.

First of all, the author tried to use the F8 key when the CD command disappeared and waited for the start to fail. Then you will select "Repair my system" and "Start repair", Windows will find the crux. This time, although I replaced the installation DVD, I chose the same steps as above and got the same result. It just needs some command prompts and gives some startup configuration data editors (BCDEDIT) that can see which parts are being used as startup.

To view these details, the command prompt must be given along with Run as an Admimistrator, as shown:

BootMgr is called D: Driver from the option. That is the author's external eSATA driver. In order to edit its value, the author enters: bcdedit/set{bootmgr} device "partition=C:". I am sure that the C: driver contains the bootmgr that the D: driver used. However, this does not help much in solving the problem.

Next, the author extracts the bootmgr backup by typing: bcdedit/export c: filename. Then, restart the computer from the DVD device and select "Repair System". Then choose to go to the command prompt and delete the bootmgr.efi file in the internal driver of the computer and the external eSATA driver.

Finally, shut down the system and disconnect the external eSATA driver. Then turn on the power and boot from the DVD device. I chose "Repair System", and when the automated process scans for Windows installation, it immediately finds the problem with the startup and recommends fixing it. The author agrees with the system's repair suggestions and restarts the computer without an external eSATA drive and DVD device. So it succeeded.

Now, in the boot menu, you can find options for Windows 7 and Windows Server 2008.

The Windows 7 option looks normal, so I turned it off and connected to the external eSATA driver. When I restarted, I chose to install Windows Server 2008 and everything worked fine.

The following figure shows the current output of the startup configuration data editor:

To change the input entries, they will not be displayed in the form of recovered. Enter: Bcdedit /set {current} description "Windows 7 Ultimate"

Bcdedit /set {001ab8a8-8ac2-11de-9b93-be53b579b53c} description "Windows Server reg; 2008 Enterprise"

Note: {001ab8a8- 8ac2-11de-9b93-be53b579b53c} is replaced with any ID listed in the list.