I tried another copy drive and I ended up with a non-bootable system. I get the same error as before when I try to boot XP.
Something about a recent hardware change and then it says the file ntldr is either corrupt or missing.
I can put in the XP install disc and go to the recovery console and run fixmbr and then fixboot and the system will then boot into XP.
I did the copy drive again, and this time I booted to a BootitNG disk. I highlight XP and click "BCD Edit"
Then with XP higlighted I click "Edit" again.
Under "Device" it said "unknown". I changed it to the only other option "{Boot}" and the system will boot now without the error.
Since XP boots properly with that change, it's not a drive letter issue.
Do you know what that entry is supposed to show?
When I'm XP now, I open EasyBCD and that new entry is listed under "Device".
Thats the same entry that always gets messed up for all the other operating systems. EasyBCD sets that entry by what the target drive letter is, from the viewpoint of the OS you are currently in.
Right now I get the same errors for the other operating systems except the error says winload instead of ntldr.
But I know if I use EasyBCD to change the vista "Device" to D then Vista will then boot or at least try to boot.
I don't think it's the partition signature because EasyBCD shows a line right above it "BCD ID".
Under XP, it says "Boot" because I changed that with BootitNG
All the others say "unknown" because thay have been broken from the drive copy.
Normally EasyBCD shows drive letters for those entries
XP would be C, Vista D, the windows 7's would be E and F.
I assume EasyBCD is just showing letters just because it's easy for someone to set them, but I can't believe windows really uses drive letters for those entries. I just can't figure out what they are really supposed to be.
Device... HD0 and Partition XP (but you could have {boot} and it would be OK although {boot} is usually associated with the Windows Boot Manager entry)
For each of the Win7s, Device and OS Device I have...
Yesterday I set up the 120 gig drive with XP1, XP2, Vista1 and Vista2, backed the drive up to create the restore point.
Using the Image/Restore method XP1 booted ok and Vista1 and Vista2 booted ok but XP2 hung on the Windows screen prior to a full bootup (blue with dark blue bands top and bottom) so very nearly cracked it.
I went into recovery consul to try and fix it (WinXP repair didn't) but I didn't know which other command to use like Dave did in message 121 but fixboot wouldn't work for me.Then I tried a Copy-Drive method and that failed completely, not one O/S would bootup.
Like I said before I had better results with Image/Restore but Copy-Drive is a complete failure, had enough now, down to the team to sort out for the next release.
Using the Image/Restore method XP1 booted ok and Vista1 and Vista2 booted ok but XP2 hung on the Windows screen prior to a full bootup (blue with dark blue bands top and bottom) so very nearly cracked it.
Deric,
That is due to a drive letter issue. I didn't get as far as trying to boot the copied OS as I was getting drive letter issues on the source OS. Ghost was editing {MountedDevices} on the source OS. I'm retiring from this testing too.
