When I recently scanned some additions for WLAN I discovered utilityspotlight05 is not perfect, because it could not collect the HWIDs from some drivers.
So... Today I looked for folders it had skipped, and found ten of those.
EDIT
Well, from over 270... not bad.

The good part of this excercise was that I spotted a few things I did wrong.
(like an empty folder here and there, caused while renaming the folders to shorten path.. or a folder that should have been deleted but wasn't.)

grrr.. ten drivers to manually get the hardware info from, to put in a worksheet.
I will try to contact the writer of this great tool, and hope he can fix the problem.

Anybody here good in Visual basic?
we may need a variant vbs for getting the info out of these few INF files.

Thanks for the quick response.

NEW W5X\ atheros 01/20/2005,2.2.5.1
NEW WBr7\ Broadcom 12/11/2007,4.0.7.0
NEW WBR8\ Broadcom 02/11/2005, 3.100.64.0
NEW WC3\ 10/12/2006, 4.100.15.5 (for compaQ C700)
NEW WR4\ Realtek (Dlink) 03/12/2005, 2.00.01.0000
NEW WS7\ Sagem 10/28/2005,6.3.0.0

WRE4\ added a Fix for toshiba notebook

updated
WAtT\ Atheros from 04/05/2007,5.3.0.35 to 07/26/2007,5.3.0.67(atheros for Toshiba notebooks)
WU6\ US robotics from 08/11/2004, 3.0.19.1 to 11/16/2005, 3.3.36.0

Nice details and info. Always a pleasure to to see a first post done so well!

After a quick research (german) i found that there had to be added an additional line to the inf file.

Adding this line:

%RTL8187B.DeviceDesc% = RTL8187B.ndi, USB\VID_0BDA&PID_8197&REV_0200

to section:

;; IDs for 98SE/ME/2K/XP

In DPW802/D/WRE4/net8187b.inf seems to solve this problem.

//Edit: corrected: i meant DPBase 8.01 RC2, sorry for that.