Ghost Image Deployment of XP on NewPC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello Everyone

I have Windows XP Pro plus other applications on my old PC. I purchased a barebone pc with came with a New larger hard drive. I created a ghost image of my partition to transfer over everything to the new hard drive. So, now I got my new system, and I restore the image fine in 25 Minutes!!! Im thinking this is Great! So, I fire up the system..I see the Windows XP boot screen for a sec..then it reboots..over and over...

So, Im thinking maybe there is something wrong with image...so to test I pop in the new larger harddrive in my old system and it boots up fine. Someone told me if you have a new motherboard, that this does something to the windows activation protection scheme or something...

Going on that advice..I inserted my Windows XP Pro with SP1 CD into new system and chose to repair installation.....pc booted back up...and I loaded Windows XP...but now all my shortcuts...settings..etc are all gone.....

So, how can I get my image to work in that new pc...withought having to put my old motherboard in it, or Repairing Installation essentially loosing my settings

Thanks for anyhelp
 
TCWho,

You may want to look at using the Files and Settings Transfer wizard as an
alternative to Ghosting your hard drive. If you're only worried about a few
files, but mostly about all your settings, this is the tool to use.

On the other hand, if you do want to ghost your hard drive to your new
machine, this is what you should do:

After you ghost your files onto your new computer, boot to the Windows XP
CD, and do a repair install. Skip the first option to repair, and let Setup
detect the Windows installation already on the drive. It will ask if you
want it to repair that installation, make sure you choose to let it do that.

I know you said you already tried this, but it shouldn't kill your
settings - I'm not sure why it did that.

There's another thing to try, but it's a bit more advanced, and has it's own
problems. Let me know if this works - if not, we'll talk about the other
option.

--
Mike Kolitz MCSE 2000
MS-MVP - Windows Setup and Deployment

Remember to check Windows Update often,
and apply the patches marked as Critical!
http://windowsupdate.microsoft.com

Protect your PC!
http://www.microsoft.com/security/protect


TCwho said:
Hello Everyone,

I have Windows XP Pro plus other applications on my old PC. I purchased a
barebone pc with came with a New larger hard drive. I created a ghost image
of my partition to transfer over everything to the new hard drive. So, now
I got my new system, and I restore the image fine in 25 Minutes!!! Im
thinking this is Great! So, I fire up the system..I see the Windows XP boot
screen for a sec..then it reboots..over and over....
So, Im thinking maybe there is something wrong with image...so to test I
pop in the new larger harddrive in my old system and it boots up fine.
Someone told me if you have a new motherboard, that this does something to
the windows activation protection scheme or something....
Going on that advice..I inserted my Windows XP Pro with SP1 CD into new
system and chose to repair installation.....pc booted back up...and I loaded
Windows XP...but now all my shortcuts...settings..etc are all gone......
So, how can I get my image to work in that new pc...withought having to
put my old motherboard in it, or Repairing Installation essentially loosing
my settings.
 
You have overlooked one of the basic 'anti-priacy' features of XP. For a start if your old PC came with an OEM and not full retail version of XP it is contrary to your EULA to move the system disk or reinstall windows xp onto a new or upgraded system

If you have a full retail version and plan to move the hard disk [by physical transfer to another system case / motherboard etc] or ghost the disk and move the ghosted disk to another PC then you should observe the following proceedure

I would strongly urge you to use the ghosted disk when attempting this process: that way if you make any mistakes you will have your original and fully operational disk available to begin again

If you upgrade your motherboard on your Windows 2000 / XP system or tried to move the hard drive to another computer, you may have received the following error message 'STOP: 0x0000007B INACCESSIBLE_BOOT_DEVICE '. This is because the hard drive does not contain the drivers for the hard drive controller for the new motherboard

If you are using a SCSI drive subsystem, usually you can install the target disk controller in the old system and install the drivers for the controller. You can then move the controller and the hard drive to the new system, boot, and remove the unused drivers

For IDE systems, it is a little more complicated since the IDE hardware is usually integrated on the motherboard itself. When Windows installs, it detects the IDE controller and only installs the driver for the detected hardware. When you upgrade the motherboard or move the hard drive to a new computer, Windows will not find the correct drivers installed. This article will show you how to install the correct drivers so that you can move the hard drive

If you are interested to find out which drive controller Windows detected, look in the file \WINNT\setupapi.log. Before you begin this procedure, please have a good backup of the current system

1. Boot the system using the hard drive in the old system. Copy the following text into a file and call it copy.reg

Windows Registry Editor Version 5.0

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="atapi



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="atapi



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="atapi



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="atapi



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk

"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}

"Service"="disk



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="pciide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]

"Service"="pciide"

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]

"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

"Service"="intelide"



;Add driver for Atapi (requires atapi.sys in drivers directory)



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]

"ErrorControl"=dword:00000001

"Group"="SCSI miniport"

"Start"=dword:00000000

"Tag"=dword:00000019

"Type"=dword:00000001

"DisplayName"="Standard IDE/ESDI Hard Disk Controller"

"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\

00,73,00,79,00,73,00,00,00



;Add driver for intelide (requires intelide.sys in drivers directory)



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]

"ErrorControl"=dword:00000001

"Group"="System Bus Extender"

"Start"=dword:00000000

"Tag"=dword:00000004

"Type"=dword:00000001

"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\

00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00





;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]

"ErrorControl"=dword:00000001

"Group"="System Bus Extender"

"Start"=dword:00000000

"Tag"=dword:00000003

"Type"=dword:00000001

"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\

00,2e,00,73,00,79,00,73,00,00,00

Im my experience, you need to copy the whole thing even if you think you know the target driver.



2. Extract the following files from \winnt\system32\i386\driver cache\i386\driver.cab and put them into the \winnt\system32\drivers directory: atapi.sys, intelide.sys, pciide.sys, and pciidex.sys. If the directory contains other cab files for service pack 1 (SP1.CAB) or service pack 2 (SP2.CAB), get the files from there instead so that you are using the latest files.



3. Right click the copy.reg file and select Merge to add it to your registry. Confirm all prompts.



4. Move the hard drive into the new system and reboot. You should be able to boot normally.
 
Hello Everyone and Thank to Everyone In These Forums. You guys are really fantastic for helping all of us out. It is appreciated

I followed your directions, and it worked JUST AS DESCRIBED! This is a Full Retail Version in question. This was very convienant...Ghost is a True Program to keep handy...It saved me the time of having to re-install all my software, download all patches, AV defs,etc

I have another machine with an OEM Version of XP, I had read before that if you attempt anything similar, that when the system boots into Windows XP, that you are prompted to call MS to purchase license and you are given 30 Days...Is this true? Am I literally forced to keep my machine the same on the OEM Version of XP (XP HOME -- Kids Machine)....or can I accomplish the same task that I did with my Machine running Retail XP Pro with SP1

Thank Again Everyone
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top