Bezalel

Multi Manufacturer Pre-Activation

554 posts in this topic

>Test 1: "FUJITSU SIEMENS" - FAILED

>Test 7: "FUJITSU FUJITSU SIEMENS SIEMENS" - Genuine

>Test 9: "FUJITSUSIEMENS fujitsu siemens" - Genuine

I don't see how Test 1 could fail and Tests 7 & 9 could succeed. Ignoring the superflous data which confuses the humans but not the computer, in all these cases a specified string occurs exactly once. Test 9 has a less desirable case though case doesn't seem to matter.

>FUJITSU SIEMENS x 2 Works

According to Tests 7 & 9, FUJITSU SIEMENS x 1 Works too. Don't let your eyes fool you into thinking that the extra text has meaning.

Could it be possible this is due the fact it should read a blank space before the first character?

Like: " FUJITSU SIEMENS"

[fs]

Edited by FreeStyler
0

Share this post


Link to post
Share on other sites

Guys, I am totally confused now. Do we really need 'Gateway,Gateway,Gateway,Gateway...etc' in oemscan.ini? I mean:

[Gateway,Gateway,Gateway,Gateway...etc]

PATH=".\Gateway\"

CMD=".\Gateway\copy.cmd"

:wacko:

Or is it enough to do a

[Gateway]

PATH=".\Gateway\"

CMD=".\Gateway\copy.cmd"

:blink:

@Bezalel: I am asking about the rapidshare folder because you are also missing some common files. At least "Acer Travelmate" notebooks are sold very well and widely spread but your repository misses the files.

0

Share this post


Link to post
Share on other sites
Guys, I am totally confused now. Do we really need 'Gateway,Gateway,Gateway,Gateway...etc' in oemscan.ini?

the answer is NO you don't have to add them all (for now)

But i suggest to let the coders here do their thing, as you could have read some are investigating the possibility to "fix" the bios ranges to scan.

@Bezalel: I am asking about the rapidshare folder because you are also missing some common files. At least "Acer Travelmate" notebooks are sold very well and widely spread but your repository misses the files.

I'm sure he updates his RS folder as soon he has the time

0

Share this post


Link to post
Share on other sites

Please excuse my bad English, I don' t have always the right words to say what exactly I mean. I don' t want to stress anyone in here! You guys have done GREAT work and I really appreciate it. It' s just not everything that clear to me because I didn' t code these tools here so I just wonder how exactly I have to use them.

I am working on a universal unattended DVD and only have an IBM ThinkPad machine for OEMBIOS testing and it works for that machine. But I can' t test other vendors so I just have to use the right information.

0

Share this post


Link to post
Share on other sites

>Test 1: "FUJITSU SIEMENS" - FAILED

>Test 7: "FUJITSU FUJITSU SIEMENS SIEMENS" - Genuine

>Test 9: "FUJITSUSIEMENS fujitsu siemens" - Genuine

I don't see how Test 1 could fail and Tests 7 & 9 could succeed. Ignoring the superflous data which confuses the humans but not the computer, in all these cases a specified string occurs exactly once. Test 9 has a less desirable case though case doesn't seem to matter.

>FUJITSU SIEMENS x 2 Works

According to Tests 7 & 9, FUJITSU SIEMENS x 1 Works too. Don't let your eyes fool you into thinking that the extra text has meaning.

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

Edited by xehqter
0

Share this post


Link to post
Share on other sites
Please excuse my bad English, I don' t have always the right words to say what exactly I mean. I don' t want to stress anyone in here! You guys have done GREAT work and I really appreciate it. It' s just not everything that clear to me because I didn' t code these tools here so I just wonder how exactly I have to use them.

I am working on a universal unattended DVD and only have an IBM ThinkPad machine for OEMBIOS testing and it works for that machine. But I can' t test other vendors so I just have to use the right information.

