Since Microsoft noticed that people like to keep on using Windows XP over Vista, they started to make patching (legalizing) Windows XP very very difficult. Before Vista, once you had patched your OS, you would be safe until at least the next SP. Now, after some time, the patches become obsolete and you will get the WGA / illegal software / not genuine remarks on Windows XP. Vista is left alone by Microsoft. Once you legalized Vista, it keeps on running without genuine / bad serial errors.

In some cases - and this is really bad - the patch will lead to an instable Windows! Typically, the patches that are run with a.bat script, are very dangerous. And guess which patches are used by most people. Typical, a system with older patch, gives remarks that they are 'low on system resources' (while free RAM is plenty).

Especially utorrent shows this behaviour quite a lot. Also the user interface can get corrupted. Screens will not display correctly, the shut down dialogue for example has no borders anymore and looks transparant. Even errors about 'file not found' when starting a piece of software can be expected.

Jan 11, 2008. I have only tried it on a XP Professional CD, but it should work for the Home and OEM versions of Windows XP from restore disks. I desperately need help ugrading media center edition to winxp pro sp3. No cd key is working i have tried everythin in the blog and in the unattend folders any help is. With these instructions you can change your Windows XP installation media to allow OEM, Retail, or Volume License product keys. Unlocking WinXP's setupp.ini. 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.

Rebooting fixes all these errors, for a while. Another disadvantage is that you cannot use Microsoft Update anymore. So, now you are in a pickle. Try the following.

Use RockXP4 to change your serial. Basically, if your serial gets accepted by Microsoft Update, no further patching is necessary. The problem is to find a serial that is not blacklisted. This serial works on Windows XP SP3 Pro - English AND Nederlands (Dutch, NL). I have not tried the serial on Windows XP Home. If I come across a Home machine that needs a new serial, I will repost the results.

For now, this is golden magic number for Windows XP Professional SP3: D36RK-QDFFD-BTWWY-BT7KK-43MGM (Corporate Genuine Serial) D36RK QDFFD BTWWY BT7KK 43MGM I found the serial in the following patch-all collection (XP/Vista/ 7). AIO contains a copy of XP Rock 4 too. Use that program to change your XP serial. If you download this All-in-One, please be aware.

Your antivirus might (will) alert you of strange / illegal software. It might call parts of this AIO a virus or spyware or trojan. As far as I can tell, these are 'false' positives.

I do not guarantee it tough. I have not tested everything in this release (but it looks professional and good enough for me to post it here.). Peace and have fun updating! Devvie Conare nullius momenti videri fortasse missilibus careant ------ All spelling mistakes are my own and may only be distributed under the GNU General Public License! - (© 1995-2001 by Coredump; 2002-009 by DevNullius) devnullius @ googlewave.com 11:06.

The 'magic' serial number got blacklisted on feb. But I do have a new patch for Windows XP (hare kridsnah!) that will not upset any antivir programs and just works: ) I'll repost the patch crack later. Het 'magische' serienummer werkt sinds afgelopen vrijdag. Maar ik heb, hare kridsnah, wel een patch 3 weken geleden per email ontvangen. Deze patch werkt prima, ook op Nederlandse installaties.

Ik zal patch later uploaden. Devvie On 28 sep 2009, 08:49, 'devnullius @ gmail' wrote:>7). >>AIO contains a copy of XP Rock 4 too. Use that program to change your >XP serial.

>>If you download this All-in-One, please be aware. Your antivirus might >(will) alert you of strange / illegal software.

It might call parts of >this AIO a virus or spyware or trojan. >>As far as I can tell, these are 'false' positives. I do not guarantee >it tough. I have not tested everything in this release (but it looks >professional and good enough for me to post it here.).

>>Peace and have fun updating! >>Devvie >>Conare nullius momenti videri fortasse missilibus careant >------ >All spelling mistakes are my own and may only be distributed under the >GNU General Public License! - (© 1995-2001 by Coredump; 2002-009 by >DevNullius) devnullius @ googlewave.com 09:07. Strange - the link for the newest windows 7 patch for enterprise does not work anymore??:( So I re-paste a link to this Google Group File again. Hope this one stays!:) In Dutch: de oude link naar de crack werkte niet meer - wat vreemd is, want het is een bestand in deze groep.

