Quote: Originally Posted by gregrocker
Hi Nighthawk -
The Windows 7 partition needs to be marked Active so Startup Repair will write the System MBR to it after XP is deleted.
And since a Logical partition cannot be marked Active, it needs to be converted to Primary first.
The 7 installer first scans all drives for 7 installations first and lists any found before you can enter the repair tools menu and use the startup repair. You then may see the message that the 7 installation was recovered.
One good example of that was just seen here when testing an idea of adding in the entry of a 7 image restored to the second HD while the first identical host drive was unplugged. The startup repair tool automatically made the second drive the active OS and the host install would fail to load until unplugging the second drive and running it again to see a normal boot.
Once the host drive was unplugged and the second plugged back in the repair tool made the second drive bootable on it's own. Likewise when having two 64bit RC installs on two separate drives without an entry for the second the startup repair (recovered) the second install into the host install when repairng the host from a Grub install error.
With the XP primary wiped the repair tool may still fail to repair the 7 boot information and files since those were likely at the root of the XP primary if 7 was installed after XP. That will mean using the command prompt option while booted live from the 7 dvd.
What worked for removing Grub from the mbr also works when the boot entries are? At the command prompt option simply type:
"bootrec /nt60 C:"
The last option would be the need to rebuild the BCD store entirely. And Windows won't install onto any extended partition only a primary type. Both XP and 7 are on primaries there.