This document was originally written for BootIt Next Generation (BING); however it also applies to BootIt Bare Metal (BIBM). There is only one minor difference, in which a BING button was moved to different screen in BIBM. That is highlighted in the appropriate steps in the procedures below. Other than that, wherever the term "BING" is used, you can consider it applies also to "BIBM".
The way Dell formats Windows 7 hard drives for new systems can cause a problem for users of BootIt NG (BING). The boot files are placed in a partition incompatible with BootIt NG's multi-boot operation. Dell now formats the hard drive into three primary partitions:
DELLUTILITY hardware diagnostics from Dell RECOVERY factory restore image, Win7 boot files, Win7 Recovery Environment OS the vast majority of Win7 files
BootIt NG expects the Windows 7 boot files to be in the OS partition with the rest of the Windows 7 files. That would allow copying the OS partition to another partition for modification and testing. It would allow booting either partition, the original or the copy, using BootIt NG's partition rearrangement and multi-boot abilities. However all this is no longer possible, given the way Dell places the Windows 7 boot files.
To make the configuration be what BootIt NG expects, the boot files must be copied from RECOVERY to OS. Then the Boot Configuration Data (BCD) in the OS partition must be edited to show that the OS partition is to be booted when BootIt NG passes control to the OS boot program. The following procedure makes these changes; the partition names used in the procedure are those assigned by Dell. The procedure was stitched together from three articles on the TeraByte website:
Those articles are really about other problems that can occur when installing Windows 7 in a Vista environment, or when installing Windows 7 on a bare hard drive. In the former case, if the Vista partition is active during the install, the Windows 7 boot files end up in the Vista partition. In the latter case, a 100 MB primary System Partition is created. It contains the boot files while the rest of Windows 7 is put into another primary partition. In both cases the boot files are not put in the Windows 7 partition, just as with the Dell RECOVERY partition case. It's as if Dell leaves the RECOVERY partition active when they install Windows 7 on the system being built.
After the following procedure, the boot records are copied to the OS partition and the BCD there is corrected. The DELLUTILITY and RECOVERY partitions are unchanged. In theory those two partitions could then be deleted, but some useful function they provide would be lost. On the other hand, they each take up a primary partition slot and some disk space. That's not so important if you turn off BootIt NG's default "Limit Primaries" option (thus allowing more than four primary partitions), and if the space used (under 20 GB) is not significant. On my systems, I have just left the two Dell partitions in place and created a number of other primary partitions for testing. Note there are some caveats described in the BootIt NG documentation if "Limit Primaries" is turned off.
For the following it is assumed that BootIt NG was already installed on the hard drive, e.g., in space at the end left by resizing the OS partition. If some subsequent Windows 7 installation or repair has replaced the hard drive's boot record so Windows 7 boots instead of BootIt NG, then BootIt NG will need to be reactivated by booting a BootIt NG CD and selecting "Reactivate BootIt NG".
DELLUTILITY
RECOVERY
OS
If such a menu item doesn't yet exist, create it. In either case,
rename (or name) it DELL in Identity to keep things clear in the
following. Make sure the RECOVERY partition is not marked with
Hide.The next step is to use BootIt NG to modify the BCD file settings in the boot files you just copied to the OS partition. In the standard Dell installation, only Windows 7 is specified in the BCD Menu section, so no change is needed there. (That is, in the BCD Menu section, for the Windows 7 item, the Device and OS Device properties should already specify the OS partition.) However the BCD Boot section must be updated as follows to point to the OS partition instead of to the RECOVERY partition.
At this point the Windows 7 boot files have been copied to the OS (Windows 7) partition; the BCD there has been reconfigured to point to the OS partition; and a WIN7 BootIt NG boot menu item has been set up to boot the OS partition. (The DELL menu item is no longer needed and can be deleted now or later.) Now click on Resume in the Maintenance window and select the WIN7 menu entry to be sure Windows 7 boots as expected. If that works, you can now boot BootIt NG and do any tailoring you want, e.g., renaming menu items and partitions. What I do is described below.
I have chosen to keep the DELLUTILITY and RECOVERY partitions. I turned off "Limit Primaries" so there can be more than four primary partitions. I renamed the OS partition to WIN7 and resized it to be much smaller than what Dell had set up. I then added TEST1 and TEST2 partitions, each with exactly the same size as WIN7, so BootIt NG Copy can be done between all three partitions. I also added a DATA extended partition, split into several logical volumes. The following three boot menu items allow each partition to be booted and have access to the DATA partition:
Menu Details
---- -------
Identity WIN7 TEST1 TEST2
HD 0 0 0
Boot WIN7 TEST1 TEST2
Boot Details
---- -------
0) WIN7 TEST1 TEST2
1) DATA DATA DATA
2)
3)
The DELLUTILITY and RECOVERY partitions are probably still reachable via Dell-specific keystrokes during boot. I usually don't try to access them via BootIt NG facilities, so I have deleted the DELL menu item. If necessary, you can always create a boot menu item to access the desired partition.