I think that is what everyones problem is. That's why we all have to work as a team. We don't all have access to every computer so we need everyones help. I think I'll put together a new tool that will help output some vital info that we need. Since the project has significantly changed in the way it finds the system info. For the most part the project will work fine. It is mainly the Gateway filesets I am concerned about. It is not very possible for us to use both filesets right now because we have no way to differentiate them when checking the system. So I would recommend everyone use the Gateway-Emachines fileset to give you the best so far. But if you have a Gateway System that fails we need you to get the debug info. That also goes for any computer that fails when you feel like you are using the correct filesets. It is possible that some of these filesets are very specific to where they search for the strings. I want to make a tool that not only finds the correct manufacturer of a system but also will scan the computer for the debug info we need. That way when people post info here we will have a better outlook on what we should actually be searching for in the bios. ;)

0

Share this post


Link to post
Share on other sites
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>

All the Fujitsu Seimens SLP String have a space at the beginning of the sting. You may have gotten lucky with tests 4 and 5 and already had a space in the prevois byte. (If you didn't have a space I'd like to know what charcter was in that byte.)

0

Share this post


Link to post
Share on other sites

@Bezalel

The previous character was CRLF so 0x0D, 0x0A, FSC SERVER, 0x20, 0x20, ....... 0x0D, 0x0A

0x20 being SPACE.. perhaps it was reading all the spaces after the string.. hmm..

Edited by xehqter
0

Share this post


Link to post
Share on other sites
Gateway 2000 using A04597C6 OEMBIOS files

S F000:0000 FFFF "Gate"
F000:4E54
F000:4E70
F000:4ED5
F000:4EF1
F000:4F45
F000:E840
F000:FFC0

DMI Information:
F000:4E50 04 00 C3 19 47 61 74 65-77 61 79 20 00 FF FF FF ....Gateway ....
F000:4E60 FF FF FF FF FF FF FF FF-FF FF FF FF FF FF 00 19 ................
F000:4E70 47 61 74 65 77 61 79 20-32 30 30 61 72 63 20 00 Gateway 200arc .
F000:4E80 FF FF FF FF FF FF FF FF-FF FF 00 19 52 65 76 69 ............Revi
F000:4E90 73 69 6F 6E 20 30 31 00-FF FF FF FF FF FF FF FF sion 01.........
F000:4EA0 FF FF FF FF FF FF 00 19-30 30 30 30 31 32 33 34 ........00001234
F000:4EB0 35 20 20 20 20 20 20 20-00 FF FF FF FF FF FF FF 5 ........
F000:4EC0 FF FF 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
F000:4ED0 00 00 00 00 19 47 61 74-65 77 61 79 20 00 FF FF .....Gateway ...
F000:4EE0 FF FF FF FF FF FF FF FF-FF FF FF FF FF FF FF 00 ................
F000:4EF0 19 47 61 74 65 77 61 79-20 32 30 30 61 72 63 20 .Gateway 200arc
F000:4F00 00 FF FF FF FF FF FF FF-FF FF FF 00 19 52 65 76 .............Rev
F000:4F10 69 73 69 6F 6E 20 30 31-00 FF FF FF FF FF FF FF ision 01........
F000:4F20 FF FF FF FF FF FF FF 00-19 30 30 30 30 31 32 33 .........0000123
F000:4F30 34 35 20 20 20 20 20 20-20 00 FF FF FF FF FF FF 45 .......
F000:4F40 FF FF FF 00 19 47 61 74-65 77 61 79 20 00 FF FF .....Gateway ...

F000:E830 B1 FA E8 14 66 81 4E 18-00 02 CB 00 00 00 00 00 ....f.N.........
F000:E840 47 61 74 65 77 61 79 00-00 00 53 BB 08 00 E8 AB Gateway...S.....
F000:E850 03 5B C3 56 26 80 3D 81-0F 94 C3 75 06 3C 02 75 .[.V&.=....u.<.u

F000:FFA0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
F000:FFB0 FF E7 50 41 54 43 48 32-E8 B8 FE CB 00 00 00 00 ..PATCH2........
F000:FFC0 47 61 74 65 77 61 00 4B-34 32 2E 30 32 2E 30 34 Gatewa.K42.02.04
F000:FFD0 00 32 30 30 41 52 43 20-20 00 34 32 2E 30 32 2E .200ARC .42.02.
F000:FFE0 30 34 00 00 E9 A8 B5 00-00 00 00 00 00 00 00 00 04..............
F000:FFF0 EA 5B E0 00 F0 30 33 2F-30 33 2F 30 34 00 FC FB .[...03/03/04...


System Informantion (Mixed Display)
< Type, Length, Handle = 1, 19h, 1h >
Manufacturer : Gateway
Product Name : Gateway 200arc

Base Board Informantion (Mixed Display)
< Type, Length, Handle = 2, 8h, 2h >
Manufacturer : Gateway
Product : Gateway 200arc

System Enclosure or Chassis (Mixed Display)
< Type, Length, Handle = 3, 11h, 3h >
Manufacturer : Gateway

Edited by xehqter
0

Share this post


Link to post
Share on other sites
@Bezalel

The previous character was CRLF so 0x0D, 0x0A, FSC SERVER, 0x20, 0x20, ....... 0x0D, 0x0A

0x20 being SPACE.. perhaps it was reading all the spaces after the string.. hmm..

I know it isn't case sensitive, Maybe it also treats all whitespace characters as it if were a space. 0x0D is considured whitespace.

@Bezalel: I am asking about the rapidshare folder because you are also missing some common files. At least "Acer Travelmate" notebooks are sold very well and widely spread but your repository misses the files.

I have all non-obsolete filesets in my RapidShare folder. I will upload obsolete files upon request (if nobody downloads them, RapidShare will drop the files).

0

Share this post


Link to post
Share on other sites

OK I finished creating a tool to allow someone to easily scan their system and collect any locations of bios strings. I recommend having this tool placed at the top of this thread so others can easily find it and use it. It will help us gather much needed info so we can better our tools.

GetSystem.exe

Edit: I just made a few changes dealing with spaces as the first or last characters of the string. So if you just downloaded this within the first 30 mins of release please redownload.

Edited by Siginet
0

Share this post


Link to post
Share on other sites

@Sigi

I ran this on my PC at work, which is a MEDIONPC who preactivates correctly with the oembios set we have, allthough i get this message:

Sorry this system is not found in the GetSystem.ini.

It may not be a system capable of pre-activation.

[edit] The updated release works ok

Edited by FreeStyler
0

Share this post


Link to post
Share on other sites

Hmmm... that's odd.

Can you try the version I just released. I fixed a couple small bugs I found after release. Maybe that fixes your issue too. Make sure you delete the GetSystem.ini as well. ;)

It's possible I messed up the code. I don't have many computers to test this on.

It should search for these 2 strings on your computer:

MEDIONPC,MEDIONNB

Thanks

Edit: actually I am pretty positive it was one of the bugs I fixed. Please try the new one. :)

Edit2: Grrr... I made another small bug in the last release as well. :( Sorry... Please download agian. lol. I accidentally made it put too much info in the log file. It gets all the needed info but it also throws a bunch of crap into the log. This version seems to work right. ;)

Edit3: I have also updated my OEMBIOS.EXE v0.3 tool. It is now possible to specify an exact area to search the bios for a string.

Edited by Siginet
0

Share this post


Link to post
Share on other sites
The new version passes WinTrust.

@xehqter

What does this exactly mean?

0

Share this post


Link to post
Share on other sites

The new version passes WinTrust.

@xehqter

What does this exactly mean?

An easier way is to use KeyUpdateTool.EXE from Microsoft. You don't need to change the key, you only need to watch to see that the files don't fail WinTrust.

Current Version

If you simply copy over the OEMBIOS files they will pass WGA Validation but fail WinTrust (ie: SFC /SCANNOW, KeyUpdateTool, etc) because the cat file needs to be imported into a special database. The new version imports the cat file. :)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.