thats what i did though: did repeat the process multiple times. in system it say its dell OEM, so the oem files are correct not ? but i do not get activated for some reason download your patch yesterday xp32 pro no error messages problem not finding a cat file was my mistatake; restarting the complete procedure did not help
think i see the problem after carefully reading all the posts i need B6FOEEFD.zib but sitting behind a firewall that does not tollerate torrent so im trieing to find a rapidshare version if i can so,ewhere ....
Is it possable to boot live to (Bart) PE and just replace the OEM BIOS Files: oembios.bin, oembios.dat, oembios.sig, oembios.cat And pidgen.dll, DPCDLL.DL_ From a USB stick and overwite the files in the Windows you want to convert ?
expand DPCDLL.DL_ to dpcdll.dll first. Don't forget the registry part as well. Simplest is to create a regfile with the key to be used, and merge into the correct hive with some of the tools on the PE CD.
hey dobbelina Ok well i have a problem fixing my dads laptop i have followed every instruction that you have described in your blog and for some strange reason it tells me that iam missing the oem.cat if use ur tool and on medics tool it tells me im missing oem.sig i have no idea whats going on with this i have checked my crc and it does match on one of them the acer incorporated and i downloaded the rar file that contains the 4 oem files and i still have no luck you think you can help me out i would greatly appreciate it thank you
Be sure any A/V programs or other are disabled..I cannot see why the tools give you these problems. I canno get these errors without removing a file from the folder..Strange for sure...
Hi. I registered to let you know my success with this utility. I've been given an old computer with a dodgy Window XP Pro VLK with some blocked key. I formatted and installed from an OEM Windows XP SP2 and used my legitimate key. I was going to format it again and leave it blank but I noticed that the BIOS had the "ELITEGROUP" string in the BIOS. I got the OEMBIOS files but couldn't find a key for it. The utility errored about a missing DLL but I manually ran one of the registry batch files and now it is active and genuine as an ACER even though the OEMBIOS string is an ELITEGROUP.
I now have another problem. I've installed XP Home from a RETAIL disc onto a laptop. I skipped entering a key and tried to set the OEM BIOS files for a Fujitsu (string in BIOS reported) but it still wants me to activate. It says it cannot be activated because I have not entered a key during setup. Keyfinder shows the correct key is set and the PID in system properties matches. Is there some other place I need to look it to tell activation I've now entered a key and not to ask for one? When I enter a key, the Fujistu and retail keys I have do not work! Any ideas?
Update: I've tried using the OEM BIOS files I took from the laptop before re-installing and it says it uses the Generic Microsoft key. Activating Windows asked for the key so I entered the Generic Microsoft Key as per what was read out in the getFiles script after changing it to use the original OEM BIOS files. Bear with me... Activation failed on the Generic Microsoft key but at least it thought I entered a key... Re-did the OEM BIOS files based on the Fujistu (which I tried to do in the first place) and rebooted. All active now It didn't accept the key from the COA at any stage of this. I've managed to restore my laptop with no recovery partition My tip therefore goes like this: If you install from Retail media, at least enter a key when asked. You can use your OEM Royalty after using VLK to OEM as per this thread. PS: seeing as I personally have confirmed that this tool converts XP Pro SP2 Generic OEM to Acer OEM _and_ converts XP Home SP3 Retail to Fujistsu OEM, should the tool be renamed ??
If you install from scratch, and use retail media. The easiest thing to do, would be to inject the 4 oembios files onto the install CD and edit SETUPP.INI to accept SLP keys. Then you can add the FUJITSU home SLP key to WINNT.SIF so it applies unattendedly. By using the corporate to oem convertor, pidgen.dll etc gets replaced with Pro version files. That's why the generic Pro key works. And yes,the tool definitively converts Home to OEM, although i myself wouldn't do it this way as it become somewhat of a "Frankenbuild". New name for the tool ? Maybe OEM Convertor would do... In favor of Intelligent Multicapability Operating System Validation Impactor MK2® Build 3003
The home retail to home OEM worked well in the end with no strangeness reported in MGADiag. My next task is to set my old P3 Intel motherboard to have Dell/HP string in the BIOS... but there is another thread for that