Ik heb hierboven opnieuw een link naar de juiste crack geplaatst - hopelijk blijft deze wel werken: ) Peace, Devvie On 20 dec 2009, 19:18, 'devnullius @ ' wrote: >On Enterprise this patch is the worst I've come across. Do not use it. >>If you did; do a repair installation from within your booted Windows 7 >Enterprise Eval version with the repair dvd. >>Once done, use this patch: >>. On 20 dec 2009, 19:18, 'devnullius @ ' wrote: >On Enterprise this patch is the worst I've come across.

Do not use it. >>If you did; do a repair installation from within your booted Windows 7 >Enterprise Eval version with the repair dvd.

>>Once done, use this patch: >>. Devnullius @ googlewave.com 00:46. First off: ALL links to files in this group do not work anymore. It is something with the files them self. Installing Cdr In Free Pbx Google Voice. I cannot download them, not even directly from the files-part of this group (). Actual reason of posting, IMPORTANT for WINDOWS 7 ENTERPRISE x64 users.

My x86 system still works fine with the last patch provided. But a friend with the x64 got the 'illegal' wga notification again: ( Using the patch again did not work - the patch became obsolete. So I upgraded Windows 7 (the new Repair update of Windows 7) and started searching for a new patch. I just applied everything, and I am awaiting the results.

One disadvantage I already found with this patch (although it might be temporary, I guess it's not) - I did not get the optional updates for Language packs. Solution here: (Windows 7 MUI (multi user interface pack) - ultimate and enterprise). The two patches I used this round are; RemoveWAT 2.2.5 (clean) 7600_RTM_v10___.exe (Suspicious for virus, but running it and then quickly re-enabling antivirus avast did not show any memory- resident baddy's.). Again; both these patches are just installed. I have to wait 2 to 3 days to know more. If anyone has a good working patch for enterprise x86/x64 - let me know.

Still, peace!; -) Devvie.

With these instructions you can change your Windows XP installation media to allow OEM, Retail, or Volume License product keys. Unlocking WinXP’s setupp.ini 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=736F696F697911AE7E05 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 = 51882335 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. A Windows product ID [currently, as of the XP Home/Pro/Server 2003 era] has the following format: xxxxx-yyy-zzzzzzz-zzzzz xxxxx-yyy-zzzzzzz-zzzzz The ‘xxxxx’ component The xxxxx section, which I will now call the “OS type”, from what I understand, determines the flavor of Windows version. Here is my current list of OS type IDs: 55274: XP Professional (Corporate/Academic) 55285: XP Professional* 55276: XP Home (?)** 55277: XP Home 51873: 2000 Professional 76487: Media Center Edition 2005 (or XP Professional Royalty OEM***) 76477: XP Home (Royalty OEM***) The current OS ID can be gotten by various methods: * If the destination computer’s operating system works well enough [even in safe mode], you can get it by right-clicking My Computer, clicking Properties, and reading the long ID number that appears under ‘Registered to’.

* You can use the command reg query “hklmsoftwaremicrosoftwindows ntcurrentversion” /v ProductID if you’re at a command prompt (CMD.EXE). * If the destination computer does not work very well, you can get it by attaching the hard drive to a working machine, and mount the hive by highlighting HKEY_LOCAL_MACHINE in regedit, and choosing File; Load Hive. Then you can surf your way to the machine’s system32configSOFTWARE hive. It will ask you what key to mount; you then give it any name you like, and it will appear under your own HKLM. You then click your way to SoftwareMicrosoftWindows NTCurrentVersion (then you will see ProductID on the right).

Don’t forget to highlight the top key of the mounted hive, and go to File; Unload Hive when you’re done! * Finally, you can actually find the ID you need [sometimes] if you check for the presence of either C:i386setupp.ini or%systemroot%i386setupp.ini. Below is a list of OEM CD keys. Use the keys to create a Dell, Compaq, IBM, restore cd that skips product registration. You will need to replace the BIOS files in the I386 and change the setupp.ini file to match the key used. For example the Dell WIndows XP Home cd uses 55277OEM.