[Tool] ListHWID.vbs v1.2.0 (Page 2 of 2)

Just added a seperate script for collecting monitor HWIDs.  Also it appears as though monitor hwids are just like some other very short hwids.  It isn't optimal but this may wind up being a solution for now.  Or I may just have to perform two regex operations for everything in one script.

The more that I am getting into this the more I am beginning to think that I may need to port the code over to another environment.  VBscript offers good but not great support for regex.  There seem to be some missing functionality in the area of conditional processing and negative lookaround.

It's funny I was just looking through the AutoIt help file to look at the regex support it offers.  And it doesn't seem to offer even as much as VBscript.  I've been wanting to take up Perl for quite some time now and that seems to be the gold standard for regex.  I'm probably going to take a look at that route.

I use MRTG which is Perl based and it's incredible.  Plus I like that Perl is cross platform.

Unfortunately for me I will be supporting Windows until I retire.  And it will be XP for the next six years if I have anything to say about it.

Already there

I've been using Kubuntu as my primary OS on my desktop (still XP on my laptop) for over a year now.  I dare anybody to do that and still contend that Windows is anything but a piece of crap.

I forgot... thanks for the new tool.

Whatever can be standardised for the better use at DriverPacks, will have a huge impact in our futer.

A prepper (or a hardware wilderness in single-image wishful-thinking-head)  looking for speed gain by automated un-duping of ORIGINAL drivers needs a tool.

And you guys are developing it.

There are still enough people using XP roll-outs for us to have that effort work for DriverPacks as is now, and I already hear clamor for filtered vista and 2008. (what the heck.. One of the guys at the MsViP meet was pleased when he heard about DPinst and the possibility it worked on 98pack.. w/i, faik, still available on Third Party DriverPacks.)

Standardised (INF=> CSV) scanner (s) are our future.
How they work out the OS and version is important. VERY much so.
OS caused dupes help us write the INI.
QUITE a few scanners cannot, because the INF does not have the OS info properly SCANNABLE, output PROPER (true) dupefiltered output.

the spotlight did not attempt to remove dupes.

edit for RogueSpear. (and wsnow)
edited above (why real OS aware dupe eliminatition is a kettle of worms.) for warmsnow and roguespear.

The problem are the writers.
DriverPacks, so far, can reduce hands on work by a huge factor, and I think that was done by the fine people at DriverPacks.
Most of it was eyeballing outputs. (sometimes comparing output from one scanner against another output.. Or the TXT of the INF.. when you scan a file and have zero HWID output and you look at the INF and it had a gumption of unquantifiables?.)

I will ask the entire DriverPacks community to help us document known WHQL conflicts in same class drivers, and ask that they pay attention to /Hwid and 'GUI class' / conflicts.

not just pci/hwid.

you look at the INF and it had a gumption of unquantifiables?.

Last edited by Jaak (2008-10-24 05:05:33)