When deploying Windows XP there a few tricks you can use to do the following.

1. Have a single image for all your machines
2. Inject storage drivers offline, eliminating the need for rebuilding your image.

The areas that you may want to use unsupported tweaks for are the following:

HAL Replacement

In 2005 I wrote my first general purpose script for HAL replacement, and back in 2008 it was still the most downloaded script on the myitforum website. The most up to date script for HAL replacement (that I know of) is maintained by Michael Petersen in Denmark

Link: http://blog.coretech.dk/osdeploy/handling-hal-switching-during-xp-deployment-no-bsod-0x07-error

Handling Multiple CPU Vendors (Intel & AMD)

If you create an image on a machine with Intel CPU you quickly find that it will bluescreen when deploying it to a machine with AMD Cpu. The reason is that the intelppm service doesn't work very well with AMD Cpu's (who would have guessed  :)  ).

One workaround is to have a script detecting the CPU type, and disable that service when deploying to AMD machines.

Another method is simply deleting the IntelPPM.sys file in C:\Windows\System32\Drivers

Here is a sample script: http://www.deployvista.com/Repository/tabid/71/EntryId/26/DMXModule/396/ctl/EntryDetails/mid/396/language/sv-SE/Default.aspx

Note: If deploying via MDT 2010 and/or ConfigMgr 2007 you need to update the script to reflect the correct path of the registry hive.

Offline injections of Mass Storage Drivers

In Windows XP, injecing storage drivers offline is not supported, unless you use ConfigMgr 2007, then it suddenly is ... Mr David Ruhle has put together a nice script that does offline injection for Windows XP...

http://ruhle.wordpress.com/2009/10/20/injecting-intel-storage-drivers-into-xp-wims-via-mdt/

Updated download link to script: www.deploymentresearch.com/DRFiles/ztiwiminjection.zip

/ Johan