Jump to content
SAU Community

Recommended Posts

*************************************************************

*** OEM BIOS Emulation Toolkit For Windows Vista x86 v1.0 ***

*************************************************************

What's the purpose of this release?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Bypassing the product activation requirement of Microsoft Windows Vista x86.

How does it work?

~~~~~~~~~~~~~~~~~

Microsoft allows large hardware manufacturers (e.g. ASUS, HP, Dell) to ship their products

containing a Windows Vista installation that does NOT require any kind of product activation as

this might be considered an unnecessary inconvenience for the end-user.

Instead these so-called 'Royalty OEMs' are granted the right to embed certain license information

into their hardware products, which can be validated by Windows Vista to make obtaining further

activation information (online or by phone) obsolete.

This mechanism is commonly referred to as 'SLP 2.0' ('system-locked pre-installation 2.0') and

consists of the following three key elements:

1. The OEM's hardware-embedded BIOS ACPI_SLIC information signed by Microsoft.

2. A certificate issued by Microsoft that corresponds to the specific ACPI_SLIC information.

The certificate is an XML file found on the OEM's installation/recovery media,

ususally called something like 'oemname.xrm-ms'.

3. A special type of product key that corresponds to the installed edition of Windows Vista.

This key can usually be obtained from some installation script found on the OEM's

installation/recovery media or directly from a pre-installed OEM system.

If all three elements match Windows Vista's licensing mechansim considers the given

installation a valid system-locked pre-activated copy (that does not require any

additional product activation procedures).

So the basic concept of the tool at hand is to present any given BIOS ACPI_SLIC information to Windows

Vista's licensing mechanism by means of a device driver.

In combination with a matching product key and OEM certificate this allows for rendering any system

practically indistinguishable from a legit pre-activated system shipped by the respective OEM.

How do I use it?

~~~~~~~~~~~~~~~~

Preliminary hint:

Most operations described below require elevated privileges, so disabling UAC (Run->MSCONFIG.EXE->

Tools->Disable UAC) for the time being is recommended, Of course, it can be safely re-enabled after

all steps have been performed. Otherwise OEMTOOL.EXE and some SLMGR.VBS operations must be explicitly

run with adminstrative privileges.

1. Install the Windows Vista x86 edition of your choice without entering any product key during setup.

Basically any Windows Vista x86 installation media will do, regardless if it's MSDN/Retail/OEM/...,

MSDN/Retail are recommended though.

2. Install the emulation driver.

Run OEMTOOL.EXE, select the OEM BIOS information to emulate (ASUS might be a good choice given the

fact that it's the only OEM for which a complete set of product keys is provided :)) and hit the

'<Install Emulation Driver>' button.

Alternatively you can just right-click the ROYAL.INF file and chose 'Install' from the appearing

menu. This only allows for installing the default OEM BIOS information (ASUS) though and is strongly

discouraged unless OEMTOOL.EXE fails for some unknown reason.

When prompted about whether to install an unsigned driver, allow it.

(For some odd reason Microsoft didn't wanna sign this one...:))

3. Reboot your machine.

4. Install the OEM certificate matching your OEM selection during driver installation by running

SLMGR.VBS -ilc <OEMNAME>.XRM-MS

(e.g. "SLMGR.VBS -ilc C:\ASUS.XRM-MS" if you chose to install the default driver and extracted

the certificate file to C:\)

Note that this operation might take quite a while depending on your system, so be patient.

5. Install an OEM product key matching the installed edition of Windows Vista x86 by running

SLMGR.VBS -ipk <OEM_PRODUCT_KEY>

(e.g. "SLMGR.VBS -ipk 6F2D7-2PCG6-YQQTB-FWK9V-932CC" if you're running Windows Vista Ultimate using

the default emulation driver)

Note that this operation might take quite a while depending on your system, so be patient.

See PKEYS.TXT for a list of OEM product keys published by different OEMs.

6. Run 'SLMGR.VBS -dlv' or right-click 'Computer' and chose 'Properties' to verify your licensing status.

Due to the variety of possible combinations of different earlier Vista activation hacks we're not gonna

provide details on 'persuading' existing installations to accept this method.

During our test the general procedure depicted above worked out fine though, i.e. installing the emulation

driver, rebooting the machine and then using the officially documented ways of installing a matching OEM

certificate and product key should do the trick in all but the most messed up cases.

What's that '<Dump OEM BIOS Information>' button in OEMTOOL.EXE for?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

It dumps the BIOS ACPI_SLIC information of any SLP 2.0-enabled OEM system.

The dump can consecutively be used to emulate ('clone') that information on any other system by specifying

the 'Custom' option.

Using this function on a system booted using the emulation driver will give a dump identical to the currently

emulated OEM BIOS information, so be sure to uninstall the driver and reboot the source machine first if you

intend to dump the actual hardware-embedded OEM BIOS data.

What are all those files for?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DIFXAPI.DLL - a runtime dll for Microsoft's DIFx API used by oemtool.exe

OEMTOOL.EXE - an application for installing/uninstalling the emulation driver

and dumping BIOS ACPI_SLIC information from any SLP 2.0-enabled

Windows Vista OEM system

PKEYS.TXT - contains a list of validated OEM product keys

README.TXT - this file

ROYAL.INF - driver .INF file, can be (ab)used to install the emulation driver

in case oemtool.exe fails to perform this task

ROYAL.SYS - the emulation device driver

CERTS\ACER.XRM-MS - the certificate that corresponds to the ACPI_SLIC information

emulated by the driver when 'Acer' has been selected during

driver installation

CERTS\ASUS.XRM-MS - the certificate that corresponds to the ACPI_SLIC information

emulated by the driver when 'ASUS' has been selected during

driver installation

CERTS\HEWLETT-PACKARD.XRM-MS - the certificate that corresponds to the ACPI_SLIC information

emulated by the driver when 'Hewlett-Packard' has been selected

during driver installation

CERTS\LENOVO.XRM-MS - the certificate that corresponds to the ACPI_SLIC information

emulated by the driver when 'Lenovo' has been selected during

driver installation

and yes... it does work...

Smeh, every shop and his dog has OEM copies they can load onto any computer... we keep them here in a drawer... not that it matters... All the computers we order come with Vista on it, and they come with a handy little 2CD package to change it from Vista to Xp too :)

While confusing at first, I have that method down-pat now :D

I can see vista being Win ME all over again

- Big price drops soon after release

- Suppliers giving customers CD to remove Vista and put xp back on

- Lots of shiny crap that people dont need

- Poor performance

- Low amount of hardware supported

hmmmm......

If you have XP and need to reinstall, then you can use the repair feature (all it does is remove the windows directory and installs a new one). This means all your data will be there but your programs may not work. best to backup then start from scratch to be on the safe side.

As for Vista to XP, dunno, haven't tried to do that.

on my work PC i've got Vista business and SP1...dontcha love being a microsoft partner? Apparently its meant to fix alot of speed issues etc. Can't see the difference. Plus installing the service pack took about 30-45 minutes.

At home i got XP as it seems more stable plus you don't have to go searching for vista compatible software.

agreed vista eats dik got a quad core processor and 768 3d card and half ma games shut down after 30 mins playing... pffft vista FTL :D

ROFL.. same shiit happens to me. Got a 2.4 Duo and once the cpu runs 100% for a few seconds, pc shuts down.

Going back xp sp2 very soon.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...