I'm gonna have to give this one a try, sounds a lot simpler than XPLIC, but so far i haven't been able to xfilz utility to work, but i am still open for new ideas Next machine that needs a conversion, this will be top of my list Thanks dobbelina, definitely two thumbs up (unfortunately there is only a one thumb icon for the post)
Vlk_to_oem This is an interesting tool but allow me this question: I have a German Corporate XP and, according to your directions, I have to put pidgen.dll and dpcdll.dll from a retail version in the same directory as VLK_TO_OEM.exe. Well, with pidgen.dll it is OK but dpcdll.dll is compessed in the Retail CD. How can I overcome this? Thanks for your attention.
I updated the VLK_TO_OEM.exe file today. Some improvements. You don't need to extract oembios.exe anymore as i made that into an option when executing. (to check bios string) It now also checks for the presence of the 4 oembios files before running, or else it aborts. This prevents "dryruns" that could otherwise screw up your system.
Don't worry about my toes, i wear steel boots He he, only joking. I like the fact that both our executables are Winrar compressed batch files, That way one doesn't need to worry about any hidden nasties. Also it gives the opportunity to see "what's cooking" so that we can learn/improve the tool. Copy DPCDLL.DL_ to the root of C: open Command Prompt and type: cd .. (Enter) cd .. (Enter) expand DPCDLL.DL_ C:\dpcdll.dll (Enter)
I updated the VLK_TO_OEM.exe file today. Some improvements. It now reads the Product Code from the Pid in your registry and adds it to your ProductId with the generic OEM serial.(The first 5 digits) This is really good, as you then retain the platform, build, and version of the original.Language specific etc... (Don't confuse this with channel id, as that is what we are changing) Did some attribute changes, just in case somebody has system attributes on the oembios files. As default they shouldn't have that, but if they do, it screws things up. So it's fixed. Footnote: It now works so well, i'd use it on any system(My own) blindfolded Have done some extensive testing in VMware trying to screw things up bigtime, it's difficult, believe me. Even though MGADiag.exe gives me some strange readings, it ALWAYS passes validation without a hitch. I've put a lot of effort into making it compliant with all versions, and more important all languages. For that specific reason it now creates the regfile "on the fly", reading your Pid, getting as close as possible to the original settings, without interfering with activation. Now i'm gonna drink a beer or 5, so i'm "off the hook". Goodmorning and goodnight
Will this utility also input the oem hp key for me , because i don't have the key only the bios file sets and i am unable to activate using xfilz utility .But my bios has the 4 codes necessary for slp 1.o activation.However i haven't tried your utility , i going to try it quite soon. thanks.
I updated the VLK_TO_OEM.exe file today. Some improvements. You can now use unexpanded files copied directly from a CD. My utility automatically detects them and expands them before conversion. Remade Yes/No into option tree. More logical, with added "Download files" option. I think i'm about done with this app now
@dobbelina Thanks for helping me out since i have got my xp activated. the generic ket that your app installed didn't work for me but the keys that urie provided me worked. Thanks.
Thanks for feedback. Nice to know it works well on foreign versions. (and it should) All feedback is welcomed.
Are you serious? Well, the only two I had got blacklisted and the ones I generated w/ keygen to try and find a good one....well, I got tired after trying 50 different keys which were all blacklisted.