PDA

View Full Version : Painless HP OEMBIOS and VMWare Bios Pre-Mod


MarkMan
12-15-2007, 08:31 AM
PAINLESS HP OEM CD AND BIOS MOD KIT
===========================================

1. Materials
2. CD Preperation
3. PC Bios Modification
4. VmWare HP modified BIOS * BONUS
5. Notes
6. Thanks!

1 - Materials
--------------

* MM_HPOEMR1.ZIP - This package contains the HP OEMBIOS files and vmware premodded bios image.

http://rapidshare.com/files/102814740/MM_HPOEMR1.ZIP

* Windows XP Pro CD. You can use a Home version but you'll need to modify the SETUPP.INI file and change the pid info yourself. The kit includes a setupp.ini for xp pro.

It dosen't matter if its an OEM CD from a different manufacturer (I started with a Dell XP SP2 OEM CD myself).

* proper tools to modify the DMI of the BIOS of your PC. I have not provided the tools for this in the archive as there is a ton of information on these forums on how to do this, I will however tell you exactly what to change to make this work correctly.


2 - CD Preperation
-------------------

Real easy step here, simply dump all the files in the archive into the i386 folder and burn a CD. The oobeinfo and setupp.ini have already been modified. The matching OEMBIOS files for HP are already compressed and ready to go.

You do not need to edit any files for this to work but feel free to integrate any service packs or updates you want before or after dumping the files into i386. I used nlite and did it both ways with no problems. Overwrite the existing files of course and you should be good.

** The only way I could see you hosing this step up is if you really messed with the 'unattended' install options in nlite or manually modified the winnt.sif file yourself and nuked the cdkey or some other stuff that throws off OEM activation. I customized the hell out of my install so likely you'll be just fine.

Create an ISO or burn the disc. You now should have an HP OEM XP Pro CD.


3. PC Bios Modification
------------------------

