|
#1
|
||||
|
||||
Windows XP PRO doesn't accept original OEM key
Hi !
Last days i manage to put my hand on 2 original OEM key for Win XP PRO. I went very happy home and wanted to install win using those keys. Guess what ... INVALID KEY. I couldn't belive my eyes as i was sure i copied them well from original licenses. So now comes a question ... posible only some builds of xp to accept those keys ? Or ... Br |
#2
|
|||
|
|||
the dvl cracked version of xp needs a winxp corp edition cd-key i think.
|
#3
|
|||
|
|||
Quote:
Little hint to find a good serial: Use your favorite search engine to find a keymaker for WinXP home/pro/corp |
#4
|
||||
|
||||
Quote:
Br |
#5
|
|||
|
|||
I assume you can install with the key that came with your version of xp pro.
The original OEM keys are tied to the disk they came with, so you won't be able to make it work with those specific keys. Or you need to install your version with the dvls key. What you need is to remove this key after you install xp and generate a new one for yourself. Hopefully this is what you want to do. That gets you a clean licensed key. Dr Pete |
#6
|
||||
|
||||
Thx ... Seems those keys are useless without the cd they came with. Damn ...
Br |
#7
|
|||
|
|||
try to use this key:
HH8PQ-P3KM8-VW2P4-QPQJG-KCBW9 it should work with windows update and stuff, atleast for a while. but i can always generate a couple of new ones. |
#8
|
|||
|
|||
Quote:
|
#9
|
||||
|
||||
...
Quote:
Br |
#10
|
|||
|
|||
There's a document available which describes how to modify the setupp.ini so that a retail windows xp pro version accepts (for example) VLK keys.
Google a bit and you will find it... |
#11
|
||||
|
||||
...
@ArC
Thx for guiding me man !!! Now i solved my problem ! For all interested how i managed that here is a short tut: Unlocking WinXP's setupp.ini (Original from wxw.thetechguide.com) WinXP's setupp.ini controls how the CD acts. IE is it an OEM version or retail? First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this: ExtraData=707A667567736F696F697911AE7E05 Pid=55034000 The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys. Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair: Retail = 51882 335 Volume License = 51883 270 OEM = 82503 OEM So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read: Pid=51882335 And if you wanted a retail CD that took OEM keys, you'd use: Pid=51882OEM Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so. best regards, .:hack3r2k:. |
#12
|
|||
|
|||
Quote:
I usually get a VLK key from a public PC with WinXP-Key Viewer. |
#13
|
|||
|
|||
Maybe this file will be useful. A lot of M$'s serials.
|
#14
|
|||
|
|||
The differences :
From my experience :
This is the all files different from a PRO and a CORP version : \I386\DPCDLL.DL_ DPCDLL.DLL \I386\NT5INF.CA_ NT5INF.CAT \I386\OEMBIOS.BI_ OEMBIOS.BIN \I386\OEMBIOS.CA_ OEMBIOS.CAT \I386\OEMBIOS.DA_ OEMBIOS.DAT \I386\OEMBIOS.SI_ OEMBIOS.SIG \I386\PIDGEN.DLL \I386\SETUPP.INI The keys uses this array "BCDFGHJKMPQRTVWXY2346789" (ie PidGen.DLL:SetupPIDGenA) setupp.ini : Pid=?????OEM => unique OEM key ProductId : MMMMM-NNN-PPPPPPP-QQQQQ MMMMM= (cf. PID=MMMMM...) NNN (640 if PID=?????270) PPPPPPP depends on S/N QQQQQ fonction of the hour ExtraData Ex: 617466716E636E6A756D9A251AC0D0 617466716E636E6A756D 9A251AC0 D0 "atfqncnjum" 9A251AC0 D0 SUM = 5D0 (so 0xD0 is a sumcheck) |
#15
|
|||
|
|||
Can you explain more clearly for each fields regarding ProductID and ExtraData??
We know that ProductID is generated based on the input ProductKey, how does this QQQQQ get generated? can give an example of its computation? And for ExtraData, how is 617466716E636E6A756D, 9A251AC0 and "atfqncnjum" related?? basic summing?? Would be very interesting to know that someone can make out what these values are for.. [EDIT JMI: You generally do NOT need to Reply with Quote unless your question is directed to a particular part of the prior post that would not be clear unless you quote a particular part. When your post is immediately after the one you are discussing, this is rearly necessary. This suggestion is made simply because "Quoting" adds volumn to the database and if your question is clear without it, it saves room if you do not quote the prior post again.] |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Why this program doesn't Unamadillo? | wili3287 | General Discussion | 8 | 02-06-2004 14:17 |