by Dean Roddey » Wed Nov 17, 2004 4:26 am
Actually, it may turn out to be a moot point, because there appears to be absolutely no way to interate devices and find a non-HID device by way of its vendor/product id, because there is no generic way under Windows to query those ids except for HID devices (maybe there is at the driver level but not at the application level.)
But this is really problematic since it's just not going to be possible to generically look for a device, since there's no practical way to indicate in some data file that you have to load DLL X and call function Y with this and that data, since that data could be anything and I couldn't create it on the fly without knowing it's form it ahead of time.
So for systems like mine, that means really that no auto-sensing can be done in any practical way that isn't hard coded for every USB device. That's pretty sad. USB is supposed to be so auto-magical, but this limitation means I can really do better with serial and ethernet devices, in terms of auto-sensing them generically.