I've spent way too much time trying to make this work and I've created about a dozen coasters in the process. The problem seems to be that sp3 integration makes the install very specific to which product keys it will accept. But I can't narrow that down since I don't have any original disks left. I work on computers for customers in a small shop that I didn't start and over the years all the originals for XP have been "lost", probably left in cdrom drives and given to customers. I have ISO's, but all of them seem to have been altered in some ways. I know this because they usually have a "Crack" folder in them. :-) I don't want to use any OS install that could have been compromised. So I recently got some ISOs with the identical MD5 hash as listed on the msdn site. I got XP Pro SP3 retail, and VL, and XP Home SP3 Retail. But almost all of my computers that I repair are OEM from large makers like HP and Dell. And none of the CD's I burn get past the Product Key section. It's always an invalid key. I've spend probably 20 hours reading everything I can find to make something work. I've tried changing the setupp.ini to OEM and that didn't work. I've used nLite on a fresh install of XP home edtion and that didn't work. I've burned the new ISO's directly with no changes and that didn't work. So I'm at a loss. Do I really have to burn a different disk for every volume label I might need? I thought the Retail CD would work on the OEM setups with the OEM product keys. Is there a straight forward guide anywhere that details how to make a working install disk that can be used on OEM computers? I really want an unattended setup with IE8 and WMP11 and Hotfixes. But at this point I'd be happy just to have a working untouched SP3 install. The "not so untouched" SP2 versions I have seem to work just fine. But when I took those same disks and slipstreamed sp3, the product key problems occurred. This was with a new version of nLite. But I can't remember if I've tried this on Windows 7 only, or with my XP machine. Even still, I don't trust these sources and would much prefer a clean source to start from. If the MSDN SP3 ISOs aren't a good starting point, where can you recommend I get clean sources from? Sorry if that's too much detail. My brain is a little scattered by the frustration of working on something that should "just work". -dav