xehqter

Could it be possible this is due the fact it should read a blank space before the first character? Like: " FUJITSU SIEMENS" [fs] I tried test #1 with and without a space, it made no difference until I added two instances of FUJITSU SIEMENS. Since MGADiag only reports the first 4 strings, how are we coming to the conclusion that the gateway bios has 23 instances of the word gateway? BTW, I didn't test the strings in the DMI section of the bios, I used VirtualPC and added them at offset 0x1397A of the Single Link Arch Bios ROM with MMTOOL and WinHEX

Hmm, the SLP from MGADiag with A04597C6 is 'Gateway, Gateway, Gateway, Gateway' but putting it in the bios 4 times doesn't pass activation..

I inserted the following strings into the bios to and used MGADiag to see if they pass, here are the results. CRC32: E161F004 SLP: " FUJITSU SIEMENS, FSC SYSTEM, FSC SERVER, FUJITSU SIEMENS" Test 1: "FUJITSU SIEMENS" - FAILED Test 2: "FUJITSU FUJITSU" - FAILED Test 3: "FSC FUJITSU" - FAILED Test 4: "FSC SERVER" - Genuine Test 5: "FSC SYSTEM" - Genuine Test 6: "FUJITSU SIEMENS FUJITSU SIEMENS" - Genuine Test 7: "FUJITSU FUJITSU SIEMENS SIEMENS" - Genuine Test 9: "FUJITSUSIEMENS fujitsu siemens" - Genuine Test 8: "FUJITSUSIEMENSfujitsusiemens" - FAILED Test 9: "FUJITSUSIEMENS fujitsusiemens" - FAILED FUJITSU SIEMENS x 2 Works FSC SYSTEM x 1 Works FSC SERVER x 1 Works Interesting results BTW: E161F004 is listed with the wrong SLP <SLPBIOS> FUJITSU SIEMENS, FSC SYSTEM, FSC SERVER, FUJITSU SIEMENS</SLPBIOS>

new version bump..

New version of my OEMSCAN utility. http://www.msfn.org/board/index.php?showtopic=82638 Thanks for telling me about the KeyUpdateTool severach. The new version passes WinTrust. Per request it now supports per-oem commands so you can write a script to copy over oem specific files (ie:oembios.bmp) . You can also use OEMSCAN to run scripts for a specific OEM without copying over the OEMBIOS files. All kinds of fun stuff.

I’ll work on it over the weekend. Currently the copied OEMBIOS files fail WinTrust. I’ll add a parameter to run a program/script for each OEM. That way you can copy/run whatever OEM specific files over that you want. I plan on open sourcing it since I have no intention of maintaining it once all the bugs are worked out. If I remember correctly it returns a value of -1 if there is no match and 1 on a match.

create a text file called cmds.txt with S F000:0000 FFFF "OEM" Q then run debug < cmds.txt > output.txt output.txt will have the matches. I use the Windows API to read that portion of memory, but this should work too.

My App replaces both the system32 and dllcache versions, you aren't prompted for the CD unless you manually run SFC /SCANNOW

@FreeStyler Sorry, I should correct myself. It searches through the range.. 0xF0000 – 0xFFFFF I said F000:0000 to infer debug –s F000:0000 FFFF “OEM”

@FreeStyler I didn't test that but I’m sure it fails since I don't have any provisions against it. I'm not sure how to go about disabling 'sfc /scannow' besides modifying SFCFILES.DLL. Do you have any idea’s?

With the information from Bazalel and FreeStyler I wrote OEMScan, It scans the bios (F000:0000) for a SLP string and if found disables Windows File Protection then copies the OEMBIOS files to their respective locations. I've tested it using the svcpack method and normal execution in windows. Check It Out http://www.msfn.org/board/index.php?showtopic=82638 Jeremy

OEMScan v1.4.1 OEMScan automates multi-manufacture installation Windows XP/2003 CD's by scanning the bios (0xE0000-0xFFFFF) for a Royalty OEM's SLP string and copying over the appropriate OEMBIOS files for windows XP activation. Features: 1. Scans BIOS Memory for a specific string within a customizable range. 2. Validates the OEMBIOS file set by checking the BIN/SIG/DAT hashes against the CAT file. 3. Can run a program/script and pass a custom argument for each OEM allowing you to further customize the installation. 4. OEMBIOS files pass Microsoft’s WinTrust Validation when copied over. New/Fixed in 1.4.1 Added more descriptive error messages (File Missing) & Dry Run Warning message Changed Copy/Import order, Imports CAT first, copies second. Fixed Bug CMD would still run if OEMBIOS files are corrupt Fixed Bug Dry Run would copy files. New in 1.4.0 Windows 2003 support For OEMBIOS files and SLP ID's check out Bazalel's OEMBIOS repository: http://www.oembios.net For Multi-Manufacture Activation Discussion http://www.msfn.org/board/index.php?showtopic=71016 oemscan_v1.4.1.zip