Design Guideline References:
PC 2001 System Design Guide - Chapter 3, “PC System” -
Hardware Design Guide 3.0 for Windows 2000 Server, Chapter 2 -
[SYS-0027, SYS-0029.3; SDG3:17]
Device ID is present, device is properly enumerated, and correct driver is found; device can be disabled automatically by Windows.
(see additional notes in specific device-class requirements).
[SYS-0025; SDG3:68]
Driver or software installation must not replace any Microsoft-authored operating system components, and the driver must not bypass any operating system components.
Windows XP: Notice that each Windows XP/Windows Whistler Server product has a unique set of files protected under system file protection; for information about operating system files protected in Windows XP, see SfcGetNextProtectedFile and SfcIsFileProtected APIs in the Microsoft Platform SDK.
If the manufacturer’s INF copies any files supplied by the operating system, those files must be copied from the Windows product disk (or preinstalled source files), unless the component is a licensed, redistributable component.
Driver must not use initialization files (INI) for configuration settings.
B1.4.3 Installing and loading the driver does not reduce or eliminate functionality of other devices installed on the system
[SYS-0025.1; SDG3:68]
B1.4.4 Device is functional without restarting the system
[SYS-0029.1]
Device installation does not cause the system to stop running or reboot (unless reboot is required by the operating system) without user interaction.
B1.4.5 Device and driver comply with ACPI and power management specifications
[SYS-0002; SDG3:10]
Device and driver comply with ACPI specification, Default Device Class Power Management Reference Specification, and other relevant device class power management specification
(see additional notes in specific device-class requirements).
|
