Important: For any system design that does not include a built-in serial port, the debug solution must be shipped with the system. This is a requirement for the "Designed for Windows" logo for legacy-free and legacy-reduced systems. The solution must consist of one of the following:
-
For serial ports with non-legacy addresses, the internal header must be exposed in such a way as to be available, but not obvious.
-
For LPC solutions, the header for the dongle connection must be exposed.
-
IEEE 1394 debug.
Systems equipped with one or more standard OHCI-compliant, Windows Logo'd IEEE 1394 controllers can utilize a standard IEEE 1394 port for connecting a host machine with one or more targets (up to 62 on a single bus). The host controller can be on the motherboard or attached via PCI, Mini-PCI, or CardBus.
If the IEEE 1394 controller is not on the motherboard, the system does not have to ship with the IEEE 1394 solution included. Rather, it must contain at least two slots for the addition of an IEEE 1394 card by the debug technician, which can be any combination of PCI, Mini-PCI and CardBus slots. This allows debugging of systems configured with another PCI-connected peripheral. Standard IEEE 1394 cables can be used for this purpose.
Note: For legacy-free or legacy-reduced sub-notebooks that are designed to implement IEEE 1394 as the debug solution, a combination of a Mini-PCI slot and CardBus slot is one possible solution. However, debugging over a mobile docking station with a PCI bridge is not a viable solution.
FAQ date: August 28, 2000; revised September 1; October 25, 2000
A1.5.17 S3 support and system test submissions (Revision)
A system preinstalled with either Windows 98 or Windows Me can provide a BIOS switch that disables S3. A system preinstalled with Windows XP/Windows 2000 must enable S3 by default in the BIOS. System test submissions for Windows 98, Windows Me, or both and that also support Windows 2000, Windows XP, or both must use the same BIOS for all submissions. In this case, S3 may be disabled in the BIOS for the Windows 98 and Windows Me test passes but S3 must remain enabled in the BIOS for Windows XP/Windows 2000 test passes.
For information about the effective dates for the S3 requirement, see A1.4.2.
FAQ date: January 31, 2001
A1.5.18 Accessibility requirements and regulations (Clarification)
[SYS-0020]
PC 2001 System Design Guide specified keyboard keys F1-F12 as having to be capable of being read and operated by software. This is incorrect; the guideline should have referred to the Fn key, an OEM-specific key often used on mobile PCs to control mobile-specific functions such as backlight brightness, CRT/LCD display switching, and so on.
Windows does not provide a keyboard scan code for the Fn key. StickyKeys cannot provide support for OEM-specific keys. System designers should provide access to all system functionality, including those functions only available through keyboard sequences involving the Fn key. The system BIOS can provide this StickyKey-like functionality.
Note: On December 21, 2000, the U.S. Access Board issued final standards for electronic and information technology under Section 508 of the Rehabilitation Act. OEM and IHVs are encouraged to review these standards as they pertain to their hardware designs. See http://www.access-board.gov/.
FAQ date: February 28, 2001
A1.5.19 Headset microphone requirement [Clarification]
A system is considered "speech capable" when the offering to customers indicates that speech is a viable input method for that system, which would therefore require a microphone to make that capability available. For example, if the platform includes an application that has the sole purpose of adding speech functionality to the system, then the system will be considered "speech capable.” However, if the system includes an application that merely supports speech input as an alternate input method, then that system is not considered "speech capable."
Note also that the inclusion of an array microphone that meets the microphone performance requirements in B3.1.4.13 also meets the requirement defined in A1.4.13.
FAQ date: April 30, 2001
A1.5.20 Number of USB ports required by system type [Clarification]
To facilitate migration away from legacy connections for keyboards, pointing devices, serial devices, and parallel devices, the logo program requirements identify how many USB ports are required for each system type. These requirements are defined in the various system type sections of Appendix A. This FAQ provides a summary:
-
General system requirement: One or more USB ports accessible by the user (A1.4.3)
-
Desktops: Two USB ports, with at least one accessible USB port supporting end-user expansion when keyboard and pointing device are attached (A2.4.1)
-
Mobiles: One USB port (A3.4.4)
-
Legacy-Free: Two USB ports, with at least one accessible USB port supporting end-user expansion when keyboard and pointing device are attached (A4.4.2)
-
Servers: One USB port (A6.4.2)
FAQ date: May 08, 2001
A1.5.21 System fans allowed to run in ACPI S1 state [Logo requirements change]
System fans may be run in the S1 state to cool the system. It is recommended that systems support advanced features like stopping the PCI clock when in S1 to allow the fans to be turned off.
FAQ date: May 08, 2001
A1.5.22 System board devices meet ACPI 1.0b [Clarification]
System board devices not power managed or configured via standard bus specifications must comply with ACPI 1.0b.
FAQ date: May 08, 2001
|
