Thanks I just used this to convert my WinXP Pro Corp (With blacklisted corp key, lol) gateway computer to a legit WinXP Pro OEM. Worked like a charm! Funny thing, is I use that old computer as my dedicated torrent box, so it's funny that its a legit box for keeping the pirate flag flying! WGA installed, no annoying popups! Thank you all for your hard work on this! I got 3 more computers that I will try this on. They are all vendor boxes, so I am sure they will all be legit after this is run as well!
Quick question, I apologize if it was in a readme or something somewhere, I didn't see anything to this extent if it was. Can you use this utility to convert a WinXp Pro Corp x64 bit version to WinXP Pro Oem x64 bit version? Or is this 32bit only? I saw that there were only like 3 OEMs that did WinXp Pro OEM 64bit, but was wondering.
Yes, they would be very much appreciated whenever you get around to it. No rush. Currently playing around with vista on here and testing out a few things. The bios mod you made me works great, if you didn't make it I wouldn't be able to be using vista now!
Ok. Here's what I have done so far to try to get back in. I made a backup of the wpa.dbl file, and copied the one from the install cd. No dice. I booted in safe mode, and then tried to run the msoobe.exe /a. No dice. In safe mode, I went to HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\Current Version\WPAEvents and changed a few digits of OOBETimer (after making a backup of the original data here as well.) Rebooted. no dice! The next thing I can think of is to try the VBS script file, and then specify the original VLK that worked. I'll try that. Beyond that, I am stumped! UPDATE: The VBS script idea for changing the product key did not work either.
Well, I think that copy of XP is hosed. I got 2 1.5TB hard drives arriving tomorrow, so it's not entirely bad timing. I'll re-install on one of them and then grab my files I need off the trashed drive. Its a little late now, but I should have tested that converter in a virtual machine from the start just in case. I even had a emulated copy of XP 64 that I could have easily torn up and then restored after wards already built and ready to go. Oh well. If you come up with any more builds of that program, I'll try them out in a VM and let you know how they went.
Run a repair install. It will fix it. or.... Copy the DPCDLL.DLL, PID.DLL, PIDGEN.DLL from your disc to the install from vista(You can do the oembios files also if you choose). You can replace them in windows\system32\ and windows\system32\dllcache I wonder if they got changed??? I am stumped as well. I have run that on a dozen installs. I will check it out.. Could you upload these files from the present install and from the cd in separate folders. I would like to compare them.... Sorry.
DPCDLL.DLL doesn't get replaced in dllcache in the :AMD section of your script. That might trigger a replacement of the old one after reboot. If the key has been changed, replacing with the old VLK files wont work. Instead copy the files from the Amd folder inside the VLK_TO_OEM.exe (Open with Winrar), to the dllcache folder and system32 folder manually from Vista. Verify that the new productkey has been applied also by booting into safemode and open regedit under the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] section and confirm that ProductId actually is *****-OEM-5111904-03160
Yes..it is all geting done. I have toyed with this for some time. The only way to be sure at this time is to replace on the cd and install. If he replaced the oembios files with the hp ones on the disc, then run a repair install it may be ok. I have tried it with and without the dllcache replacement..same problem.
That's the reason why I never made a 64 bit VLK converter, it's not needed. However, if you do have the Retail + OEM files, making a new install CD might be warranted.
Thats the only way you can. I am not sure why, I cannot find that, but you cannot change the oembios files once the install is complete. I think it is linked to the .cat file.. At any rate, the cd is easy enough to make. It has to be either a VLK or OEM install, although a repair install with the other will change the type of activation. I dont have the time or inclination to figure this out..it has no purpose..
What puzzled me was this: Maybe command line has to be different on 64 when applying the key? I don't have 64 bit to tinker with, so it's difficult to guess. I'm not at home, but what I would try is to apply the key as a readymade reg file, and see how that turns out. I would also CRC check all replaced files that they really are what they should be. This should't be a hard nut to crack. But then again,i'm firing for crows maybe, as SirSilentBob probably have a headache now, and makes a re-install instead