Windows XP Mode OEM Key

You need to login to view this posts content.

 

In the WGA output above the string used was:

<SLPBIOS>Windows_Virtual_XP_F9161D8E7FCC11DDB FAA369856D89593</SLPBIOS>

So the OEMBIOS file set seems to be a one off for the default Microsoft SLP string
inside the Virtual PC bios.
Modding a Virtual PC bios with a common string like "HP Pavilion" and using
the matching OEMBIOS files will activate it the same way. Didn't know
anything about that SLP key for it however.

 

Will that string fit in the slp bios "field" ?
ie: Andy's tool

 

Not sure, but that is not really needed anyway. The real benefit of these OEMBIOS files is
that we wont have to mod the Virtual PC bios to have OEM SLP activation for a XP install.

That string is already included inside the Virtual PC bios. If you wanted to use that new
key on a normal PC, it should work with any common Pro OEM SLP install that only needs a
single DMI string like Hewlett-Packard which we all know will fit.

 

I knew i did exactly the same as SirSilentBob, pulled the files & key from XP Mode install

 

As one of my PCs does not have Virtualization (Atom 330) available, I can not run Virtual PC, but Virtual PC 2007 runs OK on Win7 Ultimate
Tried (for fun) the XP mode image in Virtual PC 2007 & after mounting XPSP3 iso (as it was missing few files - I hope that does not happen when running in a proper way, some people would be surprised...) it works just fine, but... NO ACTIVATION

MGADiag gives the same SLP string as in post one, but still 30 days left for activation

sebus

 

As far as i know Virtual PC 2007 SP1 does not contain the SLP String

 

Running MGADiag gives same output:

While if I use my modded VPC 2007.exe with BenQHub (and corresponding oembios set) then I get:

and that instance of Windows XP activates OK

I see no difference between output in post 1 (Virtual PC RC) and mine (Virtual PC 2007), so I can not understand why it does not activate

sebus

 

the string "Windows_Virtual_XP_F9161D8E7FCC11DDB FAA369856D89593" is read from oembios files, you still need to mod that string into the VPC2007 executable as well. In the new XP mode this string is included, in VPC 2007 it is not

 

Thanks, that makes sense..., but why does it say: BIOS string matches: yes?

sebus

 

You need to login to view this posts content.

 

Thanks again, that also answered my question about Hyper-V in Windows Server forum

sebus

 

You need to login to view this posts content.

 

I did not try on any physical PC, but in Virtual PC 2007 BIOS it fits in DMI (module 06)
On physical PC (if it were to work) you do not need Andy tool, but DMI utilities for your mobo

sebus