v3.0.3 is out! Check it out driver brethren.

Yeah it is. I'm using it now to filter for exporting to Sysprep for class types SCSIAdapter, HDC and System.

I just tested that and it works! I'll add that too. I'm also working on a way to filter the Class type.

I just wish I had some feedback on how it's working for everyone.

Thanks for the compliments! big_smile

Glad you like it Echo. I'm still working on extra functionality.

v3.0.1 is out! Check first post for an update.

I thought this might be a good read and might help us out with figuring out how to edit these drivers better or more efficiently. Do you guys already know about this?

http://www.ndis.com/papers/ndisinstall/ … igncat.htm
http://www.microsoft.com/whdc/Devtools/wdk/default.mspx

You are absolutely right! I was just doing this temporarily to get all the kinks out first. I was actually going to do radio boxes instead.

v2.9 is out!

... and chew bubble gum!

v2.8 is out... see first post on changes. I'll be adding the same functionality as the spotlight tool in what it will parse out.

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

v2.6 is out which fixes an issue with any blank hwids.

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? wink

I'll be uploading v2.5 in the morning. It's a heck of a lot faster than any versions I've done before and it's as accurate as I think it could ever get. Completely rewrote the function and logic.

115 seconds to scan all DriverPacks, including the 3rd party ones. 43,141 HWIDS scanned! That was on a Core 2 Duo 2.0ghz with 2gb of ram though.

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?

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.

Did you get to try the latest version??

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

295

(2 replies, posted in DriverPack Mass Storage)

If you don't have access to the computer, ask the user to use the Sav_HWID.exe program found here http://driverpacks.mirror.thesneaky.com … _hwids.exe and paste the results in this thread. Also the XP service pack version.

What version of DP MassStorage drivers were you using?

I'm just curious on why this is the case. For me I have to scan both C:\D\C\I for *ide.inf and add those HWIDS, and then C:\D\M...

Also, is it possible to change the inf's that are specific to a certain OS to have something like infname_xp.inf? That way when searching for HWIDS we don't accidentally add 2000 only inf?

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 ??

v2.4 of FindHWIDS is out. It get's rid of a couple false HWIDS that popped up. You should get clean HWIDS now.

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

Try the latest tool... It has a little better error checking. If you need that code let me know.