Document Sample
XP_Vista_7_Dual_boot Powered By Docstoc
					This tutorial explains how to install Windows version prior to Windows Vista and Windows 7
after you have installed Windows Vista/7. In this tutorial, we are considering Windows XP as
the old windows version.

This has been tested with Windows Vista as the new Windows version and Windows XP as the
old Windows version. This tutorial should also work if the new Windows version is Windows 7,
since Windows Vista and Windows 7 uses BCD for boot control.

Step 1 - Partition the Drive:

If you have knowledge of partitioning the hard drive or if you have already partitioned the
hard drive to install Windows XP, skip this step.

Vista/7 comes with an inbuilt partitioning tool, so we’ll be using it instead of 3rd party
partitioning tool.
-Right-click “Computer” under the start menu and choose "Manage".

-Right-click the drive you want to partition, and select "Shrink Partition"

Note: Shrinking a partition is not at all recommended as it may result in data loss or corrupted
partition table (some times in the future). Use it only if there is no other way to have multiple
drives (some branded PC/Laptops don’t allow partitioning when using their recovery disks).
-The amount you shrink the partition is the amount of space used for the XP partition, so I
would suggest making it at least 3-4GB (15-20GB Recommended) in size, as a full XP installation
will take 1.5GB on its own.

-Now Right-click the unallocated memory and select new basic partition.

-Choose NTFS file system, this will save formatting before installation.
-Name the drive anything you like, I chose "Windows XP"
-Click “Next” on the rest of the screens and finish.
Once the formatting is finished you will have something like this:

Note: this new partition is where your XP installation will go, so take note of it's location, in
case there are multiple partitions on the drive (there will now be at least 2).

Step 2 - Install XP:

Wait while XP installs (I won't go into detail, there are many tutorials on this, and it is
reasonably straight forward).
Now that XP has installed, it attempts to boot for the first time... all goes fine, video settings,
networking, then the lovely welcome screen as usual.

You restart, expecting a boot loader screen... followed the tutorial this far, and now you seem
to only have XP... well not quite, I wouldn't leave you hanging without giving you a proper dual

Here lies the only real issue with installing XP after Vista/7, but it's a quick fix if you have your
Vista/7 CDs/DVD handy.
The problem is that Vista/7 and XP use different boot loader utilities in the MBR (Master Boot
Record) of your hard drive. XP does not recognize Vista/7, but Vista/7 will recognize XP, so we
need to remove the boot loader that XP just put in with the old Vista/7 boot loader. So restart
once more, but this time with your Vista/7 disc in the drive.

Step 3 - Fix Boot Loader:
Vista/7 will load the GUI files, and then display the loading splash screen.
-Click "Next" on the first screen
-Once the "Install Now" menu (do not click Install Now) choose "Repair Your Computer":

-You will be prompted to choose the OS to repair. Don't worry if Vista/7 is the only OS that
shows up, even after a search.
Click "Next".

Note: There is a "Fix Startup" option, but it's been my experience that it doesn't work, and this
method did. You are free to try that option.
-Choose to open a "Command Prompt":

Type in the command prompt the following 2 lines (separately):
Bootrec.exe /fixMBR
Bootrec.exe /fixBoot

-Close the prompt and restart (or you may type the command “shutdown –r –t 0”)
-Now that Vista/7 controls your boot loader, the process is mostly finished, now we need to
inform Vista/7 that XP is installed, as to enable the boot loader selection screen.
Step 4 - Edit boot.ini:
Note: There are programs such as EasyBCD that will do this for you; here we do it the manual

In Vista/7, the boot.ini is not editable directly, as the file itself is hard to locate, so we will be
modifying it through "Boot Configuration Data Store Editor" bcdedit.exe:
(Just as an explanation, the loader type for XP is an NT Loader, hence the use of ntldr)

