I wonder about making the excell worksheet links available here.
The worksheets are on FTP, and those with access to tester forum should have found those.
I am not a data mining expert.
(hehe, I am not an expert in anything..)
The raw output from the tool has to be looked at with argus eyes, because there are drivers what have 'dupes' in the inf. The tool is not ALWAYS able to gather Operating System info from the Inf, so I had to look at content to see why dupes was there.
That was like work.
I've seen a driver that had "suspicious" lines in it, and sure enough, the next update fixed it.
It also added wdm copies of the INF files that had not existed before..
I've seen drivers that had dupes in it that were real errors by the OEM.
(like in, they added their HWID, and it already existed. It did not call different settings/registry sections.)
It was NOT for some particular dual card. The excell shows wher I found one of those.. I marked it "B" so it would no longer hilite.. The tool's raw output does show duplicate lines caused by sections which are duplicated across drivers for registry entries. They are not HWID dupes.)
The worst are those that let generic HWIDs exist, where the only thing they really had to have is their specific ones because they have changed SYS files.
The generics fight a battle.
Windows can get information from an INF what can claim that a driver is newer, where the systemfile is actually older or same, or not suitable.
Nobody said it was easy. You guys at least try to help.
Last edited by Jaak (2007-11-17 11:08:04)
The answer was 42?
Kind regards, Jaak.