Non-Plug and Play device/non-Plug and Play driver: no Plug and Play support.
∙
Non-Plug and Play device/Plug and Play driver—possible partial Plug and Play support. A non-Plug and Play device can have partial Plug and Play support. Although it is not possible for the system to automatically and dynamically recognize the hardware and load the appropriate drivers, it is possible to have Plug and Play manage resource allocation, provide an interface for driver interaction with the Plug and Play system, interact with power management, and register device notification events. Also, if a non-Plug and Play device has a Plug and Play driver, the device appears in the Device Manager application, and property pages are available for that device.
∙
As this table indicates, any device that supports Plug and Play should have Plug and Play support in its driver. The following list expands on the possible configurations:
∙ Plug and Play device and driver—full Plug and Play support. To provide the optimal Plug and Play support, the hardware implementation must comply with the OnNow design initiative, including ACPI. Windows 2000 Plug and Play targets ACPI systems only.
∙ Plug and Play device/non-Plug and Play driver—no Plug and Play support. If a driver does not support Plug and Play, its device behaves as a non-Plug and Play device, regardless of support in the hardware. A non-Plug and Play device can constrain the Plug and Play capabilities of the entire system.
Plug and Play device
Non-Plug and Play device
or removal of a device is an example of such a dynamic event, as is the ability to awaken a device or put it to sleep. Plug and Play and power management both use WDM-based functions and have similar methods for responding to dynamic events.
∙Registration for device notification events. Plug and Play enables user- mode code to register for and be notified of certain Plug and Play events. The RegisterDeviceNotification routine allows callers to filter exactly the class or device for which they want to receive notification. This can be specific, such as
a file system handle, or general, such as a class of devices. Legacy 'HYLFHWindowsDQGNT'ULYHUnotification6XSSRUWmethods/HYHOVcontinue to work as before.
The extent to which a device supports Plug and Play depends on the Plug and Play support in both the device hardware and the driver(s) for the device (see Table 1).
Plug and Play driver
Full Plug and Play
Possible partial Plug and Play
Non-Plug and Play driver
No Plug and Play
No Plug and Play
Windows 2000 White Paper | 4 |
