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

This is my own opinion.  I was thinking that instead of having two input boxes popping up one right after the other, you could have just one window with two input boxes.  I think this would make your application look better appearance-wise.

Radio buttons will work out well for choosing what type of output to use.

I like the way the new GUI looks.

Geez, at this rate you'll be at v15.9.9 by the end of the year!
You're on FIRE dude!

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

welcome to my world...    thank goodness for bigbrit...

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

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

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

Oh, do you think that this should be stickied?? Since its THAT good

Sweet! You rock Helmi, well the whole team rocks

I just told some team members that people like echoplatoon and kickarse will make a difference in how we we use scan-tools.

Getting to understand there was more than PCI\HWID was a tiny step with huge consequences.
Understanding the difference in sysprep and disc based install will help, and I think the next step will make you see that we (you)revolutionised or had us un-invent some old approaches.

I have little doubt that this is going to be useful for SAD and SAD-Plus.
(SAD; basic driver stand alone, working with dpinst. SAD-plus is a streamed disc which has exceptions for SAD.)

I have this gutfeeling that SYSprep people finally saw that there were differences in the requirements for disc-based install and PE too.
(The total automated elimination of dupes was often no good for disc based install because it had little or no smart discrimination.)

I am no expert on PE.
Some of you sysprep guru are.
However, to do this scanning, and then automatically write exceptions so that naming conflicts go away is probably something one of YOU already thought about.

I can but warn that this would not be easy.
(some workarounds we did for disc based install took us many hours of work, or many moons of tuning and pruning.)

Kickarse, thank you for keeping yourself interested.
Echoplatoon, thank you for the guidance here.
(EchoPlatoon was one of the first whom helped us make excell sheets what helped us tremendously.)

and OverFlow.
he has a bucketful of ideas.
you guys seem to have been able to tap them.

Jaak, thanks for the compliments! I've gained so much help and insight from using Driverpacks that I feel it's my duty and privilege to give back to the community and team. I really do hope this tool can help you guys with tracking down HWIDS and keeping drivers from blowing things up.

I think I might add the ability to export to txtsetup.sif (gathering information from the txtsetup.oem). But I'll have to find out how to do that first. Shouldn't be too hard though, right?

ed. this may help http://support.microsoft.com/?kbid=288344 and this http://www.osronline.com/ddkx/install/txtsetup_1wmq.htm

The next additions should be adding filters for OS types and Architecture types. Then I'll be adding an INI file for settings, for stuff like auto running, etc.

Last edited by stamandster (2008-09-19 13:05:59)