WL-6. System and components support operating system configuration and control of devices
The goal for this requirement is correct support for complete operating system management of system configuration and behavior. This requirement applies for all BIOS, bus, and device components in a system. In particular, this includes:
Windows-ready, ACPI-compliant BIOS.
Correct implementation of Plug and Play and power management.
This requirement is based on fundamental operating system requirements, industry specifications, and Windows DDK implementation guidelines for Plug and Play and other functional capabilities of the operating system.
For details about operating system compatibility and design guidelines, see Appendix A, "System Requirements Checklist."
The following basic ease-of-use guidelines are cited for the Windows Logo:
Driver and utility installation do not require a system reboot, unless required by the operating system.
Installation of a component should not require a reboot when installed on a system where no applications are running.
Chapter 3 - Recommendations and Future Requirements
This chapter describes the processes that Microsoft follows for adding new requirements to the Windows Logo Program for hardware. This chapter also presents specific design practices that Microsoft encourages to provide an optimal end-user experience when running Microsoft Windows operating systems.
Note: Future requirements currently proposed for systems and devices based on industry specification advances and new capabilities planned for future Windows operating systems are defined in the “Future Requirements” sections in Appendixes A and B of this document.
Microsoft presents preview information about new operating system capabilities related to the hardware platform in Design Previews. System and device manufacturers are invited to attend these private sessions, based on the degree of market involvement particular manufacturers have for the specific technologies. Presentations at Design Previews include sufficient detail for manufacturers to understand the technical requirements for implementing new support in hardware and firmware. Microsoft actively solicits manufacturers’ feedback at Design Previews, and Microsoft also provides information about Logo Program requirements proposed in relation to the new system capabilities.
Advances in Industry Specifications vs. Logo Program
Microsoft works with most standards bodies for PC and server technologies, and makes plans to advance operating system support based on the current industry specifications for these technologies.
When proposing new Logo Program requirements related to advances in existing specifications, Microsoft will survey Logo Program participants to determine when most manufacturers are intending to implement the advances.
New Industry Specifications vs. Logo Program
When new technologies are being defined and proposed for general industry adoption, Microsoft typically works with the industry consortium that is defining the hardware and firmware implementation. For example, new technologies such as ACPI and Bluetooth wireless technology are defined in industry consortia. Microsoft develops the related operating system capabilities in conjunction with development of the new specification.
Adoption of such technologies as Logo Program requirements is usually defined in terms such as:
If you implement Bluetooth wireless technology, comply with the industry specification and implement driver support as defined in the Windows DDKs.
The availability of Hardware Compatibility Tests (HCTs) to validate new technologies for the Logo Program typically require good availability of new hardware at Microsoft. The Microsoft development teams require a foundation of hardware implementations in order to create and validate compatibility tests.
Note also that it is rare for the Logo Program to define requirements such as ACPI, where the entire industry was required to change hardware/firmware support to advance PC platform capabilities. In cases where such universal changes are required, Microsoft will work within an industry consortium to define the technical standards and establish appropriate phases for implementing the new requirements in the Logo Program.
Proposals for new requirements are published in the Windows Logo Program newsletter, which is distributed by e-mail.
To receive weekly notification of any Logo Program proposals, subscribe to the mail list as described at http://www.microsoft.com/winlogo/hardware/.
Dates for New Requirements
As a rule, future requirements related to operating system features go into effect when the related operating system is available and the OEM begins shipping systems that contain features supported under the new operating system. See "Windows Logo Program Dates" in Chapter 1.
In general, Microsoft attempts to meet the following general guidelines for proposing new Logo Program requirements.