| Answers to Frequently Asked Questions for Systems |
|
Last
updated on September 30, 1999
|
Q: Where can I find answers to questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Attention WHQL" or "Technical Questions".
Back to Questions
Q: Where are the "APIC Extensions to ACPI 1.0" referred to in "Basic PC 98" chapter, item 1?
A: APIC support must be in compliance with ACPI 1.0 by reporting the interrupt mechanism using the INT_MODEL field of the Fixed ACPI Description Table (Section 5.2.5) and including the Multiple APIC Description Table (Section 5.2.8). [October 13, 1997]
Back to Questions
Q: Where is the "Windows Hardware Instrumentation Implementation Guidelines, Version 1.0"?
A: This document is now available on http://www.microsoft.com/standards/top150/hardware.asp.
Back to Questions
Q: How often are the Test Tools and Test Procedures updated?
A: Test Kit releases are typically in sync with major releases of Micorsoft Operating Systems. However, some tests will need to be updated more frequently to keep in sync with the evolving operating system during beta releases. For example, WHQL posted monthly updates to the Test Kits until Windows 98 was RTM. Test kits are valid for two months after a new kit is released. For example, if you have a July Test Kit (ver 1.0), you are allowed to continue to use those Test Tools and Test Procedures for 60 days past the release of the August Test kit (ver 1.1).
Back to Top Ten QuestionsBack to Questions
Q: Where can I get information about the logo requirements?
A: Information on Microsoft Logo programs and requirements can be found on http://www.microsoft.com/hwdev/. This web site contains an extensive amount of data, including industry hardware specifications, whitepapers, FAQs and, of course, electronic copies of the SDG 2.0 and PC 99 Hardware Design Guides.
Back to QuestionsQ: Where can I get help resolving problems?
A: Before you contact WHQL or Microsoft Technical Support (MSTS), check the test description and Testing Erratafor the test you are having problems with. Test descriptions that have testing errata are linked to their errata items. If you still have problems to resolve after checking the Testing Errataand the WHQL Systems Support and FAQspage, you can find support URLs and email addresses on the Support and Problem Resolution page.
Back to Top Ten QuestionsBack to QuestionsQ: Where can I find answers to ACPI questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Technical Questions"
Back to Questions
Q: Where are the "APIC Extensions to ACPI 1.0" referred to in "Basic PC 98" chapter, item 1?
A: APIC support must be in compliance with ACPI 1.0 by reporting the interrupt mechanism using the INT_MODEL field of the Fixed ACPI Description Table (Section 5.2.5) and including the Multiple APIC Description Table (Section 5.2.8). [October 13, 1997]
Back to QuestionsQ: If a system does not support ACPI, can it get a PC 99 designation on the HCL and use the "Designed for Windows NT® and Windows 98®" Logo?
A: No, All systems and servers (except mini-notebooks) must have ACPI.
Back to QuestionsQ: My BIOS supports both APM and ACPI, What mode should I test Windows 98 in?
A: The system must be tested twice using the Microsoft® Windows® 98 operating system; once in APM mode and once in ACPI mode. A clean install of the operating system must be done between testing runs. Installing Windows 98 in APM mode and running the tests, then doing a fresh install of Windows 98 in ACPI mode, and running the tests again is the required method. This means all tests must be run in both APM mode and ACPI mode. You must return two log disks for Windows 98: one set of APM results and one set of ACPI results.
Back to QuestionsQ: What sleep/suspend modes must my system support to pass the ACPI test?
A: Currently, the ACPI test checks for BIOS compliance and functionality that has been exposed through the BIOS. The features and sleep states that the system supports are determined by each OEM. The Windows Logo Program requires the system to support On, Off and one sleeping state. That translates to S0, S5 and one of S1-S3. This is the same requirement the ACPI Test is looking for. Devices in the [ACPI] namespace (other than the legacy ISA timer, PIC, RTC and motherboard resources) are required to support four distinct configurations and be disableable. This requirement is tested with the current PnP test suite on Win98. PCI devices are required to support on and off, D0 and D3 respectively.
Back to QuestionsQ: If I test my ACPI system with version 9.0 or 9.1 HCTs and submit passing test results, what designation do I get?
A: The system will qualify for a PC 99 or SDG 2.0 (Server) designation on the HCL.
Back to QuestionsQ: Do I need to pass the ACPI Test when testing in APM mode, or the APM test when testing in ACPI mode?
A: No. If your system is running the tests in ACPI mode, the APM Test will result in a failure. If your system is running the tests in APM mode, the ACPI test will result in a failure. This is an acceptable failure.
Back to QuestionsQ: I'm having problems finding logo'd devices, where can I look?
A: In the System Self-Test kit the logo’d components test contains an index of all logo’d devices and drivers. This index is updated daily on http://www.microsoft.com/hwtest/. For the most accurate results, you must download the latest index and install it into your HCT installation. If you have failing devices with the latest index, you need to contact your IHV and discuss the problem.
Back to Top Ten QuestionsBack to QuestionsQ: It will be difficult to support wake-up events for ISA/EISA network adapters, making it expensive to write an NDIS 5.0 driver.
A: ISA-based devices are not eligible for the Windows logo under the 1998-1999 compliance guidelines. We recognize there still might be a market for ISA-based network adapters, but the performance requirements for PC systems that receive the Windows logo exclude ISA network adapters.
Back to QuestionsQ: Are network adapters required to wake up on receiving any type of packet?
A: See "Network Wake-up Events" in Power Management for Network Devices.
Back to QuestionsQ: How can I tell if my Windows 2000 system is in ACPI mode?
A: To verify that a Windows 2000 test system is in ACPI mode:
On the right side of the equal sign (=) is the name of the .dll file that defines the Hardware Abstraction Layer (HAL) that the system is currently using. If this filename is "halmacpi.dll", the system is in ACPI mode. If this filename is "halmps.dll", the system is NOT in ACPI mode, and acpi.sys is not loaded.
Back to QuestionsQ: Where can I find answers to audio questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email the audio group at acthelp@microsoft.com.
Back to QuestionsQ: How can I logo on-board AC97 components?
A: All AC97 components are motherboard components, even those on riser cards, for example, Modem Riser (MR), Audio/Modem Riser (AMR), etc. These AC97 components shall be tested in conjunction with a motherboard core logic chipset and the supporting BIOS revision. For more information, please see the AC 97 Testing proposal.
Back to QuestionsQ: Are ISA audio add-in cards acceptable? Is motherboard ISA audio the only acceptable answer?
A: Submissions of ISA audio solutions are no longer accepted.
Back to Questions
Q: Isn't the cost to achieve minimum 80dB is a little bit high, especially for low-priced Office PCs?
A: We believe that this standard can be met at a cost-effective price. In fact, most companies complained that 80dB is too low and does not sufficiently advance the industry.
Back to Questions
Q: Our design is implementing audio out as a headphone connection. Is this OK?
A: This is acceptable.
Back to QuestionsQ: Where can I find answers to display questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email the display group at dcthelp@microsoft.com.
Back to QuestionsQ: The minimum graphics memory requirement is 4 MB. This is too expensive for most PC systems.
A: The requirement for Basic PC 98 is approximately 2 MB for PC systems that support 2-D graphics. The requirement for systems that support 3-D graphics hardware is approximately 4 MB. However, the requirement emphasizes performance and feature capabilities, not a specific memory capacity.
Back to QuestionsQ: Isn't support for 3-D hardware acceleration, MPEG-2, and DVD-Video too much for notebook computers?
A: Notebook PCs are not required to support these features. (See item 14 in the "Mobile PC 98" chapter.) The PC 99 guidelines for notebooks and mini-notebooks make significant accommodations for the form-factor and heat-dissipation issues related to notebook designs.
Back to QuestionsQ: The VESA P&D connector should be recommended as video interface port connector.
A: This is not yet a widely recognized industry standard and there are no elements related to or affected by operating system behavior, so it is not included in the PC 99 guidelines. This is a guiding principle for other new technologies that are not addressed in the PC 99 guidelines: if there will not be operating system support available from Microsoft, the technology is not addressed.
Back to QuestionsQ: Regarding the requirement for a video port connection for hardware MPEG-II decoders: our graphics chip sets integrate an MPEG-2 decoder, and do not need the video port connection.
A: This requirement does not apply to integrated decoders.
Back to QuestionsQ: Is a 3-tap filter that can be turned on and off in software considered a Windows Logo Program compliant solution? Are we required to implement a selectable 2-tap or 3-tap filter?
A: A 3-tap minimum flicker filter is required that can be enabled and disabled by software. Capabilities for selecting the filter level are not required. [October 13, 1997]
Back to QuestionsQ: Why must all DVD-Video playback applications use the Microsoft DVD-Video API as part of Windows Logo Program compliance?
A: As listed on Fact Sheet for Windows Logo Program for Hardware,
WDM streaming and DirectShow are required for any MPEG-2 decoder hardware acceleration, with exceptions as noted for MPEG-2 hardware solutions provided with Windows 95 OSR 2 systems. Under this exception, the manufacturer must document the future availability of a WDM/DirectShow solution to ensure forward compatibility and easy upgrade for end users.
The Microsoft DVD-Video API includes more than just the higher level DirectShow functions that invoke it. This layer is the crucial application/decoder interface where compatibility will be maintained by Microsoft. There are three important parts to the Microsoft DVD-Video API:
All three are important for applications compatibility now and for future video playback enhancements. In particular, IDvdGraphBuilder does the complex job of creating the filtergraph by configuring the Navigator, the decoders supplied by IHVs or ISVs, and the overlay mixer. The Navigator parses the DVD stream and implements all higher-level DVD functionality (multiple languages, multiple angles, DVD menus, mouse event testing, and so on). The Overlay Mixer provides DirectDraw integration, deinterlacing, video window control, and the ability for applications to mix the UI on top of the video.
Microsoft wants to be able to ensure the widest possible range of compatibility across DirectShow titles playing on the PC. To get that, titles need to use the same APIs, and those APIs need to be supported across the board on all PCs. The best way to do this is to make sure that everyone is using the same interface, and in the case of DVD, the interface for movie playback is defined by the Navigator and the related components in the DVD-Video API.
There is no reason for ISVs to use navigators or other components that are not based on the DVD-Video API, either to support specific decoder implementations or to support content enhancements. It is easier and more compatible to support content enhancements using third-party DirectShow filters added into the playback filtergraph alongside the Microsoft navigator/splitter.
We have already seen supposedly DirectShow-compliant navigators that have extended the Microsoft Navigator using proprietary APIs. This is not good--it creates definite possibilities that games won't behave correctly or simply don't play because there is an inconsistency between the API used by the application and the navigator. There is the additional risk that other navigators will not fully implement the existing DVD API and also will not be keep up with advances and extensions to the DVD API as Microsoft makes them available.
Any of these inconsistencies can result in a broken PC. It also puts the onus on Microsoft for testing every navigator and then making sure all navigators upgrade when an operating system upgrade is installed. The best solution, as required for the Windows Logo Program, is for everyone to use the Microsoft DVD-Video API; no other solution will work universally for all users. [October 13, 1997]
Back to Questions
Q: Where can I find answers to IEEE 1394 questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Technical Questions".
Back to QuestionsQ: The requirement "Devices power their PHY at all times," in mobile PCs powered by battery causes short battery life.
A: This is a recognized issue, and mobile PCs are not required to meet this capability when running without an AC adapter. Notice also that an IEEE 1394 port is only recommended for mobile PCs.
Back to QuestionsQ: How can you recommend IEEE 1394 now for storage? Is there boot support in the operating system for this?
A: This is recommended in relation to the Device Bay initiative. Any device connecting to a IEEE 1394 bus should look like a native IEEE 1394 device to the operating system.
Back to QuestionsQ: Where can I find answers to processor questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Technical Questions".
Back to Questions
Q: If I have a system with a motherboard that takes 1-4 processors, and I want to logo it for a family with 3 different CPU speeds, how would I do that?
A: Make separate submissions for each CPU quantity, and the highest processor speed. A "family" of processors includes all of the processors of a given model at all available processor speeds. An exception to this rule is that the Intel® Pentium® III, Intel® Pentium® II and Intel® Celeron® processors can be considered to be of the same family for the purposes of multiple CPU speed submissions.
In this example there are 3 CPU speeds (450, 400 and 350) and a 1, 2, and 4 processor version.:
Submission #1:
450 MHz (4 CPU) : All required OS logs, payment and system.
List the lower speed models as marketing names.
Submission #2:
450 MHz (2 CPU) : All required OS logs, payment, etc. (No system required)
List the lower speed models as marketing names.
Submission #3:
450 MHz (1 CPU) : All required OS logs, payment, etc. (No system required)
List the lower speed models as marketing names.
Back to Questions
Q: The workstation requirement for ECC memory protection of the L2 cache shouldn't apply to RISC-based PCs, should it?
A: The intent of these requirements is that baseline performance is equivalent to the combination of the required base CPU plus L2 cache. There is not an explicit requirement for an L2 cache. Therefore, the stated requirement for ECC memory protection of the L2 cache applies only to Intel Architecture systems that include an L2 cache. Note also that ECC is only recommended. [October 13, 1997]
Back to Questions
Q: How can you require APIC support for workstations when the specification is not available to RISC-based systems?
A: This requirement does not apply for RISC-based systems, which have their own architecture for supporting interrupts. [October 13, 1997]
Back to Questions
Q: Where can I find answers to network communications questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email the network communications group at whqlnet@microsoft.com.
Back to Questions
Q: Can you please clarify the requirement that network adapters support the new remote system capabilities?
A: Item 14 in the "Network Communications" chapter requires the adapter to be compatible with remote new system capabilities if used as a boot device. This requirement is defined to ensure all network adapters carrying a Windows Logo for 1998-99 can support remote boot and that all Net PC and Office PC systems carrying the logo support remote boot out of the box.
Network adapters submitted to WHQL for 1998-99 Logo compliance testing must have this capability built in and enabled, whether the adapter is provided as an add-on device or integrated on the system board. This means that the adapter must have the socket for a boot PROM and the boot ROM must be installed to pass logo testing (this allows WHQL to test whether remote boot works with this card). However, if the vendor plans to sell these cards as standalone retail devices without the boot ROM installed, the packaging needs to indicate clearly that the remote boot capability is supported, but is available as an option.
Back to Questions
Q: It will be difficult to support wake-up events for ISA/EISA network adapters, making it expensive to write an NDIS 5.0 driver.
A: ISA-based devices are not eligible for the Windows logo under the 1998-1999 compliance guidelines. We recognize there still might be a market for ISA-based network adapters, but the performance requirements for PC systems that receive the Windows logo exclude ISA network adapters.
Back to QuestionsQ: Are network adapters required to wake up on receiving any type of packet?
A: See "Network Wake-up Events" in Power Management for Network Devices.
Back to Questions
Q: Where can I find answers to storage questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email the storage group at whqlstor@microsoft.com.
Back to Questions
Q: UltraDMA/33 should not be required for DVD or CD-ROM drives. It's too expensive.
A: UltraDMA/33 is not required for CD-ROM or DVD drives in the 1998-99 time frame. However, some vendors have implemented this feature for new higher-speed CD-ROM drives and have indicated that this support provides tremendous advantage in peripheral device-to-host transfers by doubling the transfer rate. UltraDMA is defined as a requirement in PC 99 System Design Guide.
Back to Questions
Q: The requirements for DVD-RAM are missing.
A: There are no requirements for DVD-RAM.
Back to Questions
Q: How can you recommend IEEE 1394 now for storage? Is there boot support in the operating system for this?
A: This is recommended in relation to the Device Bay initiative. Any device connecting to a IEEE 1394 bus should look like a native IEEE 1394 device to the operating system.
Back to Questions
Q: Where can I find answers to logo-related questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Attention WHQL"
Back to Questions
A: The Microsoft® Windows® Logo on hardware products lets customers know the products meet the Microsoft standards for compatibility with Microsoft Windows operating systems. The Microsoft Windows Logo Program for Hardware site presents information for system and peripheral manufacturers who want to participate in the Windows Logo Program for hardware.
Back to Top Ten QuestionsBack to Questions
Q: Why should I get the windows logo?
A: The Windows® brand is widely recognized by consumers. The Windows Logo on your product signals to customers that the product has been tested to verify that it meets Microsoft standards for compatibility with Windows. Licensing the Windows Logo allows you to leverage the world-wide awareness of the Windows brand.
Other benefits for Logo Partners include:
Back to Top Ten QuestionsBack to Questions
Q: How do I get the Windows Logo?
A: Logo compliance testing for hardware is conducted by Windows Hardware Quality Labs. To obtain the logo tests, see the WHQL web site at http://www.microsoft.com/hwtest/.
The Windows Logo Program requirements for hardware consists of the Hardware Compatibility Tests administered by WHQL, plus related Self-Test Checklists included in the Test Kit packages.
Note: Microsoft refers to PC 99 System Design Guide (and later design guides) as a guideline for the logo compliance tests administered by WHQL. The requirements in PC 99 System Design Guide do not in themselves define the requirements for the Windows Logo Program. PC 99 System Design Guide provides a series of design guidelines for PC systems and components that will result in an optimal user experience when the hardware is used with Microsoft Windows 32-bit operating systems.
Note also that the guidelines do not provide an exhaustive list of technical implementation issues for good hardware design under Windows 32-bit operating systems. Be sure to check the white papers on the web site at http://www.microsoft.com/hwdev/ frequently to ensure that you have timely information about design issues for components and systems.
Back to Questions
Q: The PC 99 guidelines don't define requirements for <many technologies> that we plan to use in our system design.
A: The PC 99 guidelines are simply that--guidelines, not a complete system definition. The focus for the Windows Logo Program is on requirements related to how the operating system works and the quality of the user experience. We are aware that many technologies are not addressed--from simple items that are omitted, such as requirements for the PC case and power supply, to new technologies that are just being introduced in the industry. If a technology is not listed in the guidelines or on Fact Sheet for Windows Logo Program for Hardware, is not part of the logo compliance tests, and if it does not conflict with any Windows Logo Program requirements or recommendations, then it's OK to include it in a system that's submitted for logo compliance testing.
Back to Questions
Q: Our company believes that one of our new system designs will provide a great platform for Windows, but it doesn't meet the definition of a Consumer PC or Office PC system.
A: The PC 99 guidelines defined mainstream system types. If you are developing a cutting-edge platform for Windows, please work with Microsoft to determine how your system can be included in the logo program. It is not Microsoft's intent to prevent innovation--but our interest is in truly innovative designs, not systems that simply lack one or two required features to cut costs.
Back to Questions
Q: The PC 99 guidelines take control of the PC away from the end user and give it to a systems administrator.
A: In fact, the PC 99 guidelines (as with the PC 97 guidelines) are the result of a great deal of research that included direct contact with end users, support personnel, and product designers. Extensive industry research indicates that the difficulty in expanding the user base among consumers and in controlling costs in corporate environments is related to the complexity of PC design, use, and maintenance.
To put it simply, the guiding principle for PC 99 is the belief that the user's primary desire is that networking (or audio or modem communications or any other feature) works correctly the first time and every time. The user's primary desire is not to be able to twiddle CMOS settings, toggle jump switches, or type entries in a configuration file.
To reduce end-user fear of complex technology and fear of obsolescence, and to reduce the mushrooming total cost of ownership for PCs, system complexity must be reduced. The PC 99 guidelines represent a series of phased changes supported by much of the PC industry in an effort to reduce both errors and costs while increasing ease of use, and are completely coordinated with changes that are being provided in the Windows 98 and Windows 2000 operating systems.
Back to Questions
Q: How can you require features that won't be available until Windows 2000 ships?
A: Logo compliance dates for requirements related to specific operating system support will be based on availability of operating system support, allowing sufficient time for vendor testing and development.
Back to Questions
Q: Are all features uniformly required, or are there exceptions based on locale?
A: Some locale-dependent requirements and exemptions are noted in PC 99 System Design Guide. Please work with your logo testing representatives to determine which requirements are not part of logo compliance testing for systems intended for specific locales.
Back to Questions
Q: What are the Logo Compliance Dates?
A: Please check the Microsoft HWDEV web site frequently for current information about logo compliance dates and other changes.
The following table lists specific features that have other dates when general requirements become part of logo compliance testing.
|
System requirements |
Compliance date |
|
System complies with the requirements of the 1999 Windows Logo Program, which are related to the guidelines defined in the PC 99 System Design Guide and Hardware Design Guide Version 2.0 for Windows NT Server. |
August 1, 1999 |
|
System does not include ISA expansion devices (PC98:3.28) |
January 1, 1999 for ISA modems and ISA audio |
|
System does not include ISA slots (PC98:3.28) |
January 1, 2000 |
|
System supports Windows Hardware Instrumentation Implementation Guidelines (WHIIG) (PC98:3.50-52) |
Compliance testing begins nine months after WHIIG v.1.0 is released. |
|
System includes support for features supported only under Windows 2000 |
Logo-compliant support provided no later than 60 days after Windows 2000 Release to Manufacturing (RTM) |
|
System includes support for features supported only under Windows 98 Service Pack |
Logo-compliant support provided no later than 60 days after Windows 98 Service Pack RTM |
|
System provides a licensed CSS copyright protection scheme |
CSS Phase II regionalization (RPC II) is not required until after January 1, 2000 |
|
Bus, device, or controllers |
Compliance date |
|
Devices use USB or external bus connections rather than legacy serial or parallel ports (PC98:13.7) |
July 1, 1999 for IR blasters. Until that date, these devices can be implemented as external RS-232 devices. |
|
Controllers comply with OpenHCI for IEEE 1394 (PC98:8.2) |
January 1, 1999 |
|
Digital Broadcast Television Requirements (PC98:15.29-39) |
January 1, 1999 |
|
January 15, 1999 for devices that use PCI connections or support hardware acceleration of DirectSound or DirectSound3D. |
|
|
PCI devices support non-DWORD-aligned audio buffers (PC99:17.22) |
January 1, 2000 |
|
Logo compliance testing based on Version 8.0 HCTs for network adapter requirements |
January 1, 1999 (Drivers must support at a minimum the same features under Windows 2000 and Windows 98) |
|
Network device supports wake-up events (PC98:20.40) |
Compliance testing begins with the release of Windows 2000. When testing begins, Wake-on-LAN support must pass testing with the same NDIS 5.0 drivery binary under Windows 2000 RTM, Windows 98 Retail with SP1, and Windows 98 OSR1. |
|
Hot swapping for PCI devices use ACPI-based methods (PC983:19) |
January 1, 1999 |
|
March 1, 1999 |
Back to Top Ten QuestionsBack to Questions
Q: How do I get my system components logo'd?
A: All components (display adapter, audio, etc.) shipping with your system must be logo’d before the system can be logo’d. You need to work with your IHV suppliers on getting their devices submitted to the appropriate device program in WHQL. Be aware that changes to a device or driver require a resubmission to WHQL for a retest.
Back to Top Ten QuestionsBack to Questions
Q: If I change components in my system, do I need to resubmit Test Logs?
A: If you are changing motherboard components, a full retest and resubmission of Test Logs is necessary. If you are changing add-in cards, and the add-in cards and drivers are logo’d, you do not need to resubmit system logs. Please note that the driver must also be logo’d.
Back to Top Ten QuestionsBack to Questions
Q: Where can I get information about the logo requirements?
A: Information on Microsoft Logo programs and requirements can be found on http://www.microsoft.com/hwdev/. This web site contains an extensive amount of data, including industry hardware specifications, whitepapers, FAQs and, of course, electronic copies of the current Design Guides.
Back to Questions
Q: How do I design my system to work with Windows?
A: To design your system to work with the Microsoft® Windows family of operating systems, follow the design guidelines laid down in the PC 99 System Design Guide and the Hardware Design Guide for Windows NT Server 2.0 (SDG 2.0). When designing your system, also be sure to use only components that carry the Windows logo and appear on the Hardware Compatibility List (HCL) for the operating system(s) you are planning to test with.
Back to Top Ten QuestionsBack to Questions
Q: Where can I find answers to Test Kit questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line "Attention WHQL".
Back to Questions
Q: Does the HCT kit support other language versions besides English?
A: The HCT kit provided by WHQL does not support other languages. Microsoft Japan (MSKK) does have a version of the HCTs that works with Japanese versions of the operating system, please contact MSKK for information.
Back to Questions
Q: Where can I get the newest version of the The Windows Hardware Quality Labs (WHQL) Hardware Compatibility Test (HCT) CD?
A: OEMs interested in obtaining the "Designed for Microsoft Windows" logos and listings on the Hardware Compatibility List (available at http://www.microsoft.com/hwtest/hcl) can now order the latest CD for a nominal fee from: http://www.microsoft.com/hwtest/hctcd. WHQL will no longer automatically ship CDs to all WHQL registered OEMs.
The current release has Self-Test programs for the following categories:
Back to Questions
Q: What Test Kit version should I be using?
A: The current Test Kit is version 9.0 and 9.1, and can be used to achieve PC 99 and SDG 2.0 designations on the HCL or can be used for PC 98 and SDG 1.0 refreshes. PC 98 submissions using HCT 8.0 are no longer allowed.
Back to Questions
Q: I can't read the document files in the HCT\DOCS folder of the HCT CD. Is there a program I can use to view the documents?
A: If you do not have access to Microsoft Word 97, you will be able to view the documents using Microsoft Word Viewer 97. This program is available as a free download from the Microsoft web site and is available in a 16-bit version (for Windows 3.x) and a 32-bit version.
Back to Questions
Q: How often are the Test Tools and Test Procedures updated?
A: Test Kit releases are typically on a quarterly schedule. However, some tests will need to be updated more frequently to keep in sync with the evolving operating system during beta releases. For example, WHQL posted monthly updates to the Test Kits until Windows 98 was RTM. Test kits are valid for two months after a new kit is released. For example, if you have a July Test Kit (ver 1.0), you are allowed to continue to use those Test Tools and Test Procedures for 60 days past the release of the August Test kit (ver 1.1).
Back to Questions
Q: I'm having problems finding logo'd devices, where can I look?
A: In the System Self-Test kit the logo’d components test contains an index of all logo’d devices and drivers. This index is updated daily on http://www.microsoft.com/hwtest/. For the most accurate results, you must download the latest index and install it into your HCT installation. If you have failing devices with the latest index, you need to contact your IHV and discuss the problem.
Back to Questions
Q: Where can I find answers to submission questions that are not listed on this FAQ?
A: If your question is not listed on this FAQ, email whqlinfo@microsoft.com, with the subject line " Attention WHQL".
Back to Questions
Q: What is the "WHQL Hardware Submission Process?"
A: A brief description of the WHQL submission process is as follows:
Devices: IHVs pretest devices using WHQL Test Tools and Test Procedures, submit devices, paperwork, and test logs to WHQL, WHQL verifies passing results and issues Test Report.
Systems: OEMs self-test using WHQL System Self-Test package, submit paperwork and test logs to WHQL, WHQL verifies passing results and issues Test Report.
Back to Questions
Q: Can I email my log files to WHQL?
A: No, WHQL does not accept emailed transmissions of log files.
Back to Questions
Q: Where can I get information about WHQL?
A: The WHQL website is at http://www.microsoft.com/hwtest/. This web site contains all the tools and documentation needed to you to participate in the Microsoft Hardware Logo programs.
Back to Questions
Q: How do I track my IHV submission status?
A: WHQL has provided a mechanism for checking submission status. You must first obtain the WHQL Submission ID of the device in question from the IHV. Then, at the WHQL Submission Status page, enter the Submission ID number. A brief summary of the current status of the submission is provided.
Back to Questions
Q: Where can I get help understanding the tests?
A: If you are having problems with WHQL System tests check the test description, the HCT Testing Errata, and the WHQL Systems Support and FAQspage. If you still need help understanding the tests, e-mail whqlsys@microsoft.comfor technical assistance. If you have testing questions not directly related to the System Test Tools, e-mail whqlinfo@microsoft.com and include the appropriate keyword in the subject line:
Artwork Request
Attention WHQL
Invoice Request
Test Report
Status Request
Technical Question
Back to Questions
Q: Where is the Hardware Compatibility List (HCL)?
A: A link to the HCL search engine can be found at the WHQL web site http://www.microsoft.com/hwtest. The HCL is updated every 24 hours.
Back to Questions
Q: If I change components in my system, do I need to resubmit Test Logs?
A: If you are changing motherboard components, a full retest and resubmission of Test Logs is necessary. If you are changing add-in cards, and the add-in cards and drivers are logo’d, you do not need to resubmit system logs. Please note that the driver must also be logo’d.
Back to Questions
Q: Can my Windows NT® system use a custom hardware abstraction layer (HAL)?
A: Yes. If a system uses a custom HAL (Hardware Abstraction Layer) for Windows NT® it must be sent to Microsoft for testing and is not eligible for self-test.
Back to Questions
Q: How do I submit my system for testing?
A: Read the Quick Step By Steppage for an overview of the WHQL submission process, and then read the System Submission Procedures for specific instructions.
Back to Top Ten QuestionsBack to Questions