Hi. I have an untouched XP Home Retail SP0 ISO (not English). If I edit SETUPP.INI's Pid value from xxxxx000 to xxxxxOEM and use oemscan 1.4.1 with a bunch of OEMBIOS sets, it installs and activates as expected when a SLP string is found in BIOS. What if I want t use an OEM:COA key? Is editing SETUPP.INI enough, or do I need "generic" OEMBIOS files? What about Retail versions of Home SP3, Pro SP0/SP3, Server 2003 Standard/Enterprise SP0/SP2, do they also need a different OEMBIOS set after editing SETUPP.INI? Thanks for any help
COA will not activate offline to my knowledge...the OS on the macine from vendor does not even use the COA. only there for licensing purposes..
Thanks for the help. Just for curiosity, I ran OEMBIOS-VERIFICATION.cmd on the OEMBIOS set from the untouched XP Home OEM SP0 ISO and because it's not brand specific, says it's RETAIL
The OEMBIOS sets don't mean anything for phone activation. There are other files for that if I remember correctly.
Hardly surprising since Pro/ Home Retail and OEM (MS) share identical OEMBIOS files. Only one different is Vol.
Just ran CDCheck to compare Home OEM and Retail, there are only 8 different files, none of significant importance (5 help files, EULA.TXT, SETUPP.INI and NT5.CAT). Pro Retail and Volume on the other hand have 8 different files, 4 OEMBIOS.*, SETUPP.INI and NT5.CAT seem also insignificant, but DPCDLL.DLL and PIDGEN.DLL make all the difference. So, Retail + modified SETUPP.INI + OEM:COA key + phone call = Activated OEM Windows