The device is detected by the USB hub driver. It finds a matching driver package for the device by comparing the device's hardware IDs and compatible IDs against those IDs that are specified within the package's INF file.įor example, when a user plugs a wireless local area network (WLAN) adapter into the port of a USB hub that is attached to the computer, the following steps occur: Windows uses hardware IDs and compatible IDs to search for a driver package for the device. The format of these identifiers within the ID is also specific to the bus driver.Ĭompatible IDs are typically more generic than hardware IDs and may not include specific manufacturer or model information and may just represent the kind of device this hardware is. Vendor-specific identifiers for the device, such as a vendor, model, and revision identifier.A bus-specific prefix, such as PCI\ or USB\.The format of a hardware ID or compatible ID typically consists of the following: For more information about hardware IDs and compatible IDs, see Device Identification Strings. Windows uses these IDs to find the closest match between a device and a driver package in order to choose a driver package to install on the device.
The primary information needed from the bus driver in order to choose a driver package to install on the device are the device's hardware identifiers (IDs) and compatible IDs. This information is needed for, among other reasons, to identify the driver package(s) that may apply to this device. When a bus driver reports a new device to the Windows operating system, Windows needs to query information about this device from the bus driver to identify the device.
0 kommentar(er)
