Discussion in 'Virtualization' started by lhgeek, Feb 23, 2010.
You need to login to view this posts content.
It uses Microsoft oem bios strings.
What are these bios strings?
How can I find them ?
It is possible to use them in VMware Player running in Windows Vista or XP?
All you need is:
in the.vmx file
That works only in Windows 7.
It does not work in Other operating systems.(Ubuntu)
It says the system is not allowed to run Virtual XP.
I want to find a way of activating XP mode In Vmware installed in Ubuntu.
Yes, you do use the oembios changer tool from stickies
make your mind up first Windows Vista or XP now Ubuntu the oembios changer tool from stickies only work on windows systems.
Lets put it to rest.
Windows XP Mode image WILL work as VM in any virualization platform running on ANY host OS.
If host OS = Win 7 Pro/Ult/Ent then only xpmode.enabled = "TRUE" is needed
If host OS = different Windows version from above then YOU need to have correct SLP string in BIOS of the virtualization software (for Virtualbox use this), for Vmware search the BIOS few threads down)
If host OS = differnt OS ie Linux then you need to have correct SLP string in BIOS of the virtualization software (it depends what that software is, and the way to get SLP string will be different), you might ALSO need to change the oembios set, using the mentioned changer
Be more precise, but first just read, as all the answers are already here
I want to use the XP Mode VHD extracted from the XP Mode installation file in VirtualBox ( or VMWARE player) running in Ubuntu
I checked this thread http://forums.mydigitallife.net/threads/3957-VirtualBox-SLP-SLIC?p=236932#post236932
But it did not help .
Windows XP Mode refuses to activate.
I do not want to change oembios files.
I just want to use the BIOS strings which XP Modes oembios files.
This will activate XP Mode VM or any XP install anywhere.
I just activated the XP Mode VM intended for Virtual Server on Win 7 Pro, but I did it on Vista Home with VirtualPC after extracting the vhd. This just works.
Click down to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
Modify OOBETimer to be FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD then click OK
Right Click on folder WPAEvents and choose Permissions
Click on 'System' and check Deny Full Control
You will get a warning that deny is more powerful than allow. Click OK.
You are done. Windows is activated and will pass the Genuine Advantage test so you can use Windows Update. Start>Run>\oobe\msoobe /a if you doubt me.
That is just brutal (but if it works, then why not?)
But you could just edit the VirtualPC executable with this http://forums.mydigitallife.net/threads/11547-vpc-2007-sp1-using-vpc-win-7-bios?p=175733#post175733
The SLP string for VirtualXP is simply way to long, so unless you mod the files in Linux you will NOT be able to activate, or you simply swap the oembios files (any GOOD reason you do not want to?)
This does not work.
Even though msoobe /a shows Windows is Activated,after 30 days,I get message saying "This copy of Windows must be activated with Microsoft before you can logon.Do you want to activate Windows now?"
When I click yes msoobe /a is executed which says Windows is already activated.
When i click ok i am taken back to the login screen and when I try to login i get the first message.it is an endless loop.
So just follow my advice above
How do I mod VirtualBox files in Linux?
Editing the xml file with the SLP string is not at all helping.