The OEMBIOS files are MS copyrighted files, such a project would probably be considured warez.

This post has been edited by Bezalel: May 29 2006, 03:58 AM

That was running through my mind, but I rationalized it by assuming the BIOS files would not allow you to install XP on a computer that it wasn't meant for. This would presumably mean Dell, Gateway, Emachines, etc. Furthermore, the key codes would not be a part of this, only the files. The other thing I thought about was the fact that people don't seem to have a crisis of conscious when it comes to distributing patched OS files - uxtheme.dll, tcpip.sys, etc.

I'm not a lawyer, but that was my take on it.

I have a set of files that worked on a Dell, HP, and Toshiba PC. I made the following changes to the CD:

I deleted OEMBIOS.BI_ OEMBIOS.DA_, OEMBIOS.SI_ from the CD (make sure you leave OEMBIOS.CA_)
I removed all lines referancing any of the OEMBIOS files (including OEMBIOS.CAT) from txtsetup.sif and dosnet.inf.
I created a winnt.sif file that included a MS Generic key http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx (Home users should use a Factory Key)
I copied the files from  activation.rar ( 55.93K ) Number of downloads: 827
to the $OEM$ directory along with the files created using  CollectFiles.rar ( 55.54K ) Number of downloads: 729

Hi Bezalel,

Sorry for the newbie question, but i got abit lost on this thread.

Do i copy the files created by the CollectFiles.rar on each of my PC's (a Dell and a HP) to the $OEM$ folder on my UAXPCD, with the files inside the activation.rar.

Then burn and run, is that correct ?

Thats understandable, I myself am figuring out this process so it keeps changing




You only need the files created by CollectFiles.rar you don't need the files contained in ColletFiles.rar (The files in CollectFiles.rar are pretty sloppy and leave behind an enviroment variable but they do work.)

Here is listing of the contents of my $OEM$ directory:


This post has been edited by Bezalel: May 30 2006, 05:37 PM

Thanx for the reply Bezalel,
I spent most of yesterday trying to collect the oembios file from the PC's around here,
but it looks like most have been formated and had clean installs. So the oembios files aren't any good.

I'm guessing i'd get into trouble asking for the files from royalty OEM's here, so i'll have to get sneaky and find them some other way to get them, before I can test this out properly.
But i'll still give it ago with the two sets I have and let you know the results.

I've got the Sony XP Pro and Compaq Home files, and I'm pretty sure i can find some Dell and HP files, its the Evesham XP Pro ones that'll be the hardest to find.

Although my method is currently working SFC is aware that the files have been changed because oembios.cat was parsed before the files were changed. If the end user ever runs SFC manually they will be prompted for the oembios files that match the origional oembios.ca_ that was left on the CD. My two question now are:

When SFC parses the oembios.cat file where does it store the thumbprints of the remaining oembios files? (I am able to delete the oembios.cat file, it is not protected but SFC still knows that the files aren't origional)

Can I run cscript.exe from DetachedProgram? (To replace oembios.cat before it is parsed.)

Presetup.cmd looks interesting but I'm trying to keep away from hacked binariess

I'm not sure about cscript.exe from DetachedProgram, but I'm sure a compiled AutoIt script would work just fine.

For about 3 months I didn't go into a certain CompUSA because I was almost caught collecting oembios files and factory keys from floor models. Its easier to get the files from a laptop because you can naturally rest you hand over your USB drive.

BTW You only need one set of files to test the CD.

I had previously kept away from AutoIt because I thought it needed a runtime to be installed. Now that you have shown me the light, I'm adding AutoIt to my collection of development tools.

I have OEMBIOS for:
Compaq - Home & Pro
Dell - Home & Pro
Emachine - Home
HP - Home & Pro
Sony - Home

ATM these are all that I have aquired...
Let me know if you need some help, I would love to have a CD that would auto determine what brand system is being used, and then use the correct preactivation files.

@ Bezalel,

I was thinking of doing the same thing here at my local PCWorld on the weekend. They already hate me in there, so it won't be a problem if the they ban me.

I've got a few sets of files now, and i've made up a UA disk.
Just gotta wait till I can Ghost the PC's, before testing it out.

@ discountpc,

I was thinking along the same lines as you, having one UA disk to cover all my OEM's
Here a list of the file set I have:
Dell: Pro & Home
Sony: Pro
IBM: Pro
Compaq: Home

I'm still working my way through old backups to see if i have,
Packard Bell: Home
Evesham: Pro
NEC: Pro

On my IBM ThinkPad T41p with preactivated Windows XP Professional SP2 OEM SLP I get this:


BTW: My unattended Windows DVD has an Installer which lets you choose which vendor files to use for preactivation. Simple as that ;-)

This post has been edited by vpn-user: Jun 1 2006, 01:33 PM

What method are you using? Do you have seperate boot directories or are you replacing the files after install?

Posting oembios file are okay, isn't it ?
A small package will be interesting ...

PM me

@Bezalel,

The numbers that make up the ID for the files, i.e. the 6F53484942412435;

Are they generated form the OS, the Hardware, or Both ?
The reason i'm asking, is most of the oembios files i've collected are from Ghost/Restore images from PC's I no longer have. Which means i don't have the ID's to go with them, so i'm at a loss as to how to name them.

I'm hoping you know the answer ito this, as it could save me a lot of messing around tomorrow, what with Ghosting/Restoring/Formating/Installing/Swearing/ Pulling Hair Out 'ing

They are named based on the system manufacturer's name as listed in the SMBIOS table. You can look through this thread to determine how different manufacturers list their name in the SMBIOS table or use the script in the first post to find the manufacturer string. The name of the file should be the same as the hex string without the spaces. (Some manufacturer's use different strings for different models, in order for the CD to work you need to use the string of the target PC.)

@Bezalel,

ooop's.. I thought the script on the first post was part of the CollectFiles.rar

Well, I spent most of yesterday messing with the OEMBIOS files, with almost total sucess
The Compaq Presario, would only work with the Compaq key. Bu the Sony, IBM and Dell all worked with each others keys.
Thanks for all your help and patients.

Heres some more PC reports if you still need them.

I replace the 4 files after install during the sysprep process using wfpreplace.exe to get around windows file protection. That way Windows is preactivated before Windows Welcome page appears.

I' m afraid each file listing is ~12MB and no, zipping them up does not save any space so I won' t post them here. I have the files for Acer, Compaq, Dell, HP, IBM/Lenovo and Samsung.