Windows Logo Program

səhifə	5/37
tarix	18.07.2016
ölçüsü	1.03 Mb.

1 2 3 4 5 6 7 8 9 ... 37

WL-2. System memory provides a satisfactory user experience

Because objective benchmarks are not available, the intent of this requirement is to define a memory size that represents the baseline of acceptable Windows performance.

The following summarizes the Windows Logo Program performance requirements.

2001-2002 Minimum Equivalent Performance Requirements

x86-based systems	RAM
Windows 98/Me Windows 2000 Professional	64 MB
Windows XP Professional Windows XP Home Edition	128 MB [note 1, 2]
Windows 2000 Server Windows Whistler Server 1-2 processors installed >2 processors installed	[note 3] 512 MB 256 MB per processor
Windows 2000 Advanced Server Windows Whistler Advanced Server 1-4 processors installed > 4 processors installed	[note 3] 1 GB 256 MB per processor
Itanium-based systems	RAM
Windows XP Professional	1 GB
Windows Whistler Advanced Server 1-4 processors installed >4 processors installed	4 GB 1 GB per processor

Note 1: For systems with shared memory architecture and 128-MB system RAM, collectively, the drivers supporting integrated chipset functionality must not lock more than 32 MB. It is acceptable to use up to 8 MB from the 64-MB minimum in desktop and mobile PCs running Windows 98/Me or Windows 2000 Professional.

These maximum-page-locked-memory limits apply during all phases of system startup and normal operation. Page-locked graphics memory includes all frame buffers and buffers for hardware acceleration, texture and lighting, Z, and AGP. Page-locked audio memory includes all memory locked by the audio driver including all wave tables, and so on.

Dynamic memory allocation under the Windows environment is allowed, subject to the paged-locked memory limit. The driver cannot advertise or switch into a graphics mode that cannot be supported within the maximum locked memory limit.

Note 2: PC client systems must have at least the minimum system memory installed.

Note 3: Server system memory configurations specify the minimum allowed system memory to run the HCT. It is recognized that OEMs supply systems with specific feature requirements to corporations, which can include providing servers that do not include any preinstalled memory or that meet specific customer requirements for installed memory.

WL-3. System includes required set of buses and devices

The system must include the following buses, connectors, and devices, with driver solutions implemented as defined in the Windows DDK:

Primary storage host controller and primary hard drive.
Support for installing the operating system (CD/DVD drive or network adapter on desktop system).
Industry-standard internal buses and devices, excluding ISA slots and devices.
Industry-standard connectors with icons or labels.

Note: WHQL System Test Submission logs must include results with both modem and network adapter installed. Systems are not required to include a modem or network adapter in their shipping configurations.

Configure to order / Build to order requirements: PC clients shipped into retail markets must have at least the minimum hardware support listed in these requirements. Retail markets include:

Retail “on-shelf” configurations.
Published advertisements.
A default configure-to-order or build-to-order system configuration.

It is recognized that OEMs may configure PC systems to meet the requirements of a specific end-user or corporate customer. For systems built based on specific customer requests, where customers request systems without either a CD or DVD optical drive, the system may be configured without an optical storage drive. However, the system must support the addition of a CD or DVD optical drive, and the system firmware must support booting from a CD or DVD device using El Torito Version 1.0 No Emulation Mode if a supporting optical drive is added.

Furthermore, systems may be configured on request without a graphics adapter or network adapter. All retail market desktop systems must include a graphics adapter and support installation of an operating system by including either a CD/DVD drive or network adapter. [see A1.4.3, A1.1.4]

For more information about requirements for each type of system, see Appendix A, "System Requirements Checklist."

WL-4. All components and devices meet Windows compatibility and quality design guidelines

The compatibility and quality guidelines include requirements for devices, drivers, and software included with the system or retail component.

For specific feature and functionality requirements for each type of system, see Appendix A, "System Requirements Checklist."

Device Requirements

Any buses, devices, or other components offered with a Logo’d system or offered as a retail product carrying the "Designed for Windows" logo must pass related feature tests and operating system compatibility tests published by WHQL.

For the complete checklist of device and bus requirements, see Appendix B, "Device Requirements Checklist."

Driver and Software Requirements

These requirements ensure a good user experience when installing and using any component:

