Bruce said:
Can you point me at references for making the changes you
referenced in SETUPP.INI, including incorporating service packs? I
ran into one recently who's CoA was XP prior to the change to SP2.
He had purchased the PC 2nd hand w/o any mfg. CDs.
Now is a great time to point you to one of the easiest ways to find
information on problems you may be having and solutions others have found:
Search using Google!
http://www.google.com/
(How-to:
http://www.google.com/intl/en/help/basics.html )
Example:
http://www.google.com/search?hl=en&q=setupp.ini
The first link would allow you to change a CD's ability to accept OEM/Retail
keys.
http://www.thetechguide.com/howto/setuppini.html
Now - I am guessing you are speaking of some machines that have what is
known as "SP2c"?
(When you say, "who's CoA was XP prior to the change to SP2"...)
http://oem.microsoft.com/downloads/public/seo/winxp_sp2c.htm
As far as I can tell - this does not affect your original question. You
asked about Windows XP Home Edition - Windows XP Home Edition never was
released in SP2c versions - so there wasn't a unique CD for Home Edition
that only accepted these "SP2c only" keys.
If you are not referring to that - I have no idea what you are speaking of.
AFAIK - Windows XP Home Edition product keys are universal down the line -
meaning that a Windows XP Home Edition RTM OEM product key will work with a
Windows XP Home Edition SP3 OEM CD or a Windows XP Home Edition SP1 retail
product key will work with a Windows XP Home Edition SP2 retail CD or a
Windows XP Home Edition SP3 OEM product key will work with a Windows XP Home
Edition RTM OEM CD... I have installed machines that came to me with 2002
and 2008 product keys and CoAs (OEM and retail, Windows XP Home Edition)
using the method I described earlier for the product key acceptance
(SETUPP.INI changes.) In all cases - I had already integrated the latest
service pack into my copy of the CD before I did it - to save time in the
long run.
Now - maybe people have ran into exception - but I have not. I have seen
OEM CDs that were *not* generic - so those could not be used for the process
I am pointing out. They had been modified by the OEM to only work on
*their* product line or even a specific model, etc. (Although that could be
removed.)
As for integrating/slipstreaming service packs (and other patches) into a
Windows XP CD, there are many references to that.
http://www.google.com/search?hl=en&q=slipstream+sp+into+Windows+XP+CD
You could use nLite, Autostreamer or some other tools. You could follow one
of the many web pages out there (like unattended.msfn.org) to not only
slipstream SPs, but other patches and even applications.
It'd take a little effort - but at this point in the Windows XP game - you
could likely make quite a few different CDs from one original that accept
Retail and OEM product keys for Windows XP Home Edition and have SP3 and all
critical patches through now integrated and you wouldn't fall too much
further behind (considering the life cycle of Windows XP Home is closer than
most to an end.)