There is a generic Bluetooth driver that ships with Windows, and this driver is only designed to work with the Microsoft Bluetooth Enumerator. One common exception is that many Bluetooth radios share very similar hardware and can therefor use each other’s drivers. It is like randomly making noises to someone that speaks a foreign language: by random chance you could say something, and by even more random chance what you say could be offensive, but most likely you won’t say anything intelligible at all. Loading the wrong driver for a device probably just won’t work, although it could make your computer unstable, and in theory, (but very unlikely in practice,) permanently break the device itself. It will then know what driver to to use for that piece of hardware and load the appropriate driver for it. Windows can look many places, including Windows Update and its collection of inf (setup Information) files. The way that device identify themselves on USB is that companies sign up for a number called a Vendor ID or VID for short, (Vernier’s is 08F7,) and then within that vendor code the company assigns Product IDs or PID for short, (LabPro was our first USB device so it is 0001.) When the device is first connected to the computer, Windows asks the device for the hardware IDs, and then looks for a driver that supports those hardware IDs. If you are not very comfortable with the underpinnings of Windows,it is probably best to get your IT staff involved to resolve this issue. Note:The below instructions are only intended for a power user or IT staff. However, that doesn’t always work, the hardware manufacturer may not have designed their hardware with that in mind. The ideal solution to all Bluetooth problems is to follow the steps to properly uninstall the conflicting enumerator and then let the Microsoft Bluetooth Enumerator take over.īluetooth Help and Troubleshooting Tips related to the Wireless Dynamics Sensor System (WDSS)
0 kommentar(er)
