Here is for IBM WHS : Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 0062E970 5B 4F 45 4D 42 49 4F 53 5D 0D 0A [OEMBIOS].. 0062E980 42 49 4F 53 3D 65 30 30 30 2C 30 30 30 30 2C 66 BIOS=e000,0000,f 0062E990 66 66 66 2C 49 42 4D 20 43 4F 52 50 4F 52 41 54 fff,IBM CORPORAT 0062E9A0 49 4F 4E 00 0A 42 49 4F 53 30 3D 66 30 30 30 2C ION..BIOS0=f000, 0062E9B0 30 30 30 30 2C 66 66 66 66 2C 49 42 4D 20 43 4F 0000,ffff,IBM CO 0062E9C0 52 50 4F 52 41 54 49 4F 4E 00 0A 0A 5B 48 61 73 RPORATION...[Has 0062E9D0 68 54 61 62 6C 65 5D 0A 0A 48 61 73 68 42 6C 6F hTable]..HashBlo
Going out for a bit, will try IBM and Dell when I get back since they both seem to have the f000 range. offon did you get my pm?
Here the last WHS for DELL... Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 0063BF10 6F 72 6D 49 44 20 3D 20 44 4F 54 4E 45 54 5F 53 ormID = DOTNET_S 0063BF20 45 52 56 45 52 0D 0A 0D 0A 5B 4F 45 4D 42 49 4F ERVER....[OEMBIO 0063BF30 53 5D 0D 0A 42 49 4F 53 3D 66 30 30 30 2C 30 30 S]..BIOS=f000,00 0063BF40 30 30 2C 66 66 66 66 2C 44 65 6C 6C 20 53 79 73 00,ffff,Dell Sys 0063BF50 74 65 6D 00 0A 42 49 4F 53 30 3D 65 30 30 30 2C tem..BIOS0=e000, 0063BF60 30 30 30 30 2C 66 66 66 66 2C 44 65 6C 6C 20 43 0000,ffff,Dell C 0063BF70 6F 6D 70 75 74 65 72 00 0A 0D 0A 0A 5B 48 61 73 omputer.....[Has 0063BF80 68 54 61 62 6C 65 5D 0A 0A 48 61 73 68 42 6C 6F hTable]..HashBlo It's late, go to bed see you tomorrow Edit : PM ok
Gonna try with IBM and Dell here in a second by just hot-replacing the files with the ones from the other oems and rebooting. Thanks offon! Edit: Ok, I retryed with the HP files, and it works now. For some reason when I did it with the custom CD made from that build.cmd, it didnt work after install. I am going to make a new CD manually now and try with the HP files and see how it goes. This time I manually uncab'd each file, which made it work. I did the same with the IBM and Dell files. Either way, it looks like offon is right, Dell System, IBM CORPORATION and Hewlett-Packard work.
Notice that the crc's of the 2003 Dell set I uploaded are the same as the WHS Dell set that FixedBit linked to. Do they use the same OEMBIOS files as 2003? Ive had these files before WHS was even released. The crc of pidgen.dll for WHS is differnt than all the 2003 versions as well
Well I know the included oembios files for whs raw are just for "over the counter" buys from like newegg, those are keys that are not retail, just oem, but not slp oem. I notice the Dell ones are the same, I assume the IBM ones would be the same. So you may now have IBM Windows Server 2003 OEMBios files. As for HP, the ones YOU have, and the one in my pack ARE different CRC's, which was what I checked in the first place. I never checked Dell or IBM for matching CRCs. Now, my last test where it said activated for HP, I must admit in the Bios I had Dell and HP strings in there, and I had done Dell last, so the HP may have been a false positive on my part since the OEMBios files may not have erased like I thought they did and overwritten by the HP ones. As for pidgen.dll amd dpcdll.dll, yeah I would agree they are different, completely different product, I mean first of all its SBS at the root of it, and before this to my knowledge there were not OEM SBS's... Now I would be interested to know if those two DLL's matched the ones from an actual SBS disk but I still suspect they might not since MS proclaims WHS is not just "sitting on top of SBS", but a lot of undercore changed, they just didnt rebrand the version strings for some reason. I would be an interesting test to see if the WHS server componant actually installed on SBS, we know it wont on Ent and Standard but that is to be expected anyhow. You know, you would think windows would have installed them right, but NOPE, after making the SLP JUST Hewlett-Packard, and MANUALLY dropping in the oembios files, its activated off it too. Atleast we got some info out of this for WHS none the less. Now I am just waiting on more info from offon for how he got the memory dumps, then we can really be on a roll.
Na, they are differnt from all 2003 versions. I extracted SP2 for 2003 which has all versions of these files seperated into folders for each version and did crc's on them all to check as well.
Ok thanks, it was as I figured since its not billed as SBS but as WHS. I had a high doubt they would let any other keys work for WHS. Still makes me wonder why they would use a different set for HP, didnt see you having an IBM to test against. But I do not according to offon, the hp one had markers that were sort of like "uuids", or keys of some sort, that actually seems weird to me. Almost like they embedded a key in the bios instead of doing a normal SLP string.
I was hoping one of them would be slp. HP would be the set to move forward with unless some others surface. If WHS slp works like slp 1.0 then HP is alot easier to mod into a non oem board.
Oh I already confirmed that once I manually dropped in the HPQ files, the Hewlett-Packard strings installed fine within the normal range. Tried the same with Dell and IBM. It was the actual INSTALL of WHS that mucked up the oembios files somehow. This time I didnt use that "build.cmd" script but replaced the files myself. Now, will they install correctly this time... we will see tomorrow. I am also going to use that trick to set in the SLP'd key (the one included in the pack I uploaded actually works fine SLP.) I am installing the Vista/Srv08 WAIK now then going to sleep to try the edit tomorrow then do another install.
Great work, offon7544! I thought as much! It's Hewlett-Packard as well. HP used the Hewlett-Packard string at XP years ago: HP (OEMBIOS CRC=3BA155E1) CODE'f000','0000','ffff','Hewlett-Packard' 'e000','0000','ffff','Hewlett-Packard' Dell Sytem uses here a wider range than at XP. Very interesting thread