Solved Cloning active partitions won't work

[Bernardus]

On my system I have a SATA 1TB drive with XP installed on a 50GB partition. I decided to run Windows 7 on another separate drive of 80 GB. Now I wanted to clone the XP to the 80 GB en transplant W7 to the faster 1TB drive. In fact swap partitions. This because I wanted a dual boot system and use some well working XP programs incompatible with W7. The W7 did work well after all, but XP gave problems with the logon. The logonscreen was demanding for a WW (which I didn't install to overcome this problems and left it blank). If I enter on the correct accountname and the blank WW, it says log of, and the screen hangs forever. No return of Administrator account for instance. No way to change that. I did the backup with Acronis 2010 on XP, and Acronis 2011 on W7 (both are incompatible). The problem is that you have to choose options whether or not to rebuild the MBR or Systemfile? Older versions simply took the whole thing at once. What could cause this problem and solve it?

 

[gregrocker]

Create an Acronis backup of XP, reimage again to a freshly formatted partition. If possible wipe the target HD first (after moving off data) with http://www.sevenforums.com/tutorials/52129-disk-clean-clean-all-diskpart-command.htmlDiskpart Clean Command to clean the boot sector.

If asked include the MBR and Track 0, providing the original XP is SYstem Active partition.

What happens now?

 

[Bernardus]

It may indeed have something to do with the boot-sector. Xp MBR is incompatible with Vista or W7. So should I rewrite de MBR with BCD in XP mode? I thought that Acronis should replace the MBR, but as you pointed out that is not the case. Backing up now both partitions before I continue and hope that the thing will start again. Thank you for your reply I let you know.

 

[Bernardus]

Yes, it worked out well. Thank you for your help. One thing. With easy BDC you can install a dual boot system. XP/W7 However what to do to delete that option? Even if I delete the XP entry the W7 bootmanager may show up or the system says: no bootmanager. No entry means, no booting. So when you don't do it correct, you won't be able to boot at all. I'd like to switch it on or off. But that will rewrite the MBR. It's possible wit BDC to write an XP or W7 MBR for what I understand. Will that reset an original kind of MBR for both versions ? With regards

 

[gregrocker]

Please post back a screenshot of your maximized Disk Management drive map and listings:

1. Type Disk Management in Start Search box.
2. Open Disk Mgmt. window and maximize it.
3. Type Snipping Tool in Start Search box.
4. Open Snipping Tool, choose Rectangular Snip, draw a box around full map and all listings.
5, Save Snip, attach using paper clip in Reply Box.

Tell us what is on each partition. We will tell you how to correctly remove the OS you don't want.

 

[Bernardus]

You mean something like this?

This is what BCD shows There are a total of 2 entries listed in the bootloader. Default: Microsoft Windows 7 Timeout: 10 seconds EasyBCD Boot Device: C:\ Entry #1 Name: Microsoft Windows 7 BCD ID: {current} Drive: C:\ Bootloader Path: \Windows\system32\winload.exe Entry #2 Name: Microsoft Windows XP BCD ID: {2b5d8dbd-d17d-11e1-bc51-000e7f6c2346} Drive: C:\ Bootloader Path: \NST\ntldr

 

[gregrocker]

Does XP boot on its own if you unplug the Win7 HD? It does not have its own System flag so it may only be booting off the Win7 partition which is System - and should also be marked Active. Mark Partition Active

If XP booted on its own on the original system then if you include MBR and Track0 when reimaging it to the new HD, it should boot on its own there. If not you can install EasyBCD to Win7 to add XP on the Add OS tab.

To hide either OS in a Windows Dual Boot go to Computer>Properties>Advanced Settings>Startup to set default, time out, or hide an OS.

 

[Bernardus]

If I start up with the XP drive only, it's behaving normal.

If I startup with the single W7 drive, the bootmanager shows up to decide what OS I should choose.
So problems seemed to be solved so far. I can use both drives with their OS now.
It may have been the MBR after all.

Thank you for your help