usbcfg.exe can't display driver information since v 10.192

[oara27]

Peter Brown's USBCFG app no longer displays the USB driver version info since 10.192. The problrm persists with 10.193

[David Azarewicz]

It works for me. I'll have to assume that you have a version or configuration problem. If you expect any help you need to provide a lot more information. Please see ​http://svn.netlabs.org/usb/wiki/Troubleshooting

[Lars Erdmann]

I assume that you run an outdated version of USBCFG. Make sure you use the latest version. That version should contain a DLL named GETDESC.DLL. I had provided Peter with this DLL so that the description string will display properly.

[David Azarewicz]

Regardless, that just proves that the problem is in the application. Since one version works and the next one doesn't, that proves that something is broken in the new version. I assume that the "driver version" is obtained by reading the build level string from the file. There is nothing wrong with the drivers. The bldlevel command has no problem finding and displaying the build level information. This means that the problem is in the application (which includes any DLLs the application might use).

[losepete]

The poster, oara27, is correct: the current build of USBcfg.exe cannot retrieve the Vendor and Version information from the 10.193 drivers - I don't know about 10.192 as those drivers did not work well enough here to keep installed.

If the poster is using the latest public build from hobbes they will see this message 4 times - once for each of the USB?HCI.SYS drivers and once for USBD.SYS on starting USBcfg.exe:-

Error

GETDESC.DLL GetDescription?? call failed

So, David must be using an older build of USBcfg.exe and if he installs the latest build from hobbes he will see the problem.

I do mention this problem myself in ticket #62 when reporting that retesting the 10.193 drivers all seem to work fine so you can close #62.

Interestingly if I backlevel the USBcfg source to use the code in place prior to using GETDESC.DLL all works correctly...

It was only fairly recent USB builds (10.18?) from Lars that needed the GETDESC.DLL file - no problem extracting the Vendor and Revision data from all other USB drivers before the switch to using GETDESC.DLL.

I must admit that I know nothing about including build level information in driver files but someone must be getting something wrong somewhere - or, at least, not quite right :-)

Regards

Peter Brown (USBcfg.exe author)

[Lars Erdmann]

If I ever find the time, I can get the 10.193 drivers and see why scanning for the description string fails with the 10.192 and 10.193 drivers. Technically, the GETDESC.DLL is querying the "resident names" table (or was it the "non-resident names" table ? I'll need to check my own code ...) and expects to find the description string as the first entry. I will need to check if, due to the build process that David chooses, this will not work anymore.

[Lars Erdmann]

Updated GETDESC.DLL and sent to Peter. The new GETDESC.DLL should work with any driver version.

[losepete]

Hi Lars

I'm sorry to report that no updated GETDESC.DLL has reached my email address as of Monday 2nd September.

Please try resending.

Thanks

Pete

[Lars Erdmann]

Updated GETDESC.DLL to scan the module info string by using bldlevel.exe

[Lars Erdmann]

I know attached an updated getdesc.dll for usbcfg.exe. That should work in all cases.

[losepete]

Hi Lars

No idea why your emails have not arrived here.

I will release an updated USBcfg with this dll file in the near future.

Thanks

Pete

[David Azarewicz]

This is an application issue. It has noting at all to do with the drivers and should not be the basedrv component.

[David Azarewicz]

This has nothing to do with the USB drivers. Can this be closed?