Page 1 of 4

OEM Activation in VM

PostPosted: Thu Aug 12, 2010 6:15 pm
by clarko71
Hi, I'm using OEMSCAN_ADDON_MULTIOEM v1.8 with great success for all my client installs - what a great tool.

I do have a problem with activation in VM's though. Currently using VM-Ware and have added "SMBIOS.reflectHost = TRUE" to my VMX file to try to get OEM activation to work, but it will not activate. I know that the product key and my install disk works when installed onto the raw hardware, just not in a VM. Odd thing is that I think I managed to get it working once by randomly fiddling around post install, but can't replicate it now.

Does anyone know (and can share) how to get OEM Activation to work in a VM - even in a different VM, I'm not fixed on using VM-Ware? I've included my log file below.

Separately - Is source code available for the tools here and how are they compiled?

Any help appreciated,

OEMBIOS autodetection script by Mr_Smartepants
v1.8.5.1 Apr 18, 2009
Do NOT pirate Microsoft software
Be certain you are installing this OS on properly licensed OEM hardware
Verify the OS type with the Certificate of Authenticity attached to this PC
Mr_Smartepants will not be held liable if YOU violate any copyright law
by installing this OS on an unlicensed PC
Windows XP Professional Edition detected
Scanning for matching XP Pro BIOS string and writing product key.
OEMBIOS Scanner v1.4.1 by Jeremy (xehqter)

Reading BIOS Memory

Matched: Dell Inc
Checking Authenticity of OEMBIOS files
OEMBIOS files pass Validation

Copying C:\WINDOWS\system32\DllCache\OEMBIOS.DAT : Successful
Copying C:\WINDOWS\system32\DllCache\OEMBIOS.SIG : Successful
Copying C:\WINDOWS\system32\DllCache\OEMBIOS.BIN : Successful

Running: D:\OEM\KEYS\XP\XP_PRO\SetKey 11111-22222-33333-44444-55555 : Successful
Attempting to move OEM logo files from "D:\OEM\Logos\Dell"

I should have luck like that

PostPosted: Mon Aug 16, 2010 10:34 pm
by Carbon Based Unit
I read and followed Mr Smartpants rules, with what should be a fairly sinple case: installing a genuine OEM XP Pro into an eMachine. But no, the invariable error message is "cannot find entries*.ini -- quitting."

This happens no matter what combination of RVMi and nLite I use. I know I've entered my data correctly and that I'm performing a legal and well practised act, but I always get the same failure message.

Meanwhile a folder containing the OEMSCAN of MrSmartepants does lodge itself into the starting lineup of folders. Is there some way to tweak that so it will work? All of my installs bring back the dreaded activation requirement.

Integrating Multi-OEM

PostPosted: Mon Aug 16, 2010 11:08 pm
by clarko71
Carbon Based Unit wrote:I read and followed Mr Smartpants rules, with what should be a fairly sinple case: installing a genuine OEM XP Pro into an eMachine. But no, the invariable error message is "cannot find entries*.ini -- quitting."

Not really an expert, but that INI file gets used by the integration tool. If you get a message saying it can't find the thing, then the end result is going to be bad.

You must use RVMI, not nLite, I think for this stuff and you must make sure that the INI file is in the root of the 7Z file you create once you've added your keys to the set.

Hope that helps...

PostPosted: Tue Aug 17, 2010 12:07 am
by mr_smartepants
Did you recompress the addon using 7-zip? Can you post your RVMi log file?
The ".ini not found" error was solved in this post:
1337 wrote:Ok, so you compressed the "filesets", "keys", "logos", and "svcpack" folders individually? Did you also compress "Entries_OEMScan_MULTIOEM.ini" as well?

11. Recompress the Entries_OEMScan_MULTIOEM.ini file and all the folders with 7zip into a single archive so that it has the filename OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8x.7 z.
12. Integrate this addon using Siginet's RVMIntegrator only. Do NOT use nLite.
13. Enjoy.

@clarko71. I don't know, I don't use vmware.

PostPosted: Tue Aug 17, 2010 12:27 am
by clarko71
mr_smartepants wrote:
@clarko71. I don't know, I don't use vmware.

Thanks for the reply - can/have you (or anyone else) got activation working with ANY virtualised environment? Am I hoping for too much?


PostPosted: Tue Aug 17, 2010 11:46 am
by mr_smartepants
I use VirtualBox, and to be honest, my builds never last longer than a week. I'm constantly making changes and testing in VM. I sometimes get VB to activate, but not often.
It's just not a priority for me.


PostPosted: Tue Aug 17, 2010 5:55 pm
by clarko71
OK, thanks. Mostly mine don't last long either, but one of the things I like to test it Windows Updates which doesn't like machines that haven't been activated.

Thanks for you efforts with this product, just wish I'd found it earlier - saves me heaps of time a mucking around!


PostPosted: Fri Aug 20, 2010 1:05 pm
by urie
Check out
Code: Select all

VMware Workstation/Player (Multi-Brand) Bios Installer

-----!!!!! ENGLISH/USA ONLY !!!!!-----
(patcher looks for English Only file directories & binres 6006 files have en/usa language ID's)

VMware W'Stn v6-7.x & Player v3.x [Windows] (Multi-Brand/Version) Bios Installer

Works on VMware W'Stn (v6-7.x) & Player (v3.x)[Windows]

This tool will auto-detect location of vmware-vmx.exe and directly patch BINRES 6006 bios file with whatever brand you select from the menu.

It works fine with older and newer versions of VMware Workstation as it disregards CRC checking of the file it's patching (x32 or 64bit).

How To Use:-

1. Make sure VMware W'Stn (v6-7.x) or VM Player (v3.x) is turned off (can't patch a file if it's in use).
2. Double-click the Installer and make your selection .... it will confirm done, seconds later.
3. VMware should now run with the bios file you selected.

Note:- on first use a "back-up" copy of your vmware-vmx.exe is made and confirmation of it's location displayed ... if for any reason you wish to return to an untouched state, you have the ability to just manually overwrite vmware-vmx.exe in your Program Files with your untouched back-up copy.

I have my own Vmware patched for dell OEM SLP 1.0 and SLIC 2.1.

Thanks for the suggestion

PostPosted: Fri Aug 20, 2010 11:31 pm
by clarko71
That looks interesting, think I'll try it out...

Not sure it's strictly legal, but my only intention is to get Dell SLP to work on Dell hardware. I hope it's not full of spyware or anything.


PostPosted: Sat Aug 21, 2010 1:05 am
by mr_smartepants
As a general rule, we don't refer anyone to "that site" because of all the pirate activity there. VirtualBox uses an .xml file to load DMI bios info for the OEM portion. I'm sure VMware does something similar.