If this turns out to be a hardware incompatibility between the source PC and the target PC, I may have a workaround for you. We have found it helpful to create a duplicate hardware profile (copy Original Configuration, then rename both) on the source PC before gathering the image. By doing so, target PCs don't know which hardware profile to use; so they ask you. Choosing 'neither of the above' forces Windows to detect all new hardware. Hope this helps. tjp -----Original Message----- From: Matt Fowler [mailto:mfowler@xxxxxxxxxxxxxxxxx]=20 Sent: Monday, August 11, 2003 1:46 PM To: mswindowsxp@xxxxxxxxxxxxx Subject: [mswindowsxp] Imaging question Has anyone had a problem imaging Windows XP to a 2.4Ghz workstation? We get=20 a BSOD on boot before anything really happens. Once we do a CD repair=20 everything works normally. Thanks for any help. Matt Fowler LAN Specialist (847)925-6113 mfowler@xxxxxxxxxxxxxxx =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/winxplist.cfm ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/winxplist.cfm