We help IT Professionals succeed at work.

Cloning a Windows XP computer

If you are going from an older machine, say a Pentium 4, to a new athelon processor machine, is this a 100% guaranteed process to work.    Are there situations where cloning no matter how much tweeking is done, cloning doesn't work?  The reason I ask is I have a P4 that I tried to clone to an athelon box using clonezilla.     I can run in safe mode, but I can't run in normal mode with the PC.    I have uninstalled/reinstalled every driver and hidden driver.       I tried to run a windows repair install.   Same blue screen problem when I go to normal mode.

At some point, isn't it just better to rebuild the PC and reinstall the software.  

Or can every cloned machine be made to work with enough tweeking?


Comment
Watch Question

Commented:
Cloning is taking an image and putting it on the same hardware.  Dumping an image on unlike hardware is very iffy.  In this case I would highly recommend building from scratch.  You will waste so much time trying to get this to work, not to mention other issues down the road if you do.
Its never going to be a 100% success with cloning machines, as the HAL files that carry the hardware ID's will conflict with the new system. The most success that I have had with this is by using sysprep before cloning to strip the HAL's you will need extra switches though, create a notepad file in the sysprep directory and call it sysprep.inf
Then paste in all the below, you will need to fill in the section for userdata with your details

;SetupMgrTag
[Unattended]
    OemSkipEula=Yes

[GuiUnattended]
    AdminPassword=""
    EncryptedAdminPassword=NO
    OEMSkipRegional=1
    OemSkipWelcome=1
    TimeZone=85
 
[UserData]
    FullName=""
    OrgName=""
    ProductID=
    ComputerName=
      
[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60

[TapiLocation]
    CountryCode=44
    Dialing=Tone

[RegionalSettings]
    LanguageGroup=1
    SystemLocale=00000809
    UserLocale=00000809
    InputLocale=0809:00000809

[SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=whistlerdist

[Identification]
    JoinWorkgroup=WORKGROUP

[Networking]
    InstallDefaultComponents=Yes

[sysprepcleanup]

[sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]

Commented:
Some of the other users are correct.  You CAN NOT simply migrate a Windows XP computer to another machine if BOTH computers contain different motherboards, hardware, etc.

With the above said, a couple exceptions exist.  I have used an application called PC Mover to perform this painful task and it worked really well.  However, you may need to reinstall one or two programs due to hardware incompatibility issues.  But needless to say, it might save you a lot of time.

I have personally used this software so I can say it does work, even in a corporate environment:

http://www.laplink.com/pcmover

I'm not sure they offer a trial version of this software but if you need to "sample" this application, just send me a message and I can help you find something that works.
Lee W, MVPTechnology and Business Process Advisor
Most Valuable Expert 2013
Commented:
I believe you can get EVERY cloned system to work on other hardware.  It may take hundreds of hours to repair the install so that it works... and require significant skills... but I'm sure you can do it.  Is it wise or intelligent to try?  Not in my opinion.  Besides that, if your copy of Windows came with your original computer, you CANNOT clone it as it's license is likely OEM and locked to the machine it was first installed on. (Activation could then be a problem on the "new" computer once you do get it to boot).

If it's not an OEM copy, you could use products that are capable of moving between hardware configs - Acronis, for example, should be able to do this with it's Universal Restore component.
Commented:
I have always been able to do it. The issue you are having is because you are going from Intel to AMD.
Start in safe mode and open regedit. Browse to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm
Then edit the DWORD value “start” and change the value to “4¿
That should take care of it. If not, you might also have to rename the target.
C:\WINDOWS\SYSTEM32\DRIVERS\intelppm.sys
Commented:
>>> edbedb
"I have always been able to do it. The issue you are having is because you are going from Intel to AMD."


-How would you do it going from intel to intel (different hardware)?

Author

Commented:
GSXRIK... I appologize.  I thought I spread the points evenly, but I see that I missed you.   I appreciate your response and believe that you are correct.  

Commented:
@ GaryFuqua: I think you closed this a little early. Does the computer start in normal mode? Is the OS utilizing the multiple processors?
@ GSXR1K: It depends on what the problem is. Most of the time it is just a matter of having the necessary hard drive controller drivers installed.