Windows 7 and Windows Server 2008 dual System errors

At present, the author mainly use notebook computer to deal with day-to-day affairs, as well as to the customer demo. The author installs Windows Server 2008 in an external eSATA drive that runs in multiple boot mode.

This external driver is believed to remain connected to the interior during the installation of Windows 7 RTM so that the installation Guide can detect the configuration requirements of the multiple-boot mode so that it can be configured automatically, and we will not intervene in this process.

The results of this operation are very interesting. The part of the installation works fine, and after Office 2007 and live services are installed, only a small number of programs are not installed and a small number of devices are not configured, and the author starts importing old data.

The reason why I did not immediately aware of the problem is because the author first started to reload the backup data. When the author installs the DVD, the system pops up "unable to find boot device" error message.

Even worse, even if the author does not eject the boot media, and does not insert an external driver, the system does not start at all.

First of all, the author before the CD instructions disappear after waiting for the start of the case, will try to use the F8 key. Windows will then find the crux of the problem by choosing to "fix my system" and "start repair." This time, although replaced by the installation DVD, but the author chose the same steps as above and get the same results. It just requires a few command prompts and gives you a startup configuration Data editor (BCDEDIT) that you can see which parts are used as launches.

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

Bootmgr from the option of calling the device is D: Driven-that is, the author's external eSATA drive. In order to edit its value, the author input: Bcdedit/set{bootmgr} device "Partition=c:". The author is sure that C: drive contains D: Drive used bootmgr. But that doesn't help a lot to solve the problem.

Next, the author through input: Bcdedit/export c:filename to extract bootmgr backup. Then, reboot the computer from the DVD device and choose Repair System. Then choose to go to the command prompt and remove the Bootmgr.efi files from both the internal driver of the computer and the external eSATA driver.

Finally, shut down the system and disconnect the external eSATA-driven connection. Then switch on the power to boot from the DVD device. The author chose the "Repair system", and when the automation process for Windows installation Scan, it will immediately find the problem of startup, and recommended to fix it. The author agrees with the proposed repair of the system and restarts the computer without external eSATA drives and DVD devices. So it worked.

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

The Windows 7 option looks normal, so the author shuts it down and connects to the external eSATA drive. When the reboot, the author chose to install Windows Server 2008, everything works fine.

The following figure is the current output of the start Configuration Data editor:

To change input entries so that they are not displayed as recovered, enter: Bcdedit/set {current} description "Windows 7 Ultimate"

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

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