Generic PC Windows XP Pro SP3 Activation

I have a generic system which I assume has no SLIC entry since it was assembled from parts and shipped with no OS, I've got XP Pro SP3 VLK edition, the version from MSDN (SHA1 66AC289AE27724C5AE17139227CBE78C01EEFE40). What's the 'best' way to activate it? I have been told an OEM install is best but I'm not sure that's possible with a generic PC?

Thanks a lot.

 

Wow thanks. It's a Foxconn RC4107MA-S2 according to Piriform's speccy, but the closest one that actually exists on the Foxconn site is RC4107MA-RS2.

Basically Foxconn are too poorly organised to keep track of the versions of mobos they make, so I can't be sure!

 

Does anyone have an answer for as to what version of Win XP Pro I need to use for the install to work with a tattoo'd SLP?

I currently have XP Pro SP3 VLK edition, the version from MSDN (SHA1 66AC289AE27724C5AE17139227CBE78C01EEFE40). Do I need to convert this AS WELL as tattoo BIOS? Or does someone suggest a more refined method?

Thank you.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Final Update:

Everything is working (WGA check and Win Updates). The solution in the end was to use the changer tool (in safe-mode) here: forums.mydigitallife.net/threads/6077-VLK-and-OEMBIOS-changer...

Essentially the source of the OEMBIOS files was basically the same ones I integrated into the install disc, taken uncompressed from

Code:

%windir%\system32\

and

Code:

%windir%\system32\catroot\{...}\OEMBIOS.CAT

.

I whacked these in the uncompressed oembios folder for the tool, ran it and it did all sorts of other trickery (which I assume were configuring the operating system to appear as an OEM one).

If i'm correct this answers my question as to whether or not replacing the OEMBIOS.* files in the install disc is sufficient to convert a VLK disc to an OEM one. Clearly not. But this software does what's left to do - if only it means you need to use some generic key for a VLK install first before running the tool and having your key changed back. This does explain why the OEM key wasn't working too.

Presumably, for the future the best method would be to find an OEM HP XP Pro SP3 disc, which would allow me to use that key and also mean nothing more than tattooing was necessary. Nevertheless I hope this is useful to someone who would like some assurance their original source was an official (MSDN) VLK install disc (although I haven't checked the actual routine involved in changing VLK to OEM, so I can't be sure if anything malicious has not been installed as part of that).

PS: XP feels so ancient now, bless it. <3

 

Thanks a lot for this.

Nope, was not slipstreamed, I think I state in OP along with SHA for the image I used (MSDN Pro SP3)

I didn't mean to sound accusative, I just wanted to disclaim for the most paranoid amongst us that I didn't check the individual files copied for integrity to official alternatives (as surely it is technically possible for malicious script to be embedded in the libraries that are copied)?

So I think you are suggesting now that simply replacing these files into the install disc is sufficient for the disc to appear as an HP OEM disc? Fascinating. I will create another disc with these replaced files and test.

These files, I understand that the OEMBIOS.* files are some sort of certified files proving that the install is able to be activated from the SLIC string. The others though, what is the purpose of DPCDLL used for? PIDGEN.DLL I assume generates or validates correct PID's for an OEM install? The magical jelly beans app informed me my PID did not match the installed product key. I wonder if this will cause an issue down the line, even if WGA confirms I am genuine up to this point.

SETUPREG.HIV I am guessing generates the preconfigured state of the registry. Am I on the right track here? I would be grateful if you could humour me by answering my questions as I find all this deepy interesting. Thanks again for your efforts!

 

Understood thanks for that urie. I did not replace or edit the setupp.ini file, no. I can see that there is one included in 911medic's HP OEM pack, which specifies a PID (and an ExtraData field). I suppose this reinforces my theory that where magical jelly bean reports my serial doesn't match my PID is the reason for the key failing on install. Does the installer use the PID as a reference when determining a valid serial then? I am trying to determine the absolute minimum changes I can make to the official windows ISO before an SLP activation method will work, hence all the questions.

 

Brilliant well it's all working as it should, I tweaked the winnt.sif a bit to skip EULA etc but nothing significant, still set up and installed without issue and is activated. Thanks a lot.