Windows-compatible driver support. Each device must have drivers for Windows XP/Windows 2000, plus support for other operating systems that may be preinstalled, as cited in requirement WL-1, "System and devices support required operating systems."
Windows-based driver installation. Driver installation and removal must use Windows-based methods, as defined in the Windows DDKs. For Windows XP/Windows 2000, this means only INF-based installation routines.
System component and installation integrity. Driver or software installation must not replace any Microsoft-authored system components and the driver must not bypass any operating system components. See http://www.microsoft.com/hwdev/sfp/wfp.htm.

Installation and loading of a driver must not reduce or eliminate the functionality of other devices installed on the system.

The driver must support unattended installation. That is, it must be possible to install the driver using a script or special software for supplying required parameters without the user being present during driver installation.

Minimum driver compatibility. Each driver must pass minimum compatibility, functionality, and stress testing as verified by the testing suites published by Microsoft WHQL for the related class.
Driver with special parameters includes Help file. To ensure that the user can correctly change settings, a Windows Help file must be provided if special driver parameters are used. This help file must install as part of the driver installation routine.
Driver Verifier. For each Windows XP/Windows 2000 driver, no errors can occur under the Driver Verifier facility provided with the operating system. Although Driver Verifier is not available for Windows 98/Me, every WDM driver should be tested with Driver Verifier on Windows XP/Windows 2000.

Poorly written kernel-mode drivers have the potential to cause the system to become unstable or stop working. Therefore, it is critical that all kernel-mode drivers be thoroughly tested to minimize this risk. For information about using Driver Verifier and diagnosing driver problems, see http://www.microsoft.com/hwdev/driver/driververify.htm.

Driver signing. All drivers installed on the system as shipped to the customer must be signed. Drivers submitted for Microsoft Windows Logo Program testing must meet the guidelines for driver signing as defined at http://www.microsoft.com/hwdev/desinit/digitsign.htm.

Other WHQL test programs that require digital signatures include the following:

Hardware Abstraction Layers (HALs): The purpose of the HAL test kit is to test third-party (non-Microsoft) HALs intended for use in server-class systems.

For details about what is tested for HALs, see Chapter 26, “HAL Test Specification,” in WHQL Test Specification.

Anti-virus software: WHQL launched a test program, related to the “Designed for Windows XP” Applications Logo Program, for anti-virus applications that include a kernel-mode file-system filter driver. Such applications that pass testing for Windows XP will receive a digital signature for their file-system filter driver, but not the entire application.

For details about what is tested for anti-virus software, see Chapter 21, “Anti-virus File System Filter Test Specification,” in WHQL Test Specification.
Note: Additional requirements related to driver and software quality may be added as tests become available.

Implementation Guidelines:
Windows DDKs at http://www.microsoft.com/ddk/

“New Technology” Requirements

For new or other technologies where specific compatibility tests have not been defined under the Windows Logo Program (as provided in the HCTs from WHQL), or where design guidelines have not been provided in a Design Guide, the following requirements apply:

Maintain system integrity. The implementation of the technology must not adversely affect the performance or stability of all functionality provided under the preinstalled operating system and under Windows XP/Windows 2000.
Use native operating system support whenever possible. If native support for the related feature is provided under a preinstalled version of Windows 98/Me or Windows XP/Windows 2000, comply with the related industry specification, create drivers based on Windows DDK guidelines, and meet the design requirements defined in PC 2001 System Design Guide or Hardware Design Guide Version 3.0 for Microsoft Windows 2000 Server.

For example, if the graphics adapter or monitor supports a digital video interface and is included on a system with Windows Me preinstalled, the implementation must follow the PC 2001 guidelines. Similarly, if the system supports IEEE 1394b and comes with Windows XP, comply with the industry specification, implement WDM minidriver support as defined in the Windows DDK, and follow the PC 2001 guidelines.

Follow the DDK and industry standards to ensure an upgrade path. If the feature is not supported natively in the preinstalled Windows operating system, comply with the related industry specification (if industry standards have been developed), follow Windows DDK guidelines for related bus and device class driver implementations, follow general Plug and Play and power management guidelines as defined in the Windows DDK, and plan an upgrade path for end users.

For example, if you design a system to include a new wireless technology for which there is no native operating system support, you must still use the related Windows driver model for adding support. In this example, driver support must be implemented as a Network Driver Interface Specification (NDIS) 5.0 miniport, as defined in the Windows DDK and cited in the guidelines for wireless devices in PC 2001 System Design Guide.

1 2 3 4 5 6 7 8 9 ... 37