Mobile PC Note: See A3.4.2 for mobile BIOS PXE requirement.
FAQ date: March 19, 1999, revised January 15, 2001
A1.5.8 AGP and requirement for expansion slots to be accessible to end users [Clarification]
For designs implementing the Accelerated Graphics Port (AGP) Pro specification, the two PCI slots adjacent to the component side of the AGP Pro slot may be blocked and used by an AGP Pro Adapter. When the AGP Pro connector is used by a "standard" AGP board, the PCI connectors must be accessible and available for use with PCI cards.
FAQ date: December 7, 1998
A1.5.9 Color coding [Clarification]
Color-coding is only recommended, not required, for both systems and retail peripherals. Recommended color codes are listed at http://www.pcdesguide.org/documents/pc99icons.htm.
A1.5.10 Floppy disk support [Clarification]
The use of a legacy floppy drive is discouraged, but not disallowed; system designers are encouraged to seek other alternatives for both the installation boot drive and casual storage.
FAQ date: March 19, 1999
A1.5.11 DELETED A1.5.12 USB mass storage [Logo program clarification]
USB-based mass storage devices cannot be the primary method of normal system booting. They are expected to be a replacement for booting to load an operating system on the primary boot drive, or as a replacement for legacy floppy drives.
FAQ date: August 26, 1999
A1.5.13 PCI SVID/SID for PCI functions on system boards [Clarification]
See "Specification for Use of PCI IDs with Windows Operating Systems" at http://www.microsoft.com/hwdev/pci/pciidspec.htm.
Note: For Windows XP, SIDs and SVIDs are not required for PCI-PCI bridges and some other core chipset classes. For the specific list of exceptions, see Appendix D of PCI 2.2.
A1.5.14 Resume from Sleep State Requirements [Logo Program Change]
Resume from sleep state (S1-S3) to operating system handoff occurs within 1 second (PC99a:3.4.2 previously stated S1-S4).
This requirement does not apply to servers.
For sleep states S1, S2, and S3, the time to operating system handoff is measured from when the processor starts running (first instruction) to the time that the BIOS jumps to the Waking Vector in the Firmware ACPI Control Structure table, as described in Section 5.2.6 in the ACPI 1.0b specification.
A1.5.15 Windows logo testing for S3 system state under Windows XP [Clarification]
[SYS-0002; SDG3:9]
For Windows XP, the Windows Logo Program for hardware includes the following requirements:
-
System ensures optimal user experience for suspend and hibernate, including correct BIOS support for the supported sleep states.
-
A uniprocessor desktop must support S1, S3, S4, and S5, and support wake from all supported sleep states, except from S4 and S5. [see A1.4.2]
Devices must correctly implement the D3 state such that the operating system can enter into and resume from all sleep states supported on the system, including S3. Devices must be fully functional upon resume from the S3 state. Any PCI devices that support wakeup capabilities must correctly support wake from D3cold.
To ensure that a device meets these requirements, it must be tested in an S3-capable system. This is a requirement for the Windows Logo Program with the release of Windows XP. Note that this is not a new requirement; earlier versions of HCTs didn't enforce this area of testing.
The device categories that will be affected by this requirement are: Audio, Modem, Network, Storage, USB/IEEE 1394, Video.
References:
S3 sleep state is defined in the ACPI specification:
http://www.teleport.com/~acpi/
Related design guidelines are defined in PC 2001 System Design Guide.
Device Class Power Management Reference Specifications
http://www.microsoft.com/hwdev/specs/Pmref/
Windows implementation guidelines, specifications, and white papers for power management
http://www.microsoft.com/hwdev/onnow/
Driver support for power management: see A1.1.2.
See also "Display Adapter Drivers and Windows Millennium Hibernation" at http://www.microsoft.com/hwdev/video/Mill_D3display.htm.
FAQ date: June 30, 2000
A1.5.16 Debug Solutions for Legacy-Free PCs [Clarification]
Microsoft has defined possible debug solutions for Windows-based PCs in the Debug Port Specification at http://www.microsoft.com/hwdev/NewPC/debugspec.htm.
Windows Me and Windows XP support IEEE 1394-based debug solutions, as described at http://www.microsoft.com/hwdev/1394/.
|
