Generic PC Windows XP Pro SP3 Activation

Discussion in 'Windows XP / Older OS' started by deed02392, Jan 31, 2012.

  1. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    #1 deed02392, Jan 31, 2012
    Last edited: Feb 2, 2012
    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.
     
  2. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,209
    14,761
    340
    Use this to tattoo with HP SLP string; anyway what is the exact model of the mobo??
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    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!
     
  4. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    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.
     
  5. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,209
    14,761
    340
    First check with this. If it detects "HP / Compaq (OEMBIOS.CAT CRC32=CD4E1902)", then go to here. Download them.

    You can then use this to make it oem:slp activated. Or make yourself a oem:slp disc.

    :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,209
    14,761
    340
    Obviously.... :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    #8 deed02392, Feb 2, 2012
    Last edited by a moderator: Apr 20, 2017
    (OP)
  8. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    #9 deed02392, Feb 2, 2012
    Last edited by a moderator: Apr 20, 2017
    (OP)
  9. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    #10 deed02392, Feb 2, 2012
    Last edited by a moderator: Apr 20, 2017
    (OP)
    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
     
  10. 911medic

    911medic MDL Guru

    Aug 13, 2008
    5,778
    488
    180
    #11 911medic, Feb 2, 2012
    Last edited: Feb 2, 2012
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    #12 deed02392, Feb 2, 2012
    Last edited: Feb 2, 2012
    (OP)
    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!
     
  12. urie

    urie Moderator
    Staff Member

    May 21, 2007
    8,644
    3,003
    300
    When you made your cd did you replace or edit the setupp.ini file because you need to change it from VLK to OEM version that is why your key wasn't working. Also Xp use SLP 1.0 type activation oembios files match SLP string in Bios DMI area SLIC is for Vista and windows 7 activation.
     
  13. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    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. :)
     
  14. urie

    urie Moderator
    Staff Member

    May 21, 2007
    8,644
    3,003
    300
    Just use all the files that 911medic included in the HP archive that is the minimum files needed to convert VLK to OEM.
     
  15. 911medic

    911medic MDL Guru

    Aug 13, 2008
    5,778
    488
    180
    SETUPREG.HIV is not needed, but some like to use it. If there is a problem with activation, disregard it. The others are needed. I would suggest you try these iso you build in a vm environment. It is easier than wasting dvd/cd..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. deed02392

    deed02392 MDL Novice

    Nov 25, 2011
    16
    0
    0
    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.