X hits on this document





125 / 174

Microsoft Windows Logo Program System and Device Requirements  —  125

Remote boot support is defined in the Preboot Execution Environment (PXE) Specification, Version 2.1. This support may either be included on the adapter, in the system BIOS, or the support may be split between the adapter and the BIOS.

On server systems that support remote new system setup, network connections used for remote boot must comply with remote new system setup capabilities as described in PXE 2.1 or later (for IA-32 systems), or EFI 1.0 (for Itanium-based systems). It must be possible to enable and disable the remote boot (remote new system setup) capabilities through administrative control in order to maintain server security.

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.

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views296
Page views296
Page last viewedTue Oct 25 13:49:34 UTC 2016