Unregistering USB device types
-
During development of a USB device, I temporarily used Vendor ID=547 and Device Id=1002, since those were the defaults for the development kit I was using. I have since switched to using properly-registered IDs. Unfortunately, a product I have purchased and would like to use (a chip programmer) uses the same IDs, and any time I plug it in Windows wants to attach my drivers rather than the proper drivers for the device. I can easily enough see what devices are 'installed' and uninstall them, but the next time I plug in the device it installs it with my drivers rather than prompting for the right ones. What must I do to tell windows that 0547/1002 is NOT my device and I would like it to prompt for a .INF file (which could then load the proper drivers)?
-
During development of a USB device, I temporarily used Vendor ID=547 and Device Id=1002, since those were the defaults for the development kit I was using. I have since switched to using properly-registered IDs. Unfortunately, a product I have purchased and would like to use (a chip programmer) uses the same IDs, and any time I plug it in Windows wants to attach my drivers rather than the proper drivers for the device. I can easily enough see what devices are 'installed' and uninstall them, but the next time I plug in the device it installs it with my drivers rather than prompting for the right ones. What must I do to tell windows that 0547/1002 is NOT my device and I would like it to prompt for a .INF file (which could then load the proper drivers)?
I have no clue to where windows caches the setting or files. Have you tried uninstalling your driver, purging the temporary files and removing any .INFs that match your description? Other than that, this is why default IDs are bad.
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
-
I have no clue to where windows caches the setting or files. Have you tried uninstalling your driver, purging the temporary files and removing any .INFs that match your description? Other than that, this is why default IDs are bad.
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
Since having written the earlier message, I've managed to delete the appropriate .INF files and pretty much convinced the system that my device doesn't exist under its old identity. I still can't get the new device to work, though. My guess is that it partially installed something in such a way as to get itself confused. Sometime I'll reinstall the OS on this machine, and when I do I can fix things then. In the mean time, I wonder how I should best contact/pester the device vendor. It seems that its .INF files contain both the default vendor/device id's and some other ones, but the device itself uses the default ones. Grrr....