FindHWIDS v3.2s - The INF Searching, Hardware ID Exporter (Page 2 of 15)

that is the magic of what we do... some of those will get along with each other and some won't

in theory if they are all written correctly and all signed and dont have specific hwids that match ect...
then they will work and can coexist - we dont live in that perfect world...
that is why it is so important people post thier hwids and tell us which driver worked...
it tells us if they are all four gettign along together...
sometimes we have to remove a hwid form a driver to prevent a conflict - this can suck becase it will generally also break its signing. and then it gets passed over for yet another driver in a domino effect ... ;(

so you can see how this is a very important tool for us

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

v1.7 is out... check the first post!

What because of no code no one speaks to me??

Last edited by stamandster (2008-09-05 23:53:23)

Updated to v2.4 - Changed everything this time around; Doesn't scan for a specific HWID and will do multiple HWIDS inline.

Basically instead of scanning for a specific HWID type like PCI\VEN or USBSTOR\ it'll find everything that matches a HWID. For instance HWIDS like NCRC710_SCSI, ACARD___RAID_PROCESSOR__1, CPQFWS2E_SCSI, ACPI\ATK0110, *VIA3058, {4B571702-E6C6-4db1-A2C6-FD1D53A70FC3}\ALICOMPOSITE, PCI\CC_0C0300, *ITE8704, etc.

And it'll find all HWIDS that are inline for instance C:\D\M\P3\S150SX8.inf has a line
%PCI\VEN_105A&DEV_8000.DeviceDesc%=S150sx8PCI,PCI\VEN_105A&DEV_8000,PCI\VEN_105A&DEV_8002,PCI\VEN_105A&DEV_8004,PCI\VEN_105A&DEV_8006
so for PCI\VEN_105A&DEV_8000 it'll add all these
PCI\VEN_105A&DEV_8000
PCI\VEN_105A&DEV_8002
PCI\VEN_105A&DEV_8004
PCI\VEN_105A&DEV_8006

Does anyone know who made the Sav_HWID.exe ??

Last edited by stamandster (2008-09-09 11:29:54)

Oh... I thought someone actually scripted the find functions. I didnt realize it was just devcon.

Did you get to try the latest version??

Thanks Overflow. I just wanted to give you an update on the logic of finding HWIDS.

I'm working on another method besides the two I just did. This one will scan the INF as an INI file.

Each INF has a section called Manufacturer and within manufacturer there are lines such as %Company% = Company or %Company% = Company, NT.5.1, NTIA64, NTAMD64
What is great about this is you can then specify what OS model you want when searching! So not only will my program be able to search for a specific HWID but also a specific OS type.

The %Company% variables end up being sections where the HWIDS go so the above would create 5 sections
[Company]
[Company.NT.5.1]
[Company.NTIA64]
[Company.NTAMD64]

Or this real example
[Manufacturer]
%MFGNAME%=Company, NT.5.1, NTamd64.5.1, NT.6.0, NTamd64.6.0

[Company]
%DEVICEDESCRIPTION% = DriverInstall,ACPI\IFX0101,ACPI\IFX0102,*IFX0101,*IFX0102,IFX0000
[Company.NT.5.1]
%DEVICEDESCRIPTION% = DriverInstall.NT.5.1,ACPI\IFX0101,ACPI\IFX0102,*IFX0101,*IFX0102,IFX0000
[Company.NTamd64.5.1]
%DEVICEDESCRIPTION% = DriverInstall.NTamd64.5.1,ACPI\IFX0101,ACPI\IFX0102,*IFX0101,*IFX0102,IFX0000
[Company.NT.6.0]
%DEVICEDESCRIPTION% = DriverInstall.NT.6.0,ACPI\IFX0101,ACPI\IFX0102,*IFX0101,*IFX0102,IFX0000
[Company.NTamd64.6.0]
%DEVICEDESCRIPTION% = DriverInstall.NTamd64.6.0,ACPI\IFX0101,ACPI\IFX0102,*IFX0101,*IFX0102,IFX0000

Then each HWID is prefaced with it's installer which has it's own sections. That sorta follows a rhyme or reason. But not as well as the Manufacturer link to section names.

So this will provide a greater granularity when doing scans.

I could possibly that with _ArrayElements which gives the unique elements of an array. However, it's not handling 2d arrays well. Plus I'm having an issue with creating 2d/multidimensional arrays. Just not getting it.

It also seems to me that if any line in the Manufacturer section is commented out then that set of HWIDS wouldn't be used. Am I correct in assuming that?

The latest version is out! I also fixed a couple issues that cropped up with testing. So it should be good for release.

What's great about this is we don't _need_ to know any of the HWID types. But in the future I could write it to only parse certain types. That and the option to scan for certain OS types/versions too!

I just noticed I had three posts in a row... I'm talking to myself aren't I?

Last edited by stamandster (2008-09-12 01:28:43)

v2.7 is out which fixes issues with perens in the manufacturer values