excuse my innocent or rather stupid question but are these files only to make the xp cd oem or can it also be used to activate an already installed xp home edition sp2 system ?
These files are to make up oem cd if you have slp 1.0 in bios if not you can add slp 1.0 with dmi boot cd
the gigabyte oembios files aren't working for making an oem slp xp cd. the xp installer complains of errors with the oembios.si_ file and refuses to go any further.
I have an Intel D945GNT motherboard, with an intel BIOS. I notice that Intel bios's aren't listed here. Does anyone have one? Thanks.
if you acquired a pre-owned motherboard and think it might be an oem version, microsoft's own mgadiag tool will tell you whether you have any bios markers present for oe slp activation.
oembios.exe is flagged as a virus by grisoft avg antivirus. i know that this program is not really a virus and won't damage a computer, but the antivirus program insists otherwise microsoft's own mgadiag tool can find obscure oem slp 1.0 activation marker strings in the bios that the aftermarket tools won't. microsoft's tool has the advantage that microsoft wrote the operating system and has a complete list of all the oembios files that they've ever signed.
here's some interesting output from mgadiag under windows 7 xpmode. OEM Activation 1.0 Data--> BIOS string matches: yes Marker string from BIOS: 19060: Dell Inc|19060:Fujitsu Siemens Computers|19060:Gateway, Inc|17249:GENUINE C&C INC|19060:Hewlett-Packard Company|19060:HITACHI, Ltd|1904F:Microsoft Corporation|18D30:Microsoft Corporation|19060:Mitsubishi Electric Information Technology Corporation|19060:NEC Corporation|19060:TOSHIBA CORPORATION|19060:Unisys Corporation Marker string from OEMBIOS.DAT: Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593 apparently, we can oe slp activate around a dozen different manufacturer's oembios files using this data in the bios C:\Documents and Settings\XPMUser>debug -d f000:9060 F000:9060 39 62 38 30 63 61 30 64-35 64 64 30 36 31 65 63 9b80ca0d5dd061ec F000:9070 39 64 61 34 65 34 39 34-66 34 63 33 66 64 31 31 9da4e494f4c3fd11 F000:9080 39 36 32 37 30 63 32 32-5D 00 57 69 6E 64 6F 77 96270c22].Window F000:9090 73 5F 56 69 72 74 75 61-6C 5F 58 50 5F 46 39 31 s_Virtual_XP_F91 F000:90A0 36 31 44 38 45 37 46 43-43 31 31 44 44 42 46 41 61D8E7FCC11DDBFA F000:90B0 41 33 36 39 38 35 36 44-38 39 35 39 33 00 54 6F A369856D89593.To F000:90C0 20 62 65 20 66 69 6C 65-64 20 62 79 20 54 45 4D be filed by TEM F000:90D0 50 4C 41 54 45 00 00 0C-05 17 00 03 54 6F 20 42 PLATE.......To B
here's a more typical output of mgadiag: OEM Activation 1.0 Data--> BIOS string matches: yes Marker string from BIOS: 1E840: Dell Inc|197BC:Elitegroup Computer Systems Co Ltd|13F1B:GENUINE C&C INC Marker string from OEMBIOS.DAT: Dell System,Dell Computer,Dell System,Dell System the mgadiag program does have the advantage that it can decrypt the oembios files on the fly and tell you whether your oembios files match the marker strings in the bios. but this program is also a win32 application that requires a working xp installation to run. oembios.exe by contrast is an old dos based application that could be run off a boot floppy on a machine without an operating system install. C:\DOCUME~1\User>debug -d f000:e840 F000:E840 44 65 6C 6C 20 43 6F 6D-70 75 74 65 72 00 00 00 Dell Computer... F000:E850 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ F000:E860 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ F000:E870 00 00 00 00 00 00 00 00-00 00 00 00 00 00 .............. -d f000:97bc F000:97B0 42 49 4F 53 BIOS F000:97C0 4C 4F 43 4B 46 55 4E 43-54 49 4F 4E 20 45 4C 49 LOCKFUNCTION ELI F000:97D0 54 45 47 52 4F 55 50 20-20 20 20 20 20 20 20 20 TEGROUP F000:97E0 20 20 20 20 20 20 20 20-20 20 20 20 20 20 00 00 .. F000:97F0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ -d f000:3f1b F000:3F10 47 65 6E 75 69 Genui F000:3F20 6E 65 20 49 6E 74 65 6C-28 52 29 20 00 50 72 6F ne Intel(R) .Pro F000:3F30 63 65 73 73 6F 72 00 49-6E 74 65 6C 28 52 29 20 cessor.Intel(R) F000:3F40 50 65 6E 74 69 75 6D 28-52 29 20 34 20 50 72 6F Pentium(R) 4 Pro F000:3F50 63 65 73 73 6F 72 00 49-6E 74 65 6C 28 52 29 20 cessor.Intel(R) F000:3F60 43 65 6C 65 72 6F 6E 28-52 29 20 50 72 6F 63 65 Celeron(R) Proce F000:3F70 73 73 6F 72 00 49 6E 74-65 6C 28 52 29 20 58 65 ssor.Intel(R) Xe F000:3F80 6F 6E 28 54 4D 29 20 50-72 6F 63 65 73 73 6F 72 on(TM) Processor F000:3F90 00 49 6E 74 65 6C 28 52-29 20 58 .Intel(R) X
What is interesting about it? That you have modded BIOS with 10 or so SLP strings that get recognized (correctly or by chance) Do you run it by any chance on Vmware Workstation 7 (not even modded?) If so check DMI OEM entries (with ie CrystalDMI) no 11 The string you see there is the one for 19060 entries sebus
No point talking to this guy seems to know everything i,e add an Hitachi hard drive and use Hitachi oem bios files and you will activate. Poor FreeStyler and Suicide Solution 911medic jcarle and some other members from MSFN who have been doing unattended installs and writing scripts to extract oembios file information for years.
lol. i don't represent myself as knowing everything. but i also treat hacking windows xp activation as an engineering problem with multiple possible solutions. that hitachi harddrive activation hack actually works with many bioses and many hitachi harddrive models. if you happen to have a non-slp motherboard that you can't update the dmi strings on, this could be a viable xp activation method. the hitachi hack is essentially a no risk method unlike flashing a custom bios where you risk turning your motherboard into an inoperative brick. adding a peice of hardware to activate the windows operating system software isn't a new idea on this message forum either. for example: the intel pxe network card bootrom posts there are other programs besides oembios.exe that search through \Device\PhysicalMemory for a set of oem xp slp markers. i'm not sure why you insist that the only "correct" method to locate slp markers in the bios memory area is to use oembios.exe when there are other functional programs that can accomplish the same task.
i have no problem with it... please use MGAdiag if that pleases you Although i'm trilled about the fact you explained in detail how to debug SLP strings...had no clue how to do that lol One last thing, oembios.exe also exactly shows you which set(s) to use by CRC32 hash(es) Do you instantly know which set to use with MGADiag?