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

76, updated.

hehe.
don't give up thinking about differences to disc and sysprep, and do not forget the reason why we filter dupes in the INI

for instructions on mass storage, Bâshrat the Sneaky and Jeff (and ruudboek) are THE guru.
For PE and UBCD4win, Jeff and Cdob are devs, and JakeLD is a sysprep/PE user/team member.

I am, compared to them and most of you, almost a  home user (I am a mecano with 17 years of PC repair experience.)

Last edited by Jaak (2008-09-19 14:04:01)

a link to information on mass storage.
it has a long txt. This was a collaboration.

after ruud posted essentials, I wanted to understand this better so I wrote up stories about learning pains and made a summary of txts I collected..
Jeff posted the essentals in a FAQ.

Kickarse, you have, I think unwittingly, been a great help to better understanding of how subtleties make a HUGE difference, and I think some of these conversations here will get pasted into this motherlode.
http://forum.driverpacks.net/viewtopic.php?id=2461

now, I want yuor insights on this too, because I (we) cannot know what was clear/diffuse/totally not understood.

you see, we still have no academy, and you are  (believe it or not) a teacher without tenure.
---
Goal, a complete scanner

1; we need full scanner, nothing missing, better than util5.
2; standard, WHICH? Sort depends on CSV rows, and util5 is a fine example of a standard.
3; in the past, skipped info we needed in reads were added manually, manually pasted in the correct row. (extra hours)

a full scan is useful for:
sysprep
PE
disc
conflict tuning by expert team (where automation will go awry, the human brain takes decisions)

a half baked scan (no full automatic filtering on at least six rows, location/version/date/OS/hardid/guiclass) is no good for any automated filter.

For what I am certain about is that my program parses every HWID that's available in all INFs that are usable by windows. I'm fairly positive it doesn't miss a single one (although I was wrong before about that).

The exports via excel and csv will show every HWID and accompanying information (which I could expand upon if you want the ClassGUID or split the version and date, etc) even duplicates that occur from different INF files with the same HWID in them. I see what you mean though. It'd be nice if the program could tell you if the duplicate HWIDs are newer than the ones you imported earlier in the scan. And you could "zoom" in to see what other HWIDs are in the same file and compare the HWID that exist in the files that duplicate. It might trim the packs down a bit.

The sysprep export is fool proof because it'll only update the HWID from the last scanned INF, meaning no duplicates. It has to be that way in order to not screw up the sysprep processes (which I found out the hard way with the first versions of FindHWIDS).

I can add those extra filters in too, if need be. That way you can hone in on any specific driver. I forgot to mention in the new version not only can you input a PNP ID type but you can type a whole or partial PNP ID (HWID) string and it will try and find that PNP ID string, starting from left to right.

<--- lol, I turned into a Driverpacks Wizard!

The INF files will only show three types of "OS" which in my code is setup as shown below.

Select
Case $aINFRead_Signature = "$Windows NT$"
	$aINFRead_Signature = "NT Based OS"
											
Case $aINFRead_Signature = "$Windows 95$"
	$aINFRead_Signature = "Windows 9x/ME"
											
Case $aINFRead_Signature = "$Chicago$"
	$aINFRead_Signature = "All Windows OS"

EndSelect

Last edited by stamandster (2008-09-19 15:23:25)

@ tingmorris.
welcome to DriverPacks

you said vbs? VBS?
did you know how often I asked for a guy to look the infinforead tool in utilityspotlight05.exe?

OK, the prize is XP or vista of choice, but I did promise that a guy whom would correct the blind spot in that scanner gets sent a retail box.
((that was almost a year ago? That challenge and the offer still has me honour bound.))

----
edit
I believe the offending skippers are no longer in the pack

There were ten drivers, and only one of them was not completely duped, and that one had one HWID.
the challenge is, find the originals at broadcom, scan and get output.

this bugged me so much I made a human decision. I bet it is not in a release now.

Last edited by Jaak (2008-09-19 16:35:28)

You will generally see the same HWID in one INF if there's different architecture the driver supports. You can get an idea of this here http://msdn.microsoft.com/en-us/library/ms790212.aspx

And as was pointed out to me earlier, I guess if an INF is EXACTLY the same as another it generally doesn't screw stuff up. But that's, I guess, where driver version and date comes in.

Perhaps the blind spot that was in the Spotlight Utility is completely gone by creating a purpose built tool? Well at least I would love to hope so.

I'd be happy to show you Tim! Just PM me your email address.

Btw, what time zone is the board on?

Last edited by stamandster (2008-09-20 02:01:43)

Well i can't send money... so how does an upgrade to your membership sound...

Nice Job. Giving back to the community is an awesome thing to do and a rare and honorable quality.
Your efforts have been recognized by the team and myself.

Welcome to the testing team Kickarse!

Thank you for that VooDoo that you do!

jeff

PS you will find that the testing team forum is now visible to you...

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!.

Awesome! Thanks guys!

Where in the program did it crash for you smartepants??

Ahh I'll have to figure out a way to make it so that doesn't happen... thanks for testing!

Which is exactly why I chose to "pinch" this data for use with OfflineSysPrep, i.e. build a database from an outputted BartPE plugin for injection into an offline system.

Regards,
Galapo.

What do you mean by root folder tally?

DriverPack Graphics A\A1 is a nightmare for pathlengths since the %SourceDisksNames% calls for a specific folder name.  The folder structure is kept to a minimum but can be hacked smaller.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!