X hits on this document





58 / 174

Microsoft Windows Logo Program System and Device Requirements  —  58

Requirements and clarifications for automatic device configuration, resource allocation, and dynamic disable capabilities for legacy components such as serial and parallel ports, as defined in Legacy Plug and Play Guidelines at http://www.microsoft.com/hwdev/tech/pnp.

Dynamic disable capabilities must be supported for all devices. All devices must be capable of being automatically disabled by the system. Also, disabling the device must result in the freeing of all its resources for use by other devices.

The following are exceptions to the requirements for a unique Plug and Play ID:

Legacy devices attached to the Industry Standard Architecture (ISA) bus on the system board set do not have unique Plug and Play IDs—for example, serial ports, parallel ports, or PS/2-compatible port devices. The method for device identification is defined in Plug and Play ISA Specification, Version 1.0a, and the ACPI specification. Itanium-based systems must comply with ACPI 2.0; x86-based systems must comply with ACPI 1.0b.

Standard system devices. The system can reserve static resources for devices such as programmable interrupt controllers (PICs) 1 and 2, timer (8254-2), keyboard controller (8042), real-time clock, DMA page registers, and DMA controllers 1 and 2. For IA-32 systems, these fixed resources are located at I/O addresses under 100h and can also include a NMI.

Devices that are completely invisible to the operating system, such as out-of-band systems management devices or I2O hidden devices; however, these devices still must properly reserve resources using ACPI methods to avoid potential conflicts.

Some multifunction devices (such as Super I/O) might include devices that do not have unique Plug and Play IDs or unique PCI Subsystem IDs, but that are supported by drivers provided with Windows.

A device such as a multifunction PCI device that supports a number of functions but uses only a single set of relocatable resources does not have to provide separate identifiers for each function included on the device.

Some devices are completely invisible to or are not managed by the operating system, such as out-of-band systems management devices or I2O system and I2O hidden devices. Such devices are exempt from this requirement, but these devices still must properly reserve resources using ACPI methods to avoid potential conflicts.

If an OEM uses a proprietary mechanism to assign asset or serial numbers to hardware, this information must be available to the operating system using Windows hardware instrumentation technology, as defined in the Windows Hardware Instrumentation Implementation Guidelines, Version 1.0 (WHIIG).

See additional notes in specific device-class requirements.

B1.4.2 Software does not replace system components

See A5.1.1

Driver or software installation must not replace any Microsoft-authored operating system components.

Notice that each Windows product has a unique set of files protected under system file protection.

For information about protected operating system files, 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.

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views301
Page views301
Page last viewedTue Oct 25 18:04:11 UTC 2016