Client system - Microsoft Windows Logo Program System and Device Requirements

Client system: Network adapters with PXE support must be available as an option at point of purchase for systems preinstalled with Windows XP Professional. See A1.1.4.
Server system: Server systems must provide PXE-based support if a network adapter with remote new system setup capabilities is provided with the system.
This is not a requirement for CardBus adapters or for Mini-PCI adapters that are not sold as a part of or with a PC system.
B7.1.4.6 HomePNA technology, if implemented, complies with HomePNA 1.0 or later, with NDIS 5.0 miniport driver
If implemented, a network adapter that implements HomePNA technology must comply with the Home Phoneline Networking Alliance Spec, Version 1.0.
B7.1.4.7 Infrared device supports both fast IR and serial IR, and unattended driver installation requirements
All infrared devices must comply with approved IrDA specifications, including support for SIR, FIR, and optional Very Fast IR (VFIR) data devices.
FIR Plug and Play hardware must report a unique Plug and Play ID that matches the combination of the chip set, transceiver, and any other system-specific parameters for the operating system to find and install the correct INF file and the associated driver for the IrDA hardware.
In the best case, the IrDA hardware has only one Plug and Play ID associated INF file and a miniport driver that can autodetect the transceiver type and other system-specific parameters. This combination enables the installation and configuration of the hardware and the driver without user intervention.
In other cases, for example, where the miniport driver cannot autodetect the transceiver type or any other system-specific parameters, a unique Plug and Play ID for each combination of the chip set and the transceiver type must be reported. Also, the vendor must provide for each combination an associated driver and INF file describing the configuration parameters.
B7.1.4.8 Full-duplex adapter automatically detects and switches to full duplex mode
If both the network adapter and switch port in a link pair support full duplex and there exists a standard way for each to detect and negotiate the duplex mode, the network adapter must negotiate full-duplex mode operation by default. Half-duplex mode can be used if that is the only mode supported by one or both link partners, or it can be manually configured if warranted by special conditions. The goal is to configure this setting automatically without end-user intervention.
B7.1.4.9 Plug and Play capabilities support multiple adapters; all resource settings are reported in the UI
For network communications devices, the Plug and Play IDs and resource support must be sufficient to allow the automatic addition of multiple network communications devices to the system.
All resource settings must be viewable in the Device Manager and in the adapter properties dialog boxes. All resource settings that can be changed by the user must be changed using the standard Windows user interface, not through the use of INI files or other setting files.
This requirement implies that all device resources must be set and read through the standard interfaces provided by the bus on which the device resides. For PCI devices, this interface is the PCI configuration space. Also, device parameter settings must be stored in the registry.
B7.1.4.10 Wireless networking requirements B7.1.4.10.1 Wireless network media adapters must meet all requirements for network adapters except where noted. B7.1.4.10.2 IEEE 802.11 wireless networking adapters support 11 Mb/s signaling using Direct Sequence Spread Spectrum. B7.1.4.10.3 Bluetooth Host Controllers (HCI)
Windows uses Bluetooth Wireless technology as a wireless local bus and cable replacement. Therefore, Bluetooth HCI (radios with PC interface) do not need NDIS miniports. Requirements for Bluetooth HCI are listed in B2.3.4.5.
B7.1.4.10.3 Wireless networking media adapters support wireless extensions to NDIS
Wireless extensions to NDIS are documented in “Network-Dependent Wireless Objects” in Network Drivers in the Windows DDK. These extensions are based on the work of the Portable Computer and Communications Association.
B7.1.4.10.4 Wireless network media adapters must meet all requirements for network adapters
IEEE 802.11 devices must support the appropriate OIDs.
IEEE 802.11 devices must be compatible with Wi-Fi
Information on Wi-Fi can be found at http://www.wi-fi.org
Flash based firmware drivers must update without user intervention.
B7.1.3.6 IEEE 802.x network adapter and driver that implement QoS support priority for IEEE 802-style networks.
Windows Quality of Service (QOS) components provide link layer priority information to NDIS 5.0 miniport drivers in each transmitted packet’s NDIS_PER_PACKET_INFO structure.
Priority values are derived by mapping Internet Engineering Task Force (IETF) Integrated Services (IntServ, RFC 1663) service typed to IEEE 802.1p priority values, referred to as the user priority object. Current IETF references include:
-
The Subnet Bandwidth Manager.
-
Framework for integrated services over 802 networks.
-
Mapping integrated services to 802.1p.
The IntServ service type used for the mapping is determined by QOS-aware applications or, on behalf of the application, by QOS-aware operating system components. Driver support for link layer priority information must adhere to IEEE 802.lp priority values.
IEEE 802.1p/q-capable Ethernet drivers must use the priority level indicated in the NDIS_PER_PACKET_INFO structure to generate the corresponding field in the IEEE 802.1p/q MAC headers of transmitted packets. Similarly, these drivers must extract the appropriate information from the MAC headers of received packets and copy the priority to the NDIS_PER_PACKET_INFO structure before indicating the packet to higher protocol layers.
Notice that any link layer driver has the ability to interpret the priority information in the NDIS_PER_PACKET_INFO structure and use it as appropriate for the particular media.
For more information, see the Windows DDK and “QOS: Assigning Priority in IEEE 802-style Networks.”
See also “QoS: Assigning Priority in IEEE 802-style Networks,” available at http://www.microsoft.com/hwdev/tech/network/qos/qos.asp
B7.1.4.11 External networking devices support standard control interfaces as applicable B7.1.4.11.1 All external USB networking devices support USB Communications Class Device 1.1 or higher. B7.1.4.11.2 NDIS 5.0 (WDM layered) miniport driver required for USB-connected network adapters B7.1.4.12 Windows Server 2003, Standard Edition: Additional adapter and driver support B7.1.4.12.1 NDIS 5.0 miniport driver supports high-performance send and receive calls.
NDIS drivers for server-side network adapters must support the higher performance send (NdisSendPackets) and receive (NdisMIndicateReceivePacket) calls as documented in the Windows DDK.
B7.1.4.12.2 - See B7.1.4.2 B7.1.4.12.3 DELETED B7.1.4.12.4 If the network device is for connection-oriented media, it must meet connection-oriented miniport driver and call manager driver requirements.
See the Network Drivers section of the Windows DDK for more information related to this requirement.
|