!! I have not included tools to modify your DMI, you can get the specific ones for your bios elsewhere on these forums. I will tell you this, if you have phoenix bios then forget about DMICFG or tools of that nature as they do not work (or maybe they do and I'm just an idiot - the jury is out). You'll prob need the Phoenix Bios Editor to get the job done. AMI or Award you can use any number of the numerous DMI config utils floating around and it will probably work fine.

* The OEMBIOS files provided in this archive only need to have 1 DMI string changed and nothing else. Edit your DMI table and change "System Manufacturer Name" to 'Hewlett-Packard' including the single quotes. If you need to copy and paste it then here it is again:

'Hewlett-Packard'

THATS IT. You don't have to change the serial number, the board manufacturer name or anything else. Thats the only string that needs to be modified if you install using the OEMBIOS files I've provided in the archive.


4. VmWare HP modified BIOS * BONUS
-----------------------------------

I've seen a few posts asking about modifying vmware bios image so as a bonus I've included a vmware bios already modified with the proper DMI string change performed. I use VMWare Workstation 6.x but I believe this will work in lower versions.

Unpack the file VMBIOS_HP.ROM into the folder with your vmware config file (*.vmx).
Open [whatever].vmx in notepad and add the following line:

bios440.filename = "VMBIOS_HP.ROM"

Now boot your virtual machine, mount the HP .iso you created with the files in this kit and install Windows XP. After install you can verify its activated by doing the following:

Start > Run > type "oobe/msoobe /a" and hit {enter}

you should get a dialog stating "Windows is already activated"

Now you can install as many XP Virtual machines as you need and not have to worry about activating shiat.


5. Notes and observations
-------------------------

XP OEM activation is a freakin' cake walk as it turns out. Once you sort through all the information on the web it really comes down to some minor modifications and you are as good as gold. At least in my experience which has only been about 6 days at the time of this writing.

One interesting thing I've noticed (you can test this yourself with the vmware modded bios) is that XP checks for the manufacturer DMI at every boot. Maybe everyone knows this and I'm just some n00b moron but I thought it was an interesting discovery myself.

Do this with the vmware modded bios, install the HP OEM copy of XP you made with this kit and then shutdown, edit your .vmx file and remove the bios440.filename string from the top and then restart your VM. You'll get notified to activate in 30 days at some point, or if you do the oobe/msoobe /a command you'll get the exciting "Lets Activate Windows" dialog.

Shutdown again and re-add the bios440 string to the .vmx file and start your Virtual machine. You'll see its activated again. The interesting part about this is that basically it means you can install XP and then edit your BIOS after the fact and Windows will activate without hassle. Nice thing to know if you need to get the OS up quick and mess with the DMI in the bios later on a real PC.

6. Thanks!
-----------

Naturally I wouldn't be sh*t without all the people on these forums. I knew almost NOTHING about how this stuff works a week ago. Because of all the invaluable information on this forum I've modified my laptop bios for Vista and converted 2 XP machines into OEM activated XP installs, plus I've got a nice vmware config for running as many copies of xp as I need.

I like not screwing around with anti-wpa cracks or any of that nonsense anymore.

I thank everyone who has posted information and worked their tails off to figure this stuff out.

A BIG THANKS FROM ME! YOU GUYS KICK MUCH @SS!

Lastly if anyone has any questions about this info I've posted or has any probs with the files in the kit please let me know!

MarkMan

kenlau
12-15-2007, 05:00 PM
I tried your files testing on a VMWare virtual machine but instead use Windows XP x64. Into installation, it pop-up saying that the product key is invalid.I tried using both your key (which I suspect will not work for x64) and it did not, as well as the OEM key listed at http://technet.microsoft.com/en-us/library/bb457078.aspx.

Does anybody else have a royalty SLP product key for Windows XP x64?

Is the OEMBIOS files equally applicable for Windows XP x64?

So many factors, and I am not too sure which is the one that is affecting me.

Any help will be much appreciated.

MarkMan
12-16-2007, 05:53 PM
I tried your files testing on a VMWare virtual machine but instead use Windows XP x64. Into installation, it pop-up saying that the product key is invalid.I tried using both your key (which I suspect will not work for x64) and it did not, as well as the OEM key listed at http://technet.microsoft.com/en-us/library/bb457078.aspx.

Does anybody else have a royalty SLP product key for Windows XP x64?

Is the OEMBIOS files equally applicable for Windows XP x64?

So many factors, and I am not too sure which is the one that is affecting me.

Any help will be much appreciated.

The key on technet should be the correct one.

I'm betting the oembios files are different on the x64 edition of Windows XP.
I don't have 64bit XP to test with to confirm this but it seems a likely reason for failure.

kenlau
12-17-2007, 03:28 AM
The key on technet should be the correct one.

I'm betting the oembios files are different on the x64 edition of Windows XP.
I don't have 64bit XP to test with to confirm this but it seems a likely reason for failure.

This is where it get confusing. MSFN reported that x32 and x64 XP shares the same oembios file here (http://www.msfn.org/board/OEMScan-Automated-Multi-Manufacture-Pre-Activation-Utility-t82638.html&st=220&p=615942).

deathdr0ne
12-24-2007, 05:05 AM
Yeah they use the same OEMBIOS.* files but not the same SERIAL. Look in another post on this forum, and you will find a XP 64 bit royalty key that someone posted.

kenlau
01-03-2008, 06:37 AM
Yeah they use the same OEMBIOS.* files but not the same SERIAL. Look in another post on this forum, and you will find a XP 64 bit royalty key that someone posted.

I already tried this Royalty key FM634-HJ3QK-6QVTY-RJY4R-XCR9J that was posted in this forum, and it simply will not accept this key.

obisan
01-06-2008, 11:08 AM
thanks for this guide

grayfox
01-11-2008, 10:25 AM
Can I change those infos inside the WINNT.SIF file without throwing off OEM activation:
Repartition (I want to format the partition I will install to is this the right option?)
FullName
OrgName
ComputerName
JoinWorkgroup
I'm a noob when coming to edit this file, please help.

EDIT: This file has a redundant line so if you copy it as is into the I386 folder you will have an unusable disc. As for CD-key problem, you need an OEM edition CD for this to work. I have tried this on a retail CD and it does not work at all, it also rejects the key. It looks like OEM edition, corporate edition and retail edition all have different key pool.

urie
01-11-2008, 12:18 PM
Yes you can edit the lines in the winnt.sif

here is an example from my unattended cd

;SetupMgrTag

[Data]
AutoPartition=0
MsDosInitiated=0
UnattendedInstall=Yes

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
Repartition=No
UnattendSwitch=Yes
WaitForReboot=No
TargetPath=\Windows
KeyboardLayout="United Kingdom"
OEMSkipWelcome=1
OemFilesPath="..\$OEM$"
OemPnPdriversPath= "Drv\1;Drv\2;Drv\3;Drv\4;Drv\5;Drv\6;Drv\7;Drv\8"
driversigningPolicy=Ignore
DUDisable=Yes

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
TimeZone=85
OemSkipWelcome=1
DetachedProgram=CMD.EXE
Arguments="/C START /Wait %SYSTEMDRIVE%\Install\DrvSign.cmd"

[UserData]
ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
FullName="Urie"
OrgName="Home"
ComputerName="Computer1"

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=75

[Shell]
DefaultStartPanelOff=Yes
DefaultThemesOff=Yes

[RegionalSettings]
LanguageGroup=1
Language=00000809

[Components]
IEAccess=off
msnexplr=off
OEAccess=off
zonegames=off
pinball=Off

[PCHealth]
RA_AllowFullControl=0
RA_AllowToGetHelp=0
RA_AllowUnsolicited=0

[WindowsFirewall]
Profiles= WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
Mode=0

[SystemRestore]
CheckpointCalendarFrequency=1
RestorePointLife=7

[Networking]
InstallDefaultComponents=No

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[NetAdapters]
Adapter1= params.Adapter1

[params.Adapter1]
INFID=*

[NetClients]
MS_MSClient=params.MS_MSClient

[NetServices]
MS_SERVER=params.MS_SERVER

[params.MS_TCPIP]
DNSDomain=
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=No
WINS=No
NetBIOSOptions=0
IPAddress=88.106.15.249
SubnetMask=255.255.255.255
DefaultGateway=88.106.15.249
DNSServerSearchOrder=80.225.248.50,80.225.253.58

[Identification]
JoinWorkgroup=WorkGroup

jetman6
01-17-2008, 01:06 AM
I need the SETUPP.INI file Info for the xphome version.
Any body have the pid numbers?

Thanks
jet

urie
01-17-2008, 11:44 AM
I need the SETUPP.INI file Info for the xphome version.
Any body have the pid numbers?

Thanks
jet


[Pid]
ExtraData=786F687170637175716954806365EF
Pid=76487OEM

kenlau
03-01-2008, 02:32 AM
Just a quick note of thanks to MarkMan for his tutorial, as I was finally able to activate my XP x64!

MarkMan
03-06-2008, 07:51 PM
Just a quick note of thanks to MarkMan for his tutorial, as I was finally able to activate my XP x64!

AWESOME!

What finally solved the problem for you? Is there anything I could add to the tutorial that would help another user of x64 XP ?

Thanks! :)

kenlau
03-07-2008, 07:35 AM
Actually my biggest problem was getting hold of a copy of Windows XP x64 OEM version. As it turn out, you cannot convert a corporate version by changing the setupp.ini and copying the oembios files.

pantagruel
03-20-2008, 12:18 PM
Thanks, MarkMan. Great post. You really put it all together. I especially like the modded VMWare Bios. The only problem, is, as greyfox mentioned, the first line of WINNT.SIF should be deleted or REM'ed...otherwise it's all gold. Thanks again.

MarkMan
03-27-2008, 06:23 PM
Thanks, MarkMan. Great post. You really put it all together. I especially like the modded VMWare Bios. The only problem, is, as greyfox mentioned, the first line of WINNT.SIF should be deleted or REM'ed...otherwise it's all gold. Thanks again.

Thank you guys for letting me know. I have modified the .zip so that any new downloads will have the correct winnt.sif file now.

jobiz
04-16-2008, 11:53 PM
I have an HP 8510w running Opensuse 10.3, with VMWare Server 1.0(5) running a WinXP SP2 guest. I was having a problem installing an application in XP that came on the HP Application and Driver Recovery DVD with my laptop. I kept getting an error message that it could not install because it did not detect a "valid HP PSGN system." Out of desperation, I put the VMBIOS_HP.ROM file in my VMWare image folder. I added the "bios440.filename = "VMBIOS_HP.ROM"" line to my .vmx file. And, voila, it installed without that error. Thanks for the file!

shimman
10-13-2008, 04:58 PM
i am using virtualbox, but i could not preactivate my oem windows xp came with my laptop; would it be possible to pre-activate xp like with vmware?

thanks

MarkMan
10-18-2008, 04:21 AM
i am using virtualbox, but i could not preactivate my oem windows xp came with my laptop; would it be possible to pre-activate xp like with vmware?

thanks

Possibly, I'll have to look at Virtualbox. I have never used it, but if it contains a BIOS image like VMWare and VirtualPC (I'm assuming it does), then yes it should be possible to mod the bios in it.

yanga
10-20-2008, 07:01 AM
Odd.. does that mean, if I have my HP MCE2005 OEM CD + VMWARE Player + the BIOS from this thread, I could install the HP edition on VMWARE under linux and it would still pass wga, install SP3, etc? I've been longing for something like this as I use linux more, but for smaller things, need to get back into windows every now and then...

MarkMan
10-22-2008, 05:03 PM
Odd.. does that mean, if I have my HP MCE2005 OEM CD + VMWARE Player + the BIOS from this thread, I could install the HP edition on VMWARE under linux and it would still pass wga, install SP3, etc? I've been longing for something like this as I use linux more, but for smaller things, need to get back into windows every now and then...

If the OEMBIOS files on your copy of MCE2005 are happy with 'Hewlett-Packard' in the DMI of the BIOS, then yes it should work out just peachy for you.

simchippy
10-31-2008, 11:52 PM
Will the vmware bios pre mod work on VMware Fusion with OS X? I will probably give it a shot.