-Open a command prompt with administrative privileges (Right-click and choose "Run as

Note: the following 2 answers from bcdedit for each item are acceptable:
"The Operation Completed Successfully"
"The Specified Entry Already Exists"

Be sure to type each line carefully (replace C in the first line with the drive containing your
Vista/7 installation):

bcdedit –set {ntldr} device partition=C:
bcdedit –set {ntldr} path \ntldr
bcdedit –displayorder {ntldr} –addlast
bcdedit -set {ntldr} description "Microsoft Windows XP"

The completed bcdedit file should resemble this:
-This will correctly add XP to your boot sequence, and even name it properly instead of "Earlier
Version of Windows"
-The “displayorder” line also allows the entry to be visible under the advanced settings of your
computer properties.

Vista/7 is the default boot, if you wish to change this to XP it can be done by setting {current} to
addlast, or under the computer

-> properties -> advanced settings.

If all done properly, XP and Vista/7 will dual boot properly!

Useful Softwares

EasyBCD (Description taken from website)
EasyBCD is NeoSmart Technologies' multiple award-winning answer to tweaking the new Windows Vista
boot loader. With EasyBCD, almost anything is possible. Setting up and configuring Windows boot
entries is simple, and there is no easier way to quickly boot right into Linux, Mac OS X, or BSD straight
from the Windows Vista boot loader - on the fly, no expert knowledge needed!

iReboot (Description taken from website)
iReboot is NeoSmart Technologies' simple yet effective reboot helper tool. iReboot sits in your taskbar
at startup (only taking up 400KB of memory!) and lets you choose which operating system you want to
reboot into. Instead of pressing restart, waiting for Windows to shut down, waiting for your BIOS to
post, then selecting the operating system you want to boot into (within the bootloader time-limit!); you
just select that entry from iReboot and let it do the rest! If you liked EasyBCD, you'll just love iReboot!

Goto NeoSmart Website to download latest versions of these softwares
BCDEdit (From Microsoft TechNet)

Boot Configuration Data (BCD) files provide a store that is used to describe boot applications
and boot application settings. The objects and elements in the store effectively replace Boot.ini.

BCDEdit is a command-line tool for managing BCD stores. It can be used for a variety of
purposes, including creating new stores, modifying existing stores, adding boot menu options,
and so on. BCDEdit serves essentially the same purpose as Bootcfg.exe on earlier versions of
Windows, but with two major improvements:

        BCDEdit exposes a wider range of boot options than Bootcfg.exe.
        BCDEdit has improved scripting support.

          Note: Administrative privileges are required to use BCDEdit to modify BCD.

BCDEdit is the primary tool for editing the boot configuration of Windows Vista and later
versions of Windows. It is included with the Windows Vista distribution in the
%WINDIR%\System32 folder.

BCDEdit is limited to the standard data types and is designed primarily to perform single
common changes to BCD. For more complex operations or nonstandard data types, consider
using the BCD Windows Management Instrumentation (WMI) application programming
interface (API) to create more powerful and flexible custom tools.

BCDEdit Command-Line Options
The following command-line options are available for BCDEdit.exe.

BCDEdit/Command [Argument1] [Argument2] ...

General BCDEdit Command-Line Option

Option                                            Description

         Displays a list of BCDEdit commands. Running this command without an argument
         displays a summary of the available commands. To display detailed help for a particular
/?       command, run bcdedit /? command, where command is the name of the command you
         are searching for more information about. For example, bcdedit /? createstore displays
         detailed help for the Createstore command.
BCDEdit Command-Line Options that Operate on a Store

   Option                                            Description

               Creates a new empty boot configuration data store. The created store is not a
               system store.
               Exports the contents of the system store into a file. This file can be used later to
/export        restore the state of the system store. This command is valid only for the system
               Restores the state of the system store by using a backup data file previously
               generated by using the /export option. This command deletes any existing entries
               in the system store before the import takes place. This command is valid only for
               the system store.
               This option can be used with most BCDedit commands to specify the store to be
               used. If this option is not specified, then BCDEdit operates on the system store.
               Running the bcdedit /store command by itself is equivalent to running the bcdedit
               /enum active command.

BCDEdit Command-Line Options that Operate on Entries in a Store

Option                                            Description

/copy Makes a copy of a specified boot entry in the same system store.
        Creates a new entry in the boot configuration data store. If a well-known identifier is
        specified, then the /application, /inherit, and /device options cannot be specified. If an
        identifier is not specified or not well known, an /application, /inherit, or /device option
        must be specified.
/delete Deletes an element from a specified entry.

BCDEdit Command-Line Options that Operate on Entry Options

   Option                        Description

/deletevalue Deletes a specified element from a boot entry.
/set           Sets an entry option value.
BCDEdit Command-Line Options that Control Output

Option                                           Description

      Lists entries in a store. The /enum option is the default value for BCEdit, so running the
/enum bcdedit command without options is equivalent to running the bcdedit /enum active
         Verbose mode. Usually, any well-known entry identifiers are represented by their
         friendly shorthand form. Specifying /v as a command-line option displays all identifiers
         in full. Running the bcdedit /v command by itself is equivalent to running the bcdedit
         /enum active /v command.

BCDEdit Command-Line Options that Control the Boot Manager

       Option                                          Description

                      Specifies a one-time display order to be used for the next boot. This
                      command is similar to the /displayorder option, except that it is used only
                      the next time the computer starts. Afterwards, the computer reverts to the
                      original display order.
                      Specifies the default entry that the boot manager selects when the timeout
                      Specifies the display order that the boot manager uses when displaying boot
                      options to a user.
                      Specifies the time to wait, in seconds, before the boot manager selects the
                      default entry.
                      Specifies the display order for the boot manager to use when displaying the
                      Tools menu.

BCDEdit Command-Line Options that Control Emergency Management
     Option                                         Description

                Enables or disables Emergency Management Services (EMS) for the specified
/ems            Enables or disables EMS for the specified operating system boot entry.
                Sets the global EMS settings for the computer. /emssettings does not enable or
                disable EMS for any particular boot entry.
BCDEdit Command-Line Options that Control Debugging

   Option                                        Description

             Enables or disables the boot debugger for a specified boot entry. Although this
             command works for any boot entry, it is effective only for boot applications.
             Specifies or displays the global debugger settings for the system. This command
             does not enable or disable the kernel debugger; use the /debug option for that
             purpose. To set an individual global debugger setting, use the bcdedit
             /setdbgsettings type value command.
/debug       Enables or disables the kernel debugger for a specified boot entry.

To troubleshoot a new installation, enable debug mode by modifying the boot configuration file
(BCD). For example, use the following syntax to enable kernel or boot debug.

bcdedit /set <id> debug on


bcdedit /set <id> bootdebug on

Where <id> is the GUID of the Loader object that is used to load the operating system. "Default"
can be used if the operating system is the default option of the Boot Manager menu.

For examples of BCDEdit, see the Windows Hardware Developer Center Web site.

Shared By: