What?
Open your eyes and read a bit!

This already is discused in this topic.... you can use ANY royalty SLP key for EVERY Royalty OEM vendor
(HP key on Dell systems, acer key on gateway systems etc etc)

...whats so hard understanding?

Another two Medion PCs (Notebooks) and a Sony VAIO VGN-FE21H.




<EDITH>
P.S.:
Anyone who can help me with the full DMI report of a Sony?
</EDITH>

mittern8
Are the Medion oembios files 100% identical? (md5 compare)

I'll check it later this evening, but from a first look I'm quite shure they're different.

Groetjes naar de Nederlands.

<EDITH>
Guess you already checked it yourself, didn't you?
THANX 4 your help with the Sony MCE!


And, here comes another one, an ACER Aspire 1310

</EDITH>

Yup, after expanding the OEMBIOS files all had the same md5 hashes (and thats good news )

@ Bezalel
Where do i add the extra line you posted a while back (to use only first 8 characters of the manufacturer hex string) in your script?


And this could easily be modded to use only the first 6 hex characters?, eg: the first 3 Manufacturer Charachters - like: HEW,DEL,MED,ACE,FUJ,ASU,IBM,SON etc etc.

Sry, I was under the impression that it wasn't legit to use say a HP SLP Key on a Non-HP System... or maybe I'm mistaken.....

Guess, if you asked MS nothing we discuss here is completely legit

Far as I'm concerned, if someone paid for the computer and it legitimately came with a royalty license then they're entitled to have the royalty version of the OS that they paid for on that computer. How it gets on there is irrelevant.

he, don't get me wrong... i agree, that's why i said if you asked Microsoft...

>discountpc: Sry, I was under the impression that it wasn't legit to use say a HP SLP Key on a Non-HP System... or maybe I'm mistaken.....
We can't be certain whether or not it's legit but I'd say not because every Royalty OEM including HP and Compaq is given different key even though it wasn't ever necessary. Mismatch keys as desired for personal experimentation but I wouldn't deploy anything wide scale or Microsoft will catch on and WGA them.

This is exactly why I requested the specific ones. So that they would stay with their respective OEM Versions instead of mismatching them. If anyone is willing to help me on this issue, please PM me.

bump

oembios wishlist:

• NEC
• LG
• Alienware

Hi bezabel

Sorry for my bad english and for my newbie question, but I am confused.
I had Samsung notebook with XP HOME.


I had copy files created by CollectFiles.rar and the files from activation.rar to the $oem$ folder of the CD.
I deleted OEMBIOS.BI_ OEMBIOS.DA_, OEMBIOS.SI_ from the CD and I removed all lines referencing any of the OEMBIOS files (including OEMBIOS.CAT) from txtsetup.sif and dosnet.inf.

I had rebuild XP HOME CD. After install this to other pc still give me to activate. What is wrong?

The contents of my $OEM$ directory is:

@pktman
The PC your installing your rebuild XP Home on has to be from the "samsung" brand to succesfully activate

PS, Can you plz post MD5 hash for your samsung OEMBIOS.BIN?

@FreeStyler

Yes, my rebuild XP Home is the samsung original.

Sorry for my ignorance, but how can I get MD5 hash for samsung OEMBIOS.BIN?

I meant,
The computer u are trying to install XP on needs to be "samsung" hardware as well
MD5 hashes can be found using (freeware) tools like HashTab

Does your other computer also report "Samsung Electronics"?
Where did you get the Key you used to install?
Do the OEMBIOS files exist in your %SYSTEMROOT%\System32 directory?
What message did you get when you tried to activate?

Hi Guys,

Another Computer Report for you:

The PC is badged as an Advent, they are made by NEC and sold in PCWorld/Dixons here in the UK.

Sorry, My other computer is not Samsung.

Can I install With samsung XP in other computer if this is not Samsung?

No, you can not...
i think you totaly misunderstood this context of this topic,
try reading it all from the beginning before asking another silly question

would someone be so kind as to post the pre-converted hex names for the respective providers?

this would greatly help me in my endevors...

thanks in advance.

I have been trying this and not having any success with an HP install. The HP machine came with XP Home installed ..drive crashed and lost all the original files and would like to create a restore disk for this machine with hotfixes and drivers.

I used an OEM Dell Home cd with SP1 as my source. Below is what i have done to the cd.

1. Slipstreamed to SP2
2. Copied over the svcpack folder and SVCPACK.INF file from an updated source so i wouldnt have to run all the integrate commands over.
3. Copied the OEM files for HP inside the I386 folder.
4. Used my custom Winnt.sif, which works fine on my retail source, with an HP SLP Home key.

Using the disk setup completes with no issues. At 1st boot all i get is the XP logo screen and then the system restarts and keeps doing this over and over.

Any suggestions?

I would do Step 3, Step 1, Step 4, and then intgrate the hotfixes. Also be sure to test your CD between each step.

Hi Randy,


I'd leave out this step, to see if everyting eles works.

Thanks guys..i kinda thought the hotfix shortcut i took might be it but wanted to see if anyone has seen the disk do that if was something else.

http://www.upline.se/download/Text2hex.exe

Hi Guys,
I'm not sure if this a warning or question.

I've read a few times in this thread that you can use a Pro OEMBIOS set on a Home install, and vice-versa.
I myself have used a my Dell Pro set to install Home on an old Dimension testbox.

Recently, I've been playing with a multi-boot disk, everything seemed fine till I tried the 'Hedy' set.
They worked with the Home install, but failed on the Pro. Has anyone else come across this problem.

I'm wondering, if its a case of the Pro sets will work on all installs, but the Home sets only work on Home.

My experiance is that the files should be interchangable. Since almost everything in the thread is based on observation and not MS documentation and I don't have (and never even saw) a Hedy PC I can't offer any more advice. If you are sure that you built the CD correctly I will add a notice in my RapidShare Directory with your observations.

This might be the case for HEDY, allthough i seriously doubt it...
Anyway i don't have a HEDY PC either, but from my own experiences with HP / MEDION OEM Media it works without issues, so either HEDY differs from the rest of the available oembios files, or maybe it is tighten to a specific serialnumber (doubt that too)

Did you use the HEDY Pro Key instead of the Home Key?

Did you install Pro and Home on two different computers? The reason is that up to 2005, most manufacturers had a single OEMBIOS.* file set for their entire line, and perhaps an extra one here or there for a wierdo model. Now some manufacturers are intentionally creating new OEMBIOS.* sets to distinguish XP product lines. You may be mistakenly thinking that your HEDY OEMBIOS set is good for all HEDY's when in it may only cover a limited set.

Check the PIDs of your Product Keys to ensure they are HEDY's Royalty OEM?

Hedy: XXXXX-OEM-0011903-00166

This is what i expected all along, this is the exact reason why i always try to use oembios files dated 2001 or so (XP without Service Pack)
In my experiences the "old" files most of the time do work on newer PC's but new (SP2) oembios files sometimes refuse to work on old PC's
Looks like the Manufactures/Microsoft have acknowledged the "flaw" in the SLP Preacvtivation are are trying to tighten the usability to use 1 set of oembios files for 1 model etc etc.

@ Bezalel, FreeStyler, Severach,
I'll explain what I was doing, which should answer most of your questions.

I was making two OEM Multi-Boot disks, one for Home and one for Pro. Each image included OEMBIOS set, the PID for that set or the Microsoft System Builder PID, oemlogo, info, wallpapers and themes [if available]
As I added each image to the disk, I tested it in VirtualPC. Which was setup to dual boot, and had the BIOS modifed with the SLP for that OEM. I know its never a great idea to test two different things at the same time, so any problems I found i.e. PID failing, wallpaper/theme not displaying I noted down so I could look i to it later and continued on with the next install.

All was fine till I tried the Hedy set. Both Home and Pro images installed fine, except the Home preactivated but Pro didn't. Which was strange as the hardware/BIOS were indentical [Dual Boot VirtualPC] I rebuilt the Pro image making sure I used the correct OEMBIOS set and installed it again, with the same results.

Now my Multi-Boot disks are complete [i think]
I'm going to test them on a real system. I'll start with the Hedy installs and report back.

NEC added

BTW, did you know the HP & COMPAQ oembios files are 100% identical?
at least mine are, (expanded) oembios.bin both have this MD5 value "3598a33c8de2e13bb3f5dbd22bc8cb76"
strange thing however is both systems have different SLP strings eg: "Hewlett-Packard" and "COMPAQ"

An OEM can have multiple SLP strings in their OEMBIOS files. This allows them to use a single image for multiple product lines.

How are you going about this? Are you using one of the dos based apps like DMI.exe, etc?

I have M$'s VirtualPC 2004, but also have the older non M$ version..which one will i need installed and if you, or anyone else, can explain the process to patch the Virtual PC bios to test my ISO's i would appreciate it.

with MS Virtual PC you can try this approach
- MMTool 2.22.1(google is your friend)
- hex-editor / ultraedit
- resource hacker

• Open Resource hacker and extract BIOS resource, the 256kb file extracted is the bios to be edited, rename it to bios.rom
• next, open mmtool "powertool" and open that bios.rom, select dmi and extract it to dmi.rom
• Open it with UltraEdit and replace the original contents, like: "Mircrosoft Corporation" , "Virtual Machine" etc etc, with the ones of your choice, save
• In mmtool use the replace function to replace the DMI with the just saved dmi.rom - save
• In resource Hacker replace BIOS, 13500 resource with the bios file saved in the step above ("BIOS, 13500, 1033")
• save and test

After renaming the 256kb resource file to bios.rom, i try to load it up with MMtool v3.12 and i always get an error saying "Error loading rom image (10007FFh)

Use MMTool 2.22.1

OK Guys,

I tested the Hedy OEMBIOS set in both Home and Pro on my test box, and both activated, I tried it on Virtual PC and again the Pro failed. So I'm guessing its a Virtual PC thing.

@ FreeStyler,
Thanks for the NEC files, and for passing on the Virtual PC info.

I got HEDY working, BIOS SLP string should read: HEDYCOMPUTER

My modded Virtual PC bios reads like this:




All SLP BIOS strings above confirmed working with the corresponding vendor OEMBIOS files, my modded Virtual PC Bios rom can be found in the attachment

This may be true on occasion but is not true in general. Dell has at least 3 OEMBIOS packs. This is how I name them with the CRC-32 of the OEMBIOS.BIN file in the name. Any CD's I generate also have both the SLP and the CRC32 printed on them. Noobs use the SLP+Nickname and I use the CRC32 to know what the coverage is.

Dell-0C706A10-Inspiron1000(SiS-2200Mhz)
Dell-263CE3FB-Common
Dell-5D93572F-New

Common covers most systems up to Pentium 4 2.5Ghz. New covers most systems from 2.0Ghz and beyond. Neither New nor Common would preactivate on the Inspiron and there are many >2.0Ghz machines that will preactivate with New but not not with Common.



The two on RapidShare are. Putting the CRC32 or MD5 in the name or description would allow you and all the rest of us to identify the dups. I'm using CRC32 myself because it keeps the names shorter and is sufficient until MS decides to generate OEMBIOS.BIN files that have different contents but the same CRC's. They won't do that even when baited because the switch to MD5 or better is trivial.

Interesting read & tools here: (if you read chinese or know how to handle babelfish, too bad the prog is in chinese)

http://www.ikown.com/html/show-id-87-page-1
http://www.bios.net.cn/Article/wzpd/BIOSJS...0060517186.html
http://www.bios.net.cn/Article/wzpd/BIOSJS...0060608978.html

"Use MMTool 2.22.1"

That did it..thanks for the info and file.

the NEC files i posted have as CRC 5D93572F
After looking through severach info, i think this isn't NEC but files who belong to DELL

@FreeStyler

Nice work with modded Virtual PC bios.

I'm using M$ Virtual Server 2005 R2 and would like to achieve same mods.

Step 3 use hexeditor to change "Microsoft Corporation" string. I would like to replace with a string (# lengh).
could i add / remove spaces when hexediting ?

I can PM you DMI.ROM file if you would like to hexedit it and attach it on the board?

What about me.

All my computers are licensed but one Forces activation.

Could you help me?

string (# lengh) ???

Think i have Virtual Server 2005 R2 laying around here somewhere

No, try reading this complete topic, if you don't get it...it's not worth telling

@ Bezalel & FreeStyler,

I've just collected the OEMBIOS file set from a new [Pro SP2] Packard bell, these files are different from the old set I sent you [Home SP0].

Do either of you want them for your collections ?

Always

BTW, I am looking for a few specific EULA's
eg:
OEM MCE2005 (Dutch)
OEM XP Home SP2 (Dutch)

Anyone here has (access to) one of these?

if i want to insert a string which length is superior to the current 'Microsoft Corporation' string length?

[off topic]
I would like to convert:
MICROSOFT WINDOWS SERVER 2003 R2 STANDARD EDITION ENGLISH VLK Media to OEM Media

I have already replaced required dlls and edit required INI file to convert it to OEM. But one error subsist during install:


I'm looking for an owner of OEM Media to get one missing file i need to replace : NT5.CAT

If you can send me this file, please write me a PM, thanks.

[/off topic]