[FreeStyler]

ZaForD, on Jun 8 2006, 08:35 PM, said:

FreeStyler,
I have both Toshiba and IBM pro filesets dated 2001, if thats any good to you ?

Ah, think i have proper files for those, actually i meant older DELL oembios files only....
it doesn't succesfully activate with newer OEMBIOS files from DELL XP Professional SP2 Media

[Bilou_Gateux]

Bezalel, on Jun 1 2006, 04:04 AM, said:

Although my method is currently working SFC is aware that the files have been changed because oembios.cat was parsed before the files were changed. If the end user ever runs SFC manually they will be prompted for the oembios files that match the origional oembios.ca_ that was left on the CD. My two question now are:

When SFC parses the oembios.cat file where does it store the thumbprints of the remaining oembios files? (I am able to delete the oembios.cat file, it is not protected but SFC still knows that the files aren't origional)

oembios.ca_ replacement may require to rebuild database as described in MS KB822798 Article - Method 3

I haven't checked myself if it would works, which OEMBIOS.* should we use in a MS virtual machine

[jrf2027]

FreeStyler, on Jun 9 2006, 12:52 AM, said:

ZaForD, on Jun 8 2006, 08:35 PM, said:

FreeStyler,
I have both Toshiba and IBM pro filesets dated 2001, if thats any good to you ?

Ah, think i have proper files for those, actually i meant older DELL oembios files only....
it doesn't succesfully activate with newer OEMBIOS files from DELL XP Professional SP2 Media

Let me know if you still need the older Dell OEMBIOS files...I have the following Dell OEM CD's:
XP Pro Gold
XP Home Gold
XP Pro with SP1
XP Home with SP1a

[FreeStyler]

jrf2027, sure i would love to get the "gold" ones
BTW, HOME and PRO oembios.* are suposed to be the same (to be sure, can you do a md5 compare on them?)

If you have access to the computers the XP runs on, can you dump their BIOS/DMI info for me and send me those text files?

Download this tool
http://crystalmark.info/download/download....=CrystalDMI.zip
Unzip & Run it -> Select “All Information” from the dropdown box -> CTRL + C
Then preferably paste (CTRL + P) the copied info into separate txt files.

I am currently working with "BIOS" patched Microsoft Virtual PC's to test as many oembios files as i can, for some strange reason up to now DELL, SONY, SAMSUNG oembios files always fail the SLP

[vpn-user]

FreeStyler, on Jun 11 2006, 09:45 AM, said:

BTW, HOME and PRO oembios.* are suposed to be the same (to be sure, can you do a md5 compare on them?)

I don' t think they are exactly the same. But, in my experience, at least they worked vice-versa.

[tkmadison]

Manufacturer: LENOVO
   Model: 8258J4U
   4C454E4F 564F

[druiddk]

How do I figure out what to rename the OEMBIOS files to?
I have my own sets from HP, IBM, Dell and NEC...

[bober]

don't rename them. the names are the same for all manufacturers. i keep the ones that i have in separate folders:
HPpro folder,HPhome folder,etc.

[Bezalel]

druiddk, on Jun 11 2006, 04:59 PM, said:

How do I figure out what to rename the OEMBIOS files to?
I have my own sets from HP, IBM, Dell and NEC...

The opening post has a script that reports the manufacturer, model, and a hex representation of the manufacturer. The filenames should be the same as the hex representation of the manufacturer but without the spaces.

In the future I plan to create a folder with these names and leave the filenames intact.

[FreeStyler]

@Bezalel

What if a developer string has additional spaces behind the actual manufacturer string?
Lets say I i have a HP box, which is being reported as:

Quote

Manufacturer: Hewlett-Packard
Model: Virtual Machine
4865776C 6574742D 5061636B 61726420 20202020 20202020 20202020 202020

Can your script filter out the additional spaces or can you make/modify your script so it checks if, when no exact match is being found files with a partially the same pattern (4865776C6574742D5061636B617264) are being used?

FreeStyler

This post has been edited by FreeStyler: 12 June 2006 - 01:43 AM

[druiddk]

@Bezalel:

Manufacturer: LENOVO
Model: 8258J4U
4C454E4F 564F

In this example I would rename the OEMBIOS files into 4C454E4F564F.* and then it should work for all computers with manufacturer LENOVO? or would this be specific to the 8258J4U model?

Thank you in advance!

[FreeStyler]

druiddk, on Jun 12 2006, 09:14 AM, said:

@Bezalel:

Manufacturer: LENOVO
Model: 8258J4U
4C454E4F 564F

In this example I would rename the OEMBIOS files into 4C454E4F564F.* and then it should work for all computers with manufacturer LENOVO? or would this be specific to the 8258J4U model?

Thank you in advance!

Yes, 4C454E4F564F.* files are being used for all pc's where Manufacturer is set to: LENOVO
Modelname and type as of yet is not being used in this whole story (might be later)

[druiddk]

Quote

Manufacturer: IBM
Model: 1871F1G
49424D

Btw:

for /F "tokens=1* delims='" %%a in ('smbios2.exe /G ^|findstr "Manufacturer"') do (
cscript CreateBatFile.vbs "%%b"
GOTO ENDFOR
)

Why is the GOTO ENDFOR included? As I see it it should just continue with the next command when the FOR is completed and since the :ENDFOR is right after the FOR command it seems pointless to me?

This post has been edited by druiddk: 12 June 2006 - 06:06 AM

[Djé]

druiddk, on Jun 12 2006, 12:56 PM, said:

Why is the GOTO ENDFOR included? As I see it it should just continue with the next command when the FOR is completed and since the :ENDFOR is right after the FOR command it seems pointless to me?

Because Findstr may find more than one "Manufacturer" line (Bezalel reported so) and you don't want to iterate on all of them but just take the 1st one (which hopefully is the right one). Hence the GOTO once the job is done.

[druiddk]

Ah Djé thank you for clearing that up for me

[Bezalel]

Djé, on Jun 12 2006, 07:40 AM, said:

druiddk, on Jun 12 2006, 12:56 PM, said:

Why is the GOTO ENDFOR included? As I see it it should just continue with the next command when the FOR is completed and since the :ENDFOR is right after the FOR command it seems pointless to me?

Because Findstr may find more than one "Manufacturer" line (Bezalel reported so) and you don't want to iterate on all of them but just take the 1st one (which hopefully is the right one). Hence the GOTO once the job is done.

Since SMBIOS.EXE always reports the structures in numerical order the first manufacturer to be encountered is in the system structure (Structure type 1). according to the SMBIOS spec there must be 1 and only 1 structure of type 1. Structure Type 0 (BIOS) does not contain a manufacturer field.

The Following Structures may also contain a manufacturer:
2 Base Board
3 System Enclosure
4 Processor
22 Portable Battery
30 Out-of-Band Remote Access
39 System Power Supply

[Bezalel]

FreeStyler, on Jun 12 2006, 02:41 AM, said:

Can your script filter out the additional spaces or can you make/modify your script so it checks if, when no exact match is being found files with a partially the same pattern (4865776C6574742D5061636B617264) are being used?

I will trim the string to remove leading and trailing spaces in a future version. Partial matches are hard to code and if I ever implement CRC32 it will be impossable to implement partial matches.

[FreeStyler]

Bezalel, on Jun 12 2006, 06:12 PM, said:

FreeStyler, on Jun 12 2006, 02:41 AM, said:

Can your script filter out the additional spaces or can you make/modify your script so it checks if, when no exact match is being found files with a partially the same pattern (4865776C6574742D5061636B617264) are being used?

I will trim the string to remove leading and trailing spaces in a future version. Partial matches are hard to code and if I ever implement CRC32 it will be impossable to implement partial matches.

That would be cool,

hey maybe eventually you can make a check that searches for Strings like: IBM, ACER, DELL....this way you would save quite some diskspace as you do not need files for every other variation in "System Manufacturer" names.

[Bezalel]

FreeStyler, on Jun 12 2006, 05:18 PM, said:

hey maybe eventually you can make a check that searches for Strings like: IBM, ACER, DELL....this way you would save quite some diskspace as you do not need files for every other variation in "System Manufacturer" names.

I'm not concerned with disk space since identical files are only written once to the CD. Implementing this would require hardcoding the manufacturer names in the script (I don't want to do this) or maintaining a database (too much work for too little benefit).

[FreeStyler]

Bezalel, on Jun 12 2006, 11:52 PM, said:

FreeStyler, on Jun 12 2006, 05:18 PM, said:

hey maybe eventually you can make a check that searches for Strings like: IBM, ACER, DELL....this way you would save quite some diskspace as you do not need files for every other variation in "System Manufacturer" names.

I'm not concerned with disk space since identical files are only written once to the CD. Implementing this would require hardcoding the manufacturer names in the script (I don't want to do this) or maintaining a database (too much work for too little benefit).

no, i believe the opposite is true and the benefit of such method will be greater then its limitations...
I'll try to explain...if you search manufacturer strings for example "Dell" or as hex "44656C6C" you would have a more variable system that should work on various types of Dell Systems.
Dell PC's come with a randomly named '"System Manufacturer" string, one advantage it always starts with "Dell" eg;
Dell Computer Corp.
Dell Computer Corporation
Dell Computer Corporation.
Dell Inc.
And maybe a whole lot more variations... who knows!
Using a technique like this you have a more "reliable" versatile fail safe method that should work on every dell pc

Same counts for Acer, eg:
Acer
Acer, Inc.
AcerSystem

This post has been edited by FreeStyler: 12 June 2006 - 04:41 PM