My winxp has been locked by microsoft, :-<

[JMI]

No actual criticism was intended by my comments. I was just generally teasing about the similiar post on Worz.net in close proximity to your's here and then gabri3l reported a sighting before Worz posted it.

We then just speculated on who may have actually made the discovery, and you had not said, one way or the other, so we didn't know whether you made the discovery or found it some place, but hadn't said. No biggie.

Regards,

[gabri3l]

Yes, please do not think I was being a smartass. You just sparked our curiosity over the origination of the list.

[c4p0ne]

Hey what if one has a key like: XXXXX-OEM-0044283-XXXXX ? Is it possible to generate with what we have?

I mean for instance, one has a 100% legit Copy of Windows XP Pro on the original CD even for good measure . The user installs this copy once, twice, OOOPS! Third time's a charm meaning Windows demands activation because as we've discussed, either things have changed "inside" the PC, or the copy has been installed "too many times during a predefined period of M$ time". Now what. Does there exist the possiblity to actually activate the damn thing with a key created by the 4in1 keygen (a key that falls completely out of the banned range)?

I highly doubt that myself (unfortunately) so then the question would be, if Windows is already asking for activation, is it possible (without physical patching of exe's) to make it believe it's been activated. As I said I've tried dosens of keys (VLK and other) generated by the 4in1 that simply wont "stick" when that update button is pressed on the windows activation dialog... All you get is "retry, retry, retry, etc.."

Perhaps I'm not generating VLK's that fall out of the banned range the right way (doubt that too) but oh well, worse comes to worst by the time this joint expires I'll have final version of Fedora to put back on this little laptop. The only reason I took Fedora off actually is cause I absolutely could not get dial-up working but fuck that who needs dial up I just take this little jammy to work and pop it on the big line.

[gabri3l]

Supposedly, and I have not personally verified this, you cannot activate with a generated key. So, if you are using a legit XP Pro OEM or retail then you need to either activate with a issued key or find a workaround to make it beleive it is activated. (example: reset5) or convert your version into corporate. A good guide to doing so is here. hxxp://homepage.mac.com/dbaumgarten/XPloiting_XP.html If you need help PM me.

I do not know why keys would not stick unless they are being generated for the wrong version. Note: Xp pro (non VLK) keys do not need to have a 640 pid. You can try to activate with a generated key and let us know how it goes.

Unless someone can 'improve' on the 4in1 KG to generate OEM keys, else U would have to stick with getting a VLK installation and key..

I've heard/seen people saying that there are chances of you generating a valid retail key that can be activated over the internet...
the PID range seems to be 011..
Like u, I can't verify it.. but it's possible.. definitely possible..

'Do I see some light bulbs blinking??''

[JMI]

zdensys:

You really didn't think you were going to get away with making two posts just because you wanted to comment on two posts, did you? Isn't going to happen. I combined your response into one.

Regards,

[c4p0ne]

Well, here's the deal. I'm not sure but I think it's fair to say there have been at least a few different "pirate" versions of the XP Pro w/ built in SP1 CD in circulation since SP1's actual realease. Therefore to better understand what I've done here you all should know that it was done with the "pirate" version of the CD which is connected to the following well-known pirate VLK key:

XK39D-3PDMC-JMMDK-X8T8M-77YVM

Now that we've got that titbit squared away, what I did basically was use that disc to create a brand new XP installation by doing a slipstream of XP Service Pack 2 Build 2162 onto the final ISO. We should note that this particular VLK circulation I'm using had a PID in XXXXX-642-XXXXXXX-23XXX <- that range.

Bottom Line:

The new installation go's through perfectly with keys generated by the 4in1. It not only accepts keys in the 640-500/640-600 range but also keys in the 642-470/642-800 range.

The big SLAP in the face-piece:

NO WINDOWS UPDATE . Forget windows update with any artificially generated key "Windows could not verify the product key". Yes it sucks elephantitis infected ballzaks I know, but all we can do at this point is hope. Either way you slice this little joint, its a BAD BAD move by M$... Can anyone guess why preventing windows updates would be bad? OF COURSE EVEN A NEW-BORN BABY FREAK could, but heaven forbid that the actual MAKERS of the damn OS can understand it. Nooo noo that would be way too much to ask.

Originally Posted by c4p0ne

...
The big SLAP in the face-piece:

NO WINDOWS UPDATE . Forget windows update with any artificially generated key "Windows could not verify the product key". Yes it sucks elephantitis infected ballzaks I know, but all we can do at this point is hope. Either way you slice this little joint, its a BAD BAD move by M$... Can anyone guess why preventing windows updates would be bad? OF COURSE EVEN A NEW-BORN BABY FREAK could, but heaven forbid that the actual MAKERS of the damn OS can understand it. Nooo noo that would be way too much to ask.

I've heard quite alot regarding WU v5 banning unknown/generated VLK..
Maybe someone can feedback WITHOUT installing SP2 after trying out
windowsupdate v5 here?

http://v5.windowsupdate.microsoft.com/v5consumer/default.aspx?ln=en-us

If this's true then we might have to use those common leaked keys..

JMI:

I'm NOT trying to boost my post by replying twices to different posts..
Just to reply to the correct posts and since the post counts doesn't changes anyway..