 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The Device Manager is loaded by the kernel, it runs continuously, and it manages loaded device drivers and their interfaces. When the Device Manager loads, it also loads the I/O Resource Manager to read a list of available resources from the registry.
The Device Manager tracks interfaces advertised by drivers and supports searches for drivers based on a globally unique identifier (GUID). The IClass interface can associate an interface GUID with the driver's legacy name, its $device name, or its $bus name. For example, COM1:, $device\com1, or $bus\pci_0_3_0.
In This Section
- Device Manager Architecture
-
Provides information about how the Device Manager manages devices.
- Device Manager Registry Keys
-
Describes the registry keys used by the Device Manager.
- Device Manager Security
-
Describes how the Device Manager validates input/output (I/O) buffers and how it enforces trusted-caller-only access to certain devices.
- Device File Names
-
Describes the file names used by devices and how to access devices with the CreateFilefunction.
- I/O Resource Manager
-
Describes how the I/O Resource Manager manages interrupt requests (IRQs) and I/O address spaces and describes how to configure IRQs and I/O address space resources yourself.
- Device Manager Reference
-
Provides information on the Device Manager programming elements.