The official blog of the Saved Content site

The aim of this blog is to collect and archive my selected thoughts, ideas, feelings, reactions, and opinions on subject matters that pique my interest. These entries represent initial drafts that may contain grammatical and spelling errors and whose substance and position could still change, and which, at some point, I could decide to put together into in-depth articles that will be posted on the main Saved Content and Poverty Sucks sites.

"God save us all from that evil Satanic Nazi, Paypal."

Transferring Windows XP to a New or Different Hardware Configuration

Posted by John Almirante on Tuesday, February 22, 2011
Topics: , , , , / Comments: (0)
Moving Windows XP to a virtual machine or a physical machine (a PC or laptop) with a different hardware configuration can cause XP to experience a blue screen upon startup.  A BSOD with a Stop 0x0000007E error code means an incompatible CPU while an incompatible hard disk controller will result in BSOD with a Stop 0x0000007B error code .

Before moving Windows XP to a new or different hardware setup, rename amdppm.sys or intelppm.sys to a different filename so that the driver won't load and cause a BSOD.  Make sure to set the SATA type in the BIOS to Native IDE or Legacy IDE since XP doesn't have built-in drivers for SATA hard drive controllers.  Watch XP boot into the desktop on your different hardware setup.

Once in XP, go to HKLM\System\CurrentControlSet\Services\intelppm (or amdppm) and change the Start value to 4. Install the correct CPU or chipset drivers and then rename amdppm.sys or intelppm.sys back to their correct filenames.