HCT 10.0 Readme

Microsoft® WHQL
Hardware Compatibility Test Kits 10.0
for Microsoft Windows® XP Operating System

• Kit Setup and Installation
  • 1.0 - Kit Setup and Installation Issues
• Testing Issues and Errata
  • 2.0 - All Test Categories: General
    • Testing Issues
    • Errata
  • 3.0 - Audio
    • Testing Issues
    • Errata
  • 4.0 - Bus Controllers
    • Testing Issues
    • Errata
  • 5.0 - Display
    • Testing Issues
    • Errata
  • 6.0 - Driver Quality
    • Testing Issues
    • Errata
  • 7.0 - Imaging
    • Testing Issues
    • Errata
  • 8.0 - Input and HID
    • Testing Issues
    • Errata
  • 9.0 - Modems
    • Testing Issues
    • Errata
  • 10.0 - Network Devices
    • Testing Issues
    • Errata
  • 11.0 - Storage Controllers and Devices
    • Testing Issues
    • Errata
  • 12.0 - Streaming Media and Broadcast
    • Testing Issues
    • Errata
  • 13.0 - Systems
    • Testing Issues
    • Errata
  • 14.0 - Unclassified
    • Testing Issues
    • Errata

     

    The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

    Microsoft Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to the patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Microsoft Corporation.

    Microsoft does not make any representation or warranty regarding specifications in this document or any product or item developed based on these specifications. Microsoft disclaims all express and implied warranties, including but not limited to the implied warranties or merchantability, fitness for a particular purpose and freedom from infringement. Without limiting the generality of the foregoing, Microsoft does not make any warranty of any kind that any item developed based on these specifications, or any portion of a specification, will not infringe any copyright, patent, trade secret or other intellectual property right of any person or entity in any country. It is your responsibility to seek licenses for such intellectual property rights where appropriate. Microsoft shall not be liable for any damages arising out of or in connection with the use of these specifications, including liability for lost profit, business interruption, or any other damages whatsoever. Some states do not allow the exclusion or limitation of liability or consequential or incidental damages; the above limitation may not apply to you.

    Microsoft, PowerPoint, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.

    Copyright ® 2001 Microsoft Corporation. All rights reserved.

    ---

    Kit Setup and Installation

    

    The Microsoft Windows XP Hardware Compatibility Test (HCT) kit version 10.0 is a Windows application that runs the hardware compatibility tests and provides a quick summary of test results. The HCT kit requires a minimum 1 GB of free hard disk drive space on the system partition for temporary installation files, as well as enough additional drive space to accommodate the actual test kit. For additional test system configuration requirements, refer to the test procedure documentation for each test category.

    Install and review the test procedure documentation for a specific hardware test category before attempting to run the Hardware Compatibility Tests (HCT) kit. To have continuous access to the test procedures during testing, install the test procedure documents to a system other than the system used for testing. When you are ready to install the HCT kit, refer to How to use the HCT kit in the Introduction.

    Viewing the test procedure documentation

    The test procedures can be viewed from the Windows XP HCT 10.0 CD autorun screen, copied as a stand-alone application from the Windows XP HCT 10.0 CD, or installed with and viewed from Test Manager during a test run.

    To view the test procedure documentation from the HCT CD autorun screen

    1. Insert the HCT CD into a drive that supports autorun functionality.
       The Windows XP HCT 10.0 window displays.
    2. Click Read the HCT Kit Documentation.
       The HCT Help system displays.

    Note: This procedure opens the HCT Help system directly from the HCT CD. It does not install the HCT Help system locally.

    To copy the test procedure documentation from the HCT CD

    1. Insert the HCT CD into a drive that supports autorun functionality.
       The Windows XP HCT 10.0 window displays.
    2. Click Browse the CD.
       The contents of the HCT CD displays.
    3. Copy the Help folder to your system.
    4. Open the Help folder and double-click HCThelp.chm.
       The HCT Help system displays.

    To view the test procedure documentation from Test Manager

    Important: Test Manager will start only if a test category is installed at the same time as the test procedure documentation.

    1. Install the Windows XP HCT 10.0.
       Note: Test procedure documentation is selected to install by default.
    2. Start Test Manager.
    3. On the Help menu, click Help Topics.
       The HCT Help system displays.

    To view the test procedure documentation from Windows Start menu

    1. Install the Windows XP HCT 10.0.
       Note: Test procedure documentation is selected to install by default.
    2. Click the Start button, point to More Programs, point to HCT, and then click HCT 10.0 Documentation.
       The HCT Help system displays.

     

    1.0 - Kit Setup and Installation Issues

    

    Program: Setup and Installation

    1.1 - HCT installation wizard appears to restart immediately after finishing

    Issue: The Windows XP HCT 10.0 installation wizard appears to restart immediately after finishing a full installation.

    Double-clicking setup.exe repeatedly will cause the installation wizard to run a corresponding number of times.

    Solution: If the Windows XP HCT 10.0 installation wizard appears to restart immediately after finishing a full installation, or multiple instances of the installation wizard start on the test system, click Cancel as soon as possible to end the unnecessary installations. Continuing with a second installation may cause errors in Windows XP HCT 10.0.

    To avoid this problem, double-click setup.exe one time only.

    Program: Setup and Installation

    1.2 - Test Manager initialization error

    Issue: Attempting to start Test Manager results in the following error message:

    missing devices.ini

    This error can occur if the HCT folder created for a previous installation of the kit is not deleted from the test system during uninstallation of the HCT kit.

    Solution: Use the Windows Add/Remove Programs application to uninstall the HCT kit, manually delete the HCT folder from the test system, and then install the HCT kit again.

    For more information on uninstalling the HCT kit, see To uninstall the Windows XP HCT 10.0 kit in the Windows XP HCT 10.0 test procedure documentation.

    Program: Setup and Installation

    1.3 - Minimum hard disk drive space requirements for the Windows XP HCT 10.0 kit

    Issue: The test system does not have enough free hard disk drive space on the system partition to install the Windows XP HCT 10.0 kit, even when the Windows XP HCT kit is not installed on the system partition.

    Solution: When the HCT kit is installed on test systems with 128 MB of RAM, the paging file may use all available space on the system partition. If this occurs, move the paging file to another partition. If possible, move the paging file to another physical hard disk drive rather than a partition on the same hard disk drive. Then, reinstall the HCT kit.
    
    

    Important: Do not attempt to move the paging file during a test run. The HCT kit will detect the configuration change and require the user to delete all existing test logs and reinstall the kit.

    
    

    To move the paging file

    1. In Control Panel, double-click System.
       The System Properties dialog box displays.
    2. On the Advanced tab, under Performance, click Settings.
       The Performance Options dialog box displays.
    3. On the Advanced tab, under Virtual memory, click Change.
    4. Create a new paging file.
       
       • Under Drive [Volume Label], click the drive where you want to create the paging file.
         Under Paging file size for selected drive, click System managed size, and then click Set.
       -or-
       
       
       • Under Paging file size for selected drive, click Custom Size, and type a new paging file size in megabytes in the Initial size (MB) or Maximum size (MB) box, and then click Set.
    5. Delete the existing paging file.
       • Under Drive [Volume Label], click the drive that contains the paging file you want to delete.
         Under Paging file size for selected drive, click No paging file, and then click Set.

     

    Testing Issues and Errata

    

    2.0 - All Test Categories: General

    

     

    General Testing Issues

    Program: General

    2.1 - 1394 Asynchronous and Isochronous Loopback test error

    Issue: When running the 1394 Asynchronous and Isochronous Loopback test the following error message may be generated:

    "Unable to allocate listen test 1 resource for host controller x" (where x is 0 or 1)

    Solution: Restart the system and re-run the 1394 Asynchronous and Isochronous Loopback test.

    Program: General

    2.2 - USB Manual Interoperability test configuration

    Issue: When running the USB Manual Interoperability test with speakers installed, you may be requested to use a USB Human Interface Device (HID) on the speakers. If you skip testing for this device, the following error in the log file is generated:

    "6E0.0F4 : +TEST+SEV1 : Assertion 9.18.45: Skipping testing for USB Human Interface Device"

    Solution: While the USB Manual Interoperabililty test runs, use the HID controls on the device. For example, many USB speakers have a volume control and/or mute button. Press the button multiple times to demonstrate data transfer.

    Program: General

    2.3 - Several tests do not run on 64-bit systems

    Issue: The following tests do not run in the Windows XP HCT 10.0 kit or the Windows Display Compliance Test (DCT) 450 kit on the specified test category when these kits are installed on 64-bit systems:

    All test categories:

    • USB Address Description test
    • USB Device Control Requests test
    • USB Enumeration Stress test
    • USB Port Reporting test
    • USB Selective Suspend test

    Audio:

    • Audio Power Management (Lullaby)test
    • Digital Rights Management test

    Keyboards:

    • ChkINF test

    Printers:

    • 16-Bit Printing test

    All Systems:

    • Server-Client Stress test

     

    Solution: Do not run these tests on 64-bit systems for the indicated test programs.

    Programs: General, USB Controller, Network Device, System

    2.4 - USB test devices do not wake from sleep mode

    Issue: USB devices capable of generating a wake event, such as mice and keyboards, do not wake the system from sleep mode when running the following tests:

    • USB Device Wake Up test
    • LAN Device Wake Up test
    • [FoxFire] PCI 3.3 Volt Auxiliary Power Load test

    Solution: Enable the test device to remotely wake the system with the following procedure:

    1. From the Windows desktop, click Start, and then click Control Panel.
    2. In the Control Panel window, click Performance and Maintenance.
    3. In the Performance and Maintenance window, click System.
    4. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
    5. In the Device Manager window, select the test device you want to wake the system.
    6. On the Action menu, click Properties.
    7. In the Properties dialog box for the selected device, click the Power Management tab.
    8. Select the Allow this device to bring the computer out of standby check box, and click OK.
    9. Close all windows.
    10. Start Test Manager and run the test.

    Program: General

    2.5 - Restart necessary if system cannot go to S3 state

    Issue: The system may be unable to go into the S3 state when running tests that are required to evoke an S3 state. If this occurs, the message that the device driver is preventing the machine from entering standby displays.

    Solution: Restart the test system with the following procedure:

    1. From the Windows desktop, click Start, and then click Shut down.
    2. In the Shut Down Windows dialog box, in the What do you want the computer to do? list, click Restart, and then click OK.
    3. If prompted, in the Log on to Windows dialog box, type the user name, password, and domain, and then click OK.
    4. Restart Test Manager and rerun the test.

       Note: If this problem persists after restarting the system, obtain an updated driver for the device that is preventing the system from entering S3 state.

    Program: General

    2.6 - Disable all Screen Savers and Power Schemes on the test system before running Test Manager

    Issue: Screen Savers and Power Schemes may interfere with HCT testing.

    Solution: Ensure that Screen Savers and Power Schemes are disabled before running HCT tests:

    To disable screen savers

    • On the taskbar, click the Start button, and then double-click Control Panel.
    • Click Switch to Classic View.
    • Double-click Display.
    • In the Display Properties dialog box, click the Screen Saver tab.
    • In the Screen Saver list box, select (None).
    • Click OK.

    To disable power schemes

    • On the taskbar, click the Start button, and then double-click Control Panel.
    • Click Switch to Classic View.
    • Double-click Power Options.
    • In the Power Options Properties dialog box, click the Power Schemes tab.
    • In the Power Schemes list box, select Home/Office Desk.
    • Click OK.

    General Errata

    Program: General

    Errata ID: 390

    Test & Log: Enable/Disable - Device I/O test; Nftest.log

    Title: Enable/Disable - Device I/O test does not support dynamic volumes

    Issue: The Enable/Disable - Device I/O test does not support dynamic volumes.

    Solution: Do not run the Enable/Disable - Device I/O test on dynamic volumes.

    General Errata

    Programs: General, 1394 Controller, USB Controller

    Errata ID: 391

    Test & Log: PCI Latency test; Latency.log

    Title: PCI Latency test false failures on 1394 controllers and USB controllers

    Issue: When running the PCI Latency test, false failures may occur on devices other than the test device, for example, PCI-based 1394 controllers and USB controllers.

    Solution: This is an acceptable failure on devices other than the test device. The test incorrectly runs on all PCI devices instead of only the test device. You can determine if you have false failures on devices other than the test device by inspecting the Latency.log file. When making a test submission package with a failed log due to this issue, please include a cover letter or Readme.txt that refers to this issue with the errata ID number.

     

    3.0 - Audio

    

    Audio Testing Issues

    Programs: Audio and Systems

    3.1 - Wave Driver test intermittent failure

    Issue: When running the Wave Driver test, intermittent failures may occur with test case 16.9:12.

    Solution: This failure occurs due to timing issues on the test system. Re-run the Wave Driver test. Do not interact with the test system until the test completes. Focus on the test window must be maintained.

    Program: Audio

    3.2 - Digital Rights Management test configuration for GFX

    Issue: When running the Digital Rights Management test in the Audio Global Effects (GFX) Filter test category, the test fails due to no supported devices found. The failing test log does not adequately explain the cause of the failure.

    Solution: Verify that the GFX filter is properly associated with the installed audio solution before running the Digital Rights Management test.

    Program: Audio

    3.3 - Two-system test configuration not required for USB audio devices

    Issue: The two-system tests, Audio Power Management (Lullaby) test and PC Audio Requirements test, run on a single system configuration when testing USB audio devices.

    Solution: When testing USB audio devices, a two-system test configuration is not needed. Install the HCT 10.0 audio test category for the test or host system only. This is the default kit installation. Do not install the server or remote audio test category.

    Audio Errata

    Program: Audio

    Errata ID: 392

    Title: External volume controls require manual adjustment during loopback testing

    Issue: If the external volume control of headphones or other audio output jacks is too high, cable detection fails and the following tests do not start:

    • Audio Power Management (Lullaby) test; Lullabyst.log
    • PC Audio Requirements test; Pcaudreqst.log
    • Direct Sound Driver test; Dsdrvtst.log
    • Full Duplex and test; Fduplex.log

    Solution: The test cannot control the external volume control. The user must manually set the volume control of headphones or other audio output jacks to 2% above the Off setting and then increase the volume by increments of 2% until the cable is detected. The test will start and/or continue when the cable is detected.

    Program: Audio

    Errata ID: 393

    Test & Log: Audio Power Management (Lullaby) test; Lullabyst.log

    Title: Audio Power Management (Lullaby) test failures on Audio Software Synthesizer

    Issue: When running the Audio Power Management (Lullaby) test in the Audio Software Synthesizer test category, failures may occur on devices other than the test device.

    Solution: This is an acceptable failure on devices other than the test device. The test incorrectly runs on all audio devices instead of only the test device. When making a test submission package with a failed log for this test, please include a cover letter or Readme.txt that refers to this issue with the errata ID number.

     

    4.0 - Bus Controllers

    

    Bus Controller Testing Issues

    Program: 1394 Controller

    There are no testing issues for this program.

    Program: CardBus/PCMCIA Controller

    There are no testing issues for this program.

    Program: Infrared (IrDA) Controller

    There are no testing issues for this program.

    Programs: General, USB Controller, Network Device, System

    4.1 - USB test devices do not wake from sleep mode

    Issue: USB devices capable of generating a wake event, such as mice and keyboards, do not wake the system from sleep mode when running the following tests:

    • USB Device Wake Up test
    • LAN Device Wake Up test
    • [FoxFire] PCI 3.3 Volt Auxiliary Power Load test

    Solution: Enable the test device to remotely wake the system with the following procedure:

    1. From the Windows desktop, click Start, and then click Control Panel.
    2. In the Control Panel window, click Performance and Maintenance.
    3. In the Performance and Maintenance window, click System.
    4. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
    5. In the Device Manager window, select the test device you want to wake the system.
    6. On the Action menu, click Properties.
    7. In the Properties dialog box for the selected device, click the Power Management tab.
    8. Select the Allow this device to bring the computer out of standby check box, and click OK.
    9. Close all windows.
    10. Start Test Manager and run the test.

    Program: USB Controller

    There are no testing issues for this program.

    Program: USB Hub

    4.2 - USB Interoperability test configuration

    Issue: The USB Interoperability test does not detect that the USB test hub is connected to the system.

    Solution: The three 4-port self-powered USB hubs, used to construct the USB tree during testing, must be different from the USB test hub. The USB test hub must have a unique vendor identification (VID) and unique product identification (PID).

     

    Bus Controller Errata

    Programs: General, 1394 Controller, USB Controller

    Errata ID: 394

    Test & Log: PCI Latency test; Latency.log

    Title: PCI Latency test false failures on 1394 controllers and USB controllers

    Issue: When running the PCI Latency test, false failures may occur on devices other than the test device, for example, PCI-based 1394 controllers and USB controllers.

    Solution: This is an acceptable failure on devices other than the test device. The test incorrectly runs on all PCI devices instead of only the test device. You can determine if you have false failures on devices other than the test device by inspecting the Latency.log file. When making a test submission package with a failed log due to this issue, please include a cover letter or Readme.txt that refers to this issue with the errata ID number.

    Program: CardBus/PCMCIA Controller

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Infrared (IrDA) Controller

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: USB Hub

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

    5.0 - Display

    

    Display Testing Issues

    Program: Display Adapter

    There are no testing issues for this program.

    Program: Display Monitor

    There are no testing issues for this program.

     

    Display Errata

    Program: Display Adapter

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Display Monitor

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

     

    6.0 - Driver Quality

    

    Driver Quality Testing Issues

    Program: Anti-Virus/File System Filter Driver

    There are no testing issues for this program.

     

    Driver Quality Errata

    Program: Anti-Virus/File System Filter Driver

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

    7.0 - Imaging

    

    Imaging Testing Issues

    Program: Camera

    There are no testing issues for this program.

    Program: Printer

    7.1 - Windows Application Compatibility test prints undocumented PowerPoint page

    Issue: When running the Windows Application Compatibility test, the test case for the Microsoft® PowerPoint® presentation graphics program prints an undocumented page. This document is named PPT_PR.PPT and "Results" is printed at the top of the page.

    Solution: Verify that the printout on this page is correct.

    Programs: Printer and Scanner

    7.2 - Surprise Removal test not required

    Issue: The Printer testing overview and the Scanner testing overview topics in the test procedure documentation incorrectly list the Surprise Removal test.

    Solution: Do not run the Surprise Removal test for printers or scanners with the Windows XP HCT 10.0 kit. This test is not available for the Printer and Scanner test categories at this time, but will be available in a later test kit.

     

    Imaging Errata

    Program: Camera

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Printer

    Errata ID: 395

    Test & Log: Image Color Management Profile test; Profwiz.log and Windows Color Quality Compliancy Test for Printers; printcolor.log

    Title: Image Color Management Profile test and Windows Color Quality Compliancy Test are required for Printers

    Issue: The Image Color Management Profile test and the Windows Color Quality Compliancy for Printers test topics in the test procedure document incorrectly contain the following note:

    "Important: Do not not run this test if the test device is sRGB compatible and the default sRGB Color Space Profile.icm profile is used."

    Solution: The Image Color Management Profile test and the Windows Color Quality Compliancy Test for Printers are required for all Printers even if they do not implement their own profile and, therefore, use the default sRGB Color Space Profile.

    Note: Monochrome printers should use the default sRGB profile when running these tests.

    Program: Scanner

    Errata ID: 396

    Test & Log: Windows Image Acquisition Minidriver test; Wiatest.log

    Title: Windows Image Acquisition Minidriver test rotation property false failure

    Issue: When running the Windows Image Acquisition Minidriver test, false failures may occur with scanners that implement the optional read/write WIA_IPS_ROTATION property.

    Solution: This is an acceptable failure. The test incorrectly assumes the WIA_IPS_ROTATION property is a read only property. When making a test submission package with a failed log due to this issue, please include a cover letter or Readme.txt that refers to this issue with the errata ID number.

     

    8.0 - Input and HID

    

    Input and HID Testing Issues

    Program: Game Device

    There are no testing issues for this program.

    Program: Keyboard

    There are no testing issues for this program.

    Program: Keyboard-Video-Mouse Switch

    There are no testing issues for this program.

    Program: Pointing and Drawing Device

    There are no testing issues for this program.

    Program: Smart Card Reader

    There are no testing issues for this program.

     

    Input and HID Errata

    Program: Game Device

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Keyboard

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Keyboard-Video-Mouse Switch

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Pointing and Drawing Device

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Smart Card Reader

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

    9.0 - Modems

    

    Modem Testing Issues

    Program: Modems

    9.1 - NDIS test false failures

    Issue: After completion of the Fax test, the Fax component on the server system answers calls sent by the client (test) system during portions of the NDIS test that require two-system communication (the two-system test cases).

    Solution: Complete the following steps to disable the Fax Test Server component immediately after the Fax test has completed.

    1. From the Windows desktop, click Start, then click Printers and Faxes.
    2. Double-click Faxes.
    3. In the Fax Console window, click Tools, and then click Fax Printer Configuration.
    4. Click the Devices tab, and then click the appropriate modem used for the Fax Test Server test.
    5. Click Properties.
    6. Click the Send tab, and then clear the Enable device to send check box.
    7. Click the Receive tab, and then clear the Enable device to receive check box.
    8. Click Apply, and then click OK.
    9. Close all windows.

     

    Program: Modems

    9.2 - Fax Test Modem test fails on test systems on which previous installations of the modem has been installed.

    Issue: The Fax Test Modem test will false fail a modem if there has been a previous instance of that modem on the test system. For example: if a GenericSoft56K type modem was installed, then removed, the operating system will remember that instance of the modem and list it in the Modem's properties in Control Panel. If that modem is reinstalled in the same test system, it will be installed as a "GenericSoft56K #2". The test detection code is looking only for the literal ID string, i.e. "GenericSoft56K", it will not successfully identify the second instance of the physical modem, "GenericSoft56K #2", but will default to the first instance of the modem. Since only the "ghost" modem will be detected, the Fax test will always fail.

    Solution: To remove previous instances of the modem, follow this procedure:

    1. Click Start, then Control Panel, then Network and Internet Connections, then Phone and Modem Options.
       The Phone and Modem Options window opens.
    2. Click the Modems tab. All modem instances will be viewable on the screen.
    3. Delete all modems viewable on this list by selecting each modem and clicking Delete.
    4. Now add the appropriate test modem back by clicking the Add tab.
       The Add New Hardware Wizard screen opens.
    5. In the Install New Modem screen click Next.
    6. If the modem is not found during the hardware detection step, click the Have Disk button and navigate to the location of the INF file for the test modem, then click OK.
    7. Click Next.
    8. Click Next.
    9. Exit all windows.

     

    Program: Modems

    9.3 - Wireless Zero Configuration service interferes with NDIS test for wireless modem devices

    Issue: Wireless Zero Configuration services interfere with NDIS test for wireless modem devices. Normally the NDIS test stops and restarts this service during the test. However, occasionally the service fails to stop, and a pop up windows appears with the following message:

    "Failed to stop Wireless Zero Configuration Service".

    Solution: When testing Modems other than Wireless modem devices, click OK to continue.

    For wireless modem devices, follow this procedure:

    • Click Start, then type cmd at the command window. This opens a command prompt window.
    • At the command prompt, type in net stop wzcsvc. This stops the Wireless Zero Configuration service.
    • Close the command prompt window.

     

    Program: Modems

    9.4 - The NDIS test reports incorrect server back channel information.

    Issue: The server-side devices (either the Ethernet back channel adapter or the reference modem device) do not accurately identify themselves to Test Manager on the server system.

    Solution:

    1. Quit Test Manager on the server system.
    2. Restart the server system.
    3. Restart Test Manager on the server system.
    4. start NDIS testing on the client system

     

    Program: Modems

    9.5 - ACPI Stress - Device I/O (Extended - Modem) test not required for external serial modems

    Issue: Although the ACPI Stress - Device I/O (Extended - Modem) test is not required for external serial modems, it is listed incorrectly in the Available Tests for Selected Test Category pane in Test Manager.

    Solution: Do not select the ACPI Stress - Device I/O (Extended - Modem) test from the Available Tests for Selected Test Category pane in Test Manager when testing external serial modems. It is not a required test for this type of modem.

    Programs: Modem

    9.6 - Reference Courier I modem INF file doesn’t include some ISDN switch types

    Issue:

    The INF file used during the installation of the Courier I reference modem excludes some types of ISDN switches. When configuring the reference modem before beginning HCT testing of a modem, the ISDN switch type that the reference modem will need for communication with the ISDN switch may be missing.

    Solution:

    If the correct ISDN switch type is not an option, select the National ISDN 1 (NI-1) switch type. The Courier I modem has auto sensing switch capabilities. These configure the reference modem for the correct ISDN switch type.

     

    Modem Errata

    Program: Modems

    Errata ID: 397

    Test & Log: ACPI Stress - Device I/O (Extended - Modem) test, Pmte.log

    Title: ACPI Stress - Device I/O (Extended - Modem) test fails on integrated modem devices

    Issue: The ACPI Stress - Device I/O (Extended - Modem) test fails on modems integrated onto mobile system motherboards . The failure is due to the conflict between the two power states that the mobile system may support (either S1 or S3, AND either S4 or S5) and the three power states that the ACPI test verifies (S1, S3, and S4). Because the mobile system supports fewer power states than the ACPI test verifies, the test fails and returns the following message in the log file:

    ERROR: Work item completed with Error Code: -1073721812
ERROR: The system does not support the S1 , S3 , and the S4 system power states required for device certification.
ERROR: PMTE_CheckForMustSupportedSleepStates(): System doesn't support sleep state S1

    Solution:

    To test integrated modems

    1. Run all modem tests in the HCT, with the exception of the ACPI Stress - Device I/O (Extended - Modem) test.
    2. Return all test logs to one .cab file.
    3. Install the Mobile System HCT kit.
    4. Run the ACPI Stress - Device I/O (Extended - Modem) test from that kit.
    5. Return the single log to one .cab file.
    6. Include both .cab files with your submission.
    7. Include a readme.txt files with your submission that refers to this issue with the errata ID number.

     

     

    10.0 - Network Device

    

    Network Device Testing Issues

    Programs: Network Device

    10.1 - ACPI Stress - Device I/O (NIC) test does not cancel immediately when "Cancel Script" is selected

    Issue: The ACPI Stress - Device I/O (NIC) test takes eight minutes to close after Cancel Script is selected from the Test menu in the PM Test Shell window (PM stands for power management). Additionally, if you close the command window that appears while running this test, the test does not complete successfully.

    Solution: Wait for the Cancel Script command to complete, and do not close the command window while the test is running.

    Program: Network Device

    10.2 - Identical test devices recommended, but not required, as support devices for NDIS test

    Issue: The NDIS test requires a server and client (test) system, and multiple network devices in either system. Two standard Ethernet cards are used for back channel communication (one each in the client [test] and server systems), the test network device in (or attached to) the client (test) system, and a similar (or identical) network device in the server system, This last network device is referred to as the support device.

    If the support device isn’t identical to, or provide the same functionality as the test device, NDIS test failures may occur.

    An additional support device may be installed in the client (test) system to verify multiple network device functionality. In this case the support device installed across the PCI bridge must be identical.

    Solution: If identical network devices are not used during the NDIS test, insure that all network devices used for support card operation during testing provide identical functionality.

     

    Programs: Modems, Network Device, and Systems

    10.3 - Wireless Zero Configuration services interfere with NDIS test for wireless network devices

    Issue: The Wireless Zero Services interfere with the NDIS test for wireless network devices. Normally, the NDIS test stops and restarts this service during the NDIS test. However, occasionally the service fails to stop, and a window appears with the following message:

    "Failed to stop Wireless Zero Configuration Service."

    Solution: When testing Modems, Systems, and Network devices other than wireless network devices, click OK to continue.

    For wireless network devices, follow this procedure:

    1. From the Windows desktop, click Start and then Run.
    2. In the Open box, type cmd and click OK. A command prompt window opens.
    3. At the command prompt, type net stop wzcsvc. This stops the Wireless Zero Configuration Service.
    4. Close the command prompt window.

     

    Program: Network Device

    10.4 - Remote Boot test not required for USB LAN devices

    Issue: Although the Remote Boot test is not required for USB LAN devices, it is incorrectly listed in the Available Tests for Selected Test Category pane in Test Manager.

    Solution: Do not select the Remote Boot test from the Available Tests for Selected Test Category pane in Test Manager when testing USB LAN devices. It is not a required test for USB LAN devices.

     

    Program: Network Device

    10.5 - Server-side LAN Device Wake Up test not required for cable modems

    Issue: The LAN Device Wake Up test requires communication with a remote test host (referred to as the server system). Although the server-side version of LAN Device Wake Up test is not required for cable modems, it is incorrectly listed in the Available Tests for Selected Test Category pane in Test Manager.

    Solution: Do not select the LAN Device Wake Up test from the Available Tests for Selected Test Category pane in Test Manager when testing cable modems. It is not a required test for cable modems.

     

    Program: Network Device

    10.6 - LAN Device Wake Up test not required for non-self-powered USB LAN devices

    Issue: Although the LAN Device Wake Up test is not required for USB LAN devices, it is listed incorrectly in the Available Tests for Selected Test Category pane in Test Manager.

    Solution: Do not select the Remote Boot test from the Available Tests for Selected Test Category pane in Test Manager when testing non-self-powered USB LAN devices. It is not a required test for non-self-powered USB LAN devices.

     

    Program: Network Device

    10.7 - Network Adapters must have Wake On LAN enabled before running NDISTEST (Manual), Phase 1, Phase 2, and Driver Verifier (NDIS)

    Issue: Network Adapters must have Wake On LAN enabled before running NDISTEST (Manual), Phase 1, Phase 2, and Driver Verifier (NDIS). Wake On LAN must then be disabled after NDISTEST (Manual), Phase 1, Phase 2, or Driver Verifier (NDIS) completes.

    Solution: Follow the instructions below to disable Wake On LAN before running these tests and to enable Wake On LAN after running these tests:

    To enable Wake On LAN

    1. On the task bar, click the Start button, and then click Control Panel.
    2. In Control Panel, click Administrative Tools.
    3. In Administrative Tools, click Computer Management.
    4. In Computer Management, click Device Manager.
    5. Click the plus sign (+) next to Network Adapters.
    6. For each network adapter listed:
       1. Right-click the network adapter and select Properties.
       2. Click the Power Management tab.
       3. Select the Allow this device to bring the computer out of standby check box.
       4. Click the Advanced tab.
       5. In the Property list box, select Enable PME, and then select Enable in the Value list box.
    7. Click OK.

    To disable Wake On LAN

    1. On the task bar, click the Start button, and then click Control Panel.
    2. In Control Panel, click Administrative Tools.
    3. In Administrative Tools, click Computer Management.
    4. In Computer Management, click Device Manager.
    5. Click the plus sign (+) next to Network Adapters.
    6. For each network adapter listed:
       1. Right-click the network adapter and select Properties.
       2. Click Power Management.
       3. Clear the Allow this device to bring the computer out of standby check box.
    7. Click OK.

     

    Program: Network Device

    10.8 - NDIS and Driver Verifier test failures on 64-bit platforms

    Issue: During the NDIS and Driver Verifier tests, both tests invoke the 2c_loadUnload.wsf test script, which performs additional driver functional testing. However, this script fails.

    Solution: Immediately after NDIS or Driver Verifier begins, the NDIS test shell opens. Follow this procedure to place the NDIS test in manual mode and clear the 2c_loadUnload.wsf script:

    1. Click Stop Test in the NDIS test Shell.
    2. Clear the WHQL Mode option, and select the Manual option.
       

       Note: Running the NDIS test in manual mode will cause the test log to report the test as a failure; so include a note about this release note when making submissions for this issue.

    3. Clear only the 2c_loadUnload.wsf test.
    4. Click Start.

     

    Program: Network Device

    10.9 - Driver Verifier - NDIS test error message

    Issue: Driver Verifier - NDIS test invokes functionality contained in the Enable/Disable Device I/O (Network) test. As this test runs it displays the following error message several times during the test run:

    The network path not found

    Solution: Disregard this error message. No user action is required.

     

    Program: Network Device

    10.10 - Fatal system error on the server system when testing NDIS for IA64 systems

    Issue: The NDIS test requires a server system (with the HCT 10.0 installed) for communication with the client system during testing. However, when running the NDIS test on IA64 platforms, the Server system exhibits a fatal system error (blue screen) when the client system attempts to communicate with it.

    Solution: For IA64 NDIS testing, use a 32 bit platform for the server system, with the corresponding 32-bit version of the HCT 10.0.

    Program: Network Device

    10.11 - NDIS test Wake On LAN detection problem

    Program: Network

    Issue: During the NDIS test, the Wake On LAN (WOL) functionality is verified. However, this functionality is not required and may not be supported for the following classes of devices:

  • Broadband devices (such as cable modems and xDSL)
  • CardBus/PCMCIA devices
  • IrDA devices
  • integrated (on the motherboard) network devices
  • LAN emulation devices
  • Mobile systems
  • Multifunction devices
  • Server LAN (such as multiport, FDDI, or Gigabit Ethernet) devices
  • Wireless LAN devices
  • USB bus-powered devices

    Solution: When making a test submission package for devices that do not support WOL functionality, please include a readme file that refers to this issue, with the number of this release note.

    Program: Network Device

    10.12 - The NDIS test reports incorrect server back channel information.

    Program: Network, Modem

    Issue: The server-side devices (either the Ethernet back channel adapter or the support devices) do not accurately identify themselves to Test Manager on the server system.

    Solution:

    1. Quit Test Manager on the server system.
    2. Restart the server system.
    3. Restart Test Manager on the server system.
    4. start NDIS testing on the client system

    Program: Network device

    10.13 - The Remote Boot - LAN test should not fail if the test device does not support Remote Boot functionality

    Issue: When testing network devices, the Remote Boot - LAN test incorrectly appears in the list of available test in Test Manager. It is not a required test because, while remote boot functionality is required for systems submissions, it is not required for device submissions.

    However, if you allow the Remote Boot test to run on a network device, it returns a false failure even when it is specified that the test device does not support the remote boot functionality.

    Solution: When testing LAN network devices, remove the Remote Boot test from the list of tests in the Available Tests for Selected Test Category pane before beginning testing.

     

    Program: Network Device

    10.14 - Support devices missing from NDISTEST configuration screen when preparing to Run NDIS test.

    Issue: The NDIS test requires support devices for communication between the client (test) system and the server system. When configuring or reviewing support devices for either system in the NDISTEST screen, some or all of the available support devices may not display properly, preventing correct configuration of the NDIS test.

    Solution:Set the message device option to “No card”; then set the message device back to the previously chosen message device. If the available support devices do not display correctly, stop and restart the NDIS test.

     

    Program: Network Device

    10.15 - The ACPI Stress - Device I/O (Extended-NIC) test doesn't exit immediately when cancel test option is selected.

    Issue: If you quit the ACPI Stress - Device I/O (Extended-NIC) test before the test completes, there is an eight-minute delay before the test actually stops running.

    Solution: You must wait the full eight minutes for the test to quit. Closing the command window will not cause the test to stop running any sooner.

     

    Program: Network Device

    10.16 - Identical test devices recommended, but not required for NDIS test

    Issue: If the support device installed on the server isn’t identical to, or does not support the same functionality as the test device, the NDIS test may fail.

    An additional support device may be installed in the client system to verify multiple network device functionality. However, In this case, the support device installed across the PCI bridge must be identical to the test device.

    Solution: Use two test devices when testing multiple network device support. If a second test device is not used as the support device in the server system, ensure that the network device used for support card operation during testing provides identical functionality.

     

    Program: Network Device

    10.17 - NDIS test error messages hidden by other Test Manager windows.

    Issue: Error messages that display while the NDIS test is running may be hidden behind other Test Manager windows. Several NDIS error messages relate useful information, or require user interaction.

    Solution: Error message windows generated by the NDIS test appear in the taskbar . Check the taskbar while the test is running and respond to error messages that require user intervention.

     

    Program: Network Device

    10.18 - NDIS test Hibernation mode error message

    Issue: The NDIS test requires support for S1, S3, and S4 power states. If the test system does not support Hibernation mode, the following error message displays:

    Windows Script Host
---------------------------
Script: E:\Documents and Settings\Administrator\Desktop\4.02.0014\scripts\lan\2c_PMHibernate.wsf
Line: 0
Char: 1
Error: Cannot create object
Code: 80040066
Source: Windows Script Host

    Solution:

    If the test system supports all required power states

    Verify that Hibernation mode is turned on. The Hibernation mode may turn off automatically if the amount of free disk space is not equal to, or greater than, the amount of available system memory. If this occurs, free up additional hard disk space until the available disk space is greater than the amount of system memory. Alternately, you can retest on a different system with more hard drive space.

    If the S1, S3, and S4 power states are not supported on the test system

    Rerun the NDIS test on an ACPI-compliant system.

     

    Program: Network Device

    10.19 - NDIS test error if S3 power state is not supported

    Issue: When running the NDIS test on a test system does not support the S3 power state, the following error message displays:

    Windows Script Host
---------------------------
Script: E:\Documents and Settings\Administrator\Desktop\4.02.0014\scripts\lan\2c_PMStanby.wsf
Line: 0
Char: 1
Error: Cannot create object
Code: 80040066
Source: Windows Script Host
---------------------------

    Solution: If the dialog box displays, discontinue NDIS testing and retest on a system that supports S1, S3, and S4 power states.

     

    Program: Network Device

    10.20 - NDIS test error messages hidden by other Test Manager windows.

    Issue: Error messages that display while the NDIS test is running may be hidden behind other Test Manager windows. Several NDIS error messages relate useful information, or require user interaction.

    Solution: Error message windows generated by the NDIS test appear in the taskbar . Check the taskbar while the test is running and respond to error messages that require user intervention.

     

    Program: Network Device

    10.21 - NDIS test Hibernation mode error message

    Issue: The NDIS test requires support for S1, S3, and S4 power states. If the test system does not support Hibernation mode, the following error message displays:

    Windows Script Host
---------------------------
Script: E:\Documents and Settings\Administrator\Desktop\4.02.0014\scripts\lan\2c_PMHibernate.wsf
Line: 0
Char: 1
Error: Cannot create object
Code: 80040066
Source: Windows Script Host

    Solution: If the test system supports all required power states Verify that Hibernation mode is turned on. The Hibernation mode may turn off automatically if the amount of free disk space is not equal to, or greater than, the amount of available system memory. If this occurs, free up additional hard disk space until the available disk space is greater than the amount of system memory. Alternately, you can retest on a different system with more hard drive space. If the S1, S3, and S4 power states are not supported on the test system.
    Rerun the NDIS test on an ACPI-compliant system.

     

    Program: Network Device

    10.22 - Back Channel Ethernet adapters need to support PCI 2.2 standard

    
    

    Issue: If the Ethernet adapters used for back channel communication do not support the PCI 2.1 specification, NDIS test false failures may occur.

    Solution:Use only PCI 2.1 compliant Ethernet adapters for the NDIS test.

     

    Program: General, USB Controller, Network Device, System

    10.24 - USB test devices do not wake from sleep mode

    Issue: USB devices capable of generating a wake event, such as mice and keyboards, do not wake the system from sleep mode when running the following tests:

    • USB Device Wake Up test
    • LAN Device Wake Up test
    • [FoxFire] PCI 3.3 Volt Auxiliary Power Load test

    Solution: Enable the test device to remotely wake the system with the following procedure:

    1. From the Windows desktop, click Start, and then click Control Panel.
    2. In the Control Panel window, click Performance and Maintenance.
    3. In the Performance and Maintenance window, click System.
    4. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
    5. In the Device Manager window, select the test device you want to wake the system.
    6. On the Action menu, click Properties.
    7. In the Properties dialog box for the selected device, click the Power Management tab.
    8. Select the Allow this device to bring the computer out of standby check box, and click OK.
    9. Close all windows.
    10. Start Test Manager and run the test.

    Programs: Network

    10.23 - PCI 2.2 Compliance test false failures caused by additional, non PCI 2.2 compliant, network devices present during testing.

    Issue:

    When running the PCI 2.2 Compliance test for network devices, the test experiences false test failures if the test system includes other, non PCI 2.2 compliant, network devices. These test devices are required for additional HCT tests (the NDIS test for example).

    Solution:

    Insure that any additional network devices present in the test system support the PCI 2.2 standard before beginning HCT 10.0 testing.

    Programs: Network

    10.24 - NDIS test error if S3 power state is not supported.

    Issue:

    When running the NDIS test on a test system does not support the S3 power state, the following error message displays:

    Windows Script Host
---------------------------
Script: E:\Documents and Settings\Administrator\Desktop\4.02.0014\scripts\lan\2c_PMStanby.wsf
Line: 0
Char: 1
Error: Cannot create object
Code: 80040066
Source: Windows Script Host
---------------------------

    Solution:

    If the dialog box displays, discontinue NDIS testing and retest on a system that supports S1, S3, and S4 power states.

    Programs: Network

    10.25 - Server-side LAN Device Wake Up test not required for cable modems.

    Issue:

    The LAN Device Wake Up test requires communication with a remote test host (referred to as the server system). Although the server-side version of LAN Device Wake Up test is not required for cable modems, it appears in the Available Tests for Selected Test Category pane in Test Manager.

    Solution:

    Do not select the LAN Device Wake Up test from the Available Tests for Selected Test Category pane in Test Manager when testing cable modems. It is not a required test.

    Programs: Network

    10.26 - Driver Verifier test doesn't exit properly

    Issue:

    Driver Verifier performs a variety of device driver tests. One task for network devices is to examine both the checked and free versions of the NDIS.sys file. After testing the checked version of the NDIS.sys file the test issues a reboot command to the operating system. During the system shutdown a popup windows appears with the following message:

    This program is not responding.
To return to windows and check the status of the program, click cancel.
If you choose to end the program immediately, you will lose any unsaved data. To end the program
now, click End Now.

    Solution:

    Disregard the popup message, and allow the system to continue shutting down.

     

    Network Device Errata

    Programs: Network Device

    Errata ID: 398

    Test & Log: NDIS test and NDIS (low speed) test, NDIS.log (both)

    Title: NDIS and NDIS (low speed) test false failures

    Issue: The NDIS and NDIS (low speed) tests include validation of S1, S3, and S4 power states. These states are not supported on 64-bit systems; however, the test generates false test failures when testing these unsupported power states.

    Solution: This is an acceptable failure when related to the 2m_PMStandby, 2m_PMHibernate, 2m_WOLPattern, and 2m_WOLMagicPacket test cases. When creating a submission package, please include a readme.txt files with your submission that refers to this issue with this errata ID number.

    Program: Network Device

    Errata ID: 365

    Test & Log: NDIS test, NDIS.log

    Title: NDIS 2m_addre test fails when testing an intermediate driver

    Issue: When running the NDIS test on an intermediate driver, one script (2m_adder.wsf) returns a false failure.

    Solution: This is an acceptable failure. When making a test submission package with a failed log for this test, please include a readme.txt files with your submission that refers to this issue with this errata ID number.

    Program: Network Device

    Errata ID: 399

    Test & Log: ACPI Stress - Device I/O (Extended) test, Pmte.log

    Title: ACPI Stress - Device I/O (Extended) test fails on integrated network devices

    Issue: The ACPI Stress - Device I/O (Extended) test fails on network devices integrated onto mobile system motherboards . The failure is due to the conflict between the two power states that the mobile system may support (either S1 or S3, AND either S4 or S5) and the three power states that the ACPI test verifies (S1, S3, and S4). Because the mobile system supports fewer power states than the ACPI test verifies, the test fails and returns the following message in the log file:

    ERROR: Work item completed with Error Code: -1073721812
ERROR: The system does not support the S1 , S3 , and the S4 system power states required for device certification.
ERROR: PMTE_CheckForMustSupportedSleepStates(): System doesn't support sleep state S1

    Solution:

    To test network devices

    1. Run all network tests in the HCT, with the exception of the ACPI Stress - Device I/O (Extended - NIC) test.
    2. Return all test logs to one .cab file.
    3. Install the Mobile System HCT kit.
    4. Run the ACPI Stress - Device I/O (Extended) test from that kit.
    5. Return the single log to one .cab file.
    6. Include both .cab files with your submission.
    7. Please include a readme.txt files with your submission that refers to this issue with this errata ID number.

     

    11.0 - Storage Controllers and Devices

    

    All Storage Controllers and Devices Testing Issues

    Programs: All Storage

    11.1 - SDStress test error

    Issue: If run more than once in the same test pass, the SDStress test excludes a drive partition and records the following error in the test log:

      Drive_X: does not have enough free space. Ignoring.

    The SDStress test creates a folder named SDDATA in the root directory of each partition tested. When run on a test system configuration that includes an Iomega Zip 100 drive or an Imation SuperDisk 120MB drive, the SDStress test does not delete the SDDATA folders created during the test run. When the test is run a second time, it detects insufficient free disk space on the removable drive partition and excludes it.

    Solution: This error can be avoided in one of two ways:

    • Insert a blank disk into the removable media drive before each SDStress test run.
      
      - OR -
    • Delete all SDDATA folders before each SDStress test run.

     

    Programs: All Storage CD/DVD Drive, Recordable CD/DVD Drive Programs

    11.2 - CD-ROM drives detected as potential test devices during Recordable CD/DVD Drive test category installation

    Issue: The HCT installation program detects CD-ROM drives as potential test devices during Recordable CD/DVD Drive test category installation.

    Solution: When installing the Recordable CD/DVD Drive test category, select only drives that have recording capabilities, such as CD-R and CD-RW drives, as the test device.

     

    All 64-bit Storage Testing

    There are no testing issues for these programs.

    All 1394 Storage Programs

    There are no testing issues for these programs.

    All Storage Controller Programs

    There are no testing issues for these programs.

    All Storage Cluster Programs

    There are no testing issues for these programs.

    All Storage Hard Disk Drive Programs

    11.3 - ATA/ATAPI SMART disk test missing from ATA/ATAPI Hard Disk Drive test category

    Issue: The ATA/ATAPI SMART disk test is missing from the ATA/ATAPI Hard Disk Drive test category.

    Solution: The ATA/ATAPI SMART disk test is required for the ATA/ATAPI Hard Disk Drive test category. Install the ATA/ATAPI Hard Disk Drive test category and run all required tests. Then install the Other Storage test category and run the ATA/ATAPI SMART disk test. When testing completes, return all test logs.

    All Storage RAID Programs

    Programs: Storage RAID

    11.4 - RAID Data Integrity test creates large file on hard disk drive

    Issue: Running the RAID Data Integrity test creates a file, Bigraid.bin, on the test system hard disk drive. This file expands to consume all but 100 MB of space on the hard disk drive, and is not deleted after the RAID Data Integrity test is completed.

    Solution: After completing the RAID Data Integrity test, delete the Bigraid.bin file from the root directory of the C: drive.

    Programs: Storage RAID

    11.5 - RAID Data Integrity test creates large file on hard disk drive

    Issue: Running the RAID Data Integrity test creates a file, Bigraid.bin, on the test system hard disk drive. This file expands to consume all but 100 MB of space on the hard disk drive, and is not deleted after the RAID Data Integrity test is completed.

    Solution: After completing the RAID Data Integrity test, delete the Bigraid.bin file from the root directory of the C: drive.

    Program: RAID Controller

    11.6 - Updates to RAID controller test procedure documentation

    Issue: The RAID controller test procedure documentation for the Windows XP HCT 10.0 requires updates.

    Solution #1: Make the following additions and deletions to the RAID controller testing with Windows XP overview topic:

    Add to the manual tests requiring user intervention list-

    • Extensible Firmware Interface (for 64-bit systems only)

    Add to the automated test list-

    • FAT - File I/O

    Remove from automated test list-

    • Large Memory/PAE - Phase 1
    • Large Memory/PAE - Phase 2
    • Large Memory/PAE -System Reset
    • Public Import

     

    Solution #2: Make the following additions and deletions to the RAID controller basic functionality testing with Windows XP overview topic:

    Add to the manual tests requiring user intervention list-

    • Extensible Firmware Interface (Only for 64 bit systems)

    Remove from the manual tests list-

    • ACPI Stress - Device I/O (Disk Only)

    Add to the automated test list-

    • NTFS - File I/O
    • Driver Verifier - RAID Controller

     

    Solution #3: Make the following additions to the Running the RAID controller functionality automated tests with Windows XP topic:

    Add to the automated test list-

    • ACPI Stress - Device I/O (Disk Only) (For 64-bit systems only)
    • NTFS - File I/O

     

    Solution #4: Make the following additions and deletions to the Running the RAID controller functionality manual tests with Windows XP topic:

    Add to the manual test list-

    To run the Extensible Firmware Interface test (for 64- bit systems only)

    1. Start Test Manager.
    2. At the Test Manager window in the Available Tests for Selected Test Category pane, select Extensible Firmware Interface, and then click Add Selection.
    3. Click Start Tests.
    4. Follow the instructions displayed.
    5. When the test is completed, view test log files.
    6. Run all other required tests for this configuration.

    Remove from the manual test list-

    • ACPI Stress - Device I/O (Disk Only) (for 64-bit systems only)

     

    Programs: RAID Controller and RAID JBOD

    11.7 - Test name updates

    Issue: Several tests are listed incorrectly in the test procedure documentation for the Windows XP HCT 10.0.

    Solution: Use the following updated test name list as indicated for your program:

    • PCI Latency - RAID is renamed to Z[Run Last] PCI Latency - RAID Controller
    • PCI 2.2 Compliance is renamed to PCI 2.2 Compliance - RAID
    • ACPI Stress - Device I/O (Disk Only) is renamed to ACPI Stress - Device I/O (Extended)
    • ChkINF is renamed to ChkINF - SCSI Adapter
    • ChkINF is renamed to ChkINF - RAID

    Programs: RAID Controller and RAID JBOD

    11.8 - Only required tests are listed in Test Manager

    Issue: Some tests listed in the Windows XP HCT 10.0 test procedure documentation for RAID Controller and RAID JBOD devices may not be required tests for your test device. The Windows XP HCT 10.0 automatically determines which tests are required for your test device by detecting the hardware and software on your test system.

    Solution: Verify that all hardware devices are installed on the test system before installing and running the Windows XP HCT 10.0.

    Do not run tests listed in the test procedure documentation if they do not appear in the Available Tests for Selected Test Category pane of Test Manager. If tests are not listed in Test Manager, then they are not required for your test device.

    All Storage Removable Media Drive Programs

    There are no testing issues for these programs.

    All Storage Tape Drive Programs

    There are no testing issues for these programs.

    All USB Storage Programs

    There are no testing issues for these programs.

     

    Storage Controllers and Devices Errata

    There are no errata items for these programs. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

    12.0 - Streaming Media and Broadcast

    

    Streaming Media and Broadcast Testing Issues

    Programs: DVD Playback

    There are no testing issues for this program.

    Programs: DXVA Compliant DVD Playback

    There are no testing issues for this program.

    Programs: Video Input and Capture

    There are no testing issues for this program.

     

    Streaming Media and Broadcast Errata

    Program: DVD Playback

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: DXVA Compliant DVD Playback

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

    Program: Video Input and Capture

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

     

    13.0 - Systems

    

    Systems Testing Issues

    Programs: Audio and Systems

    13.1 - Wave Driver test intermittent failure

    Issue: When running the Wave Driver test, intermittent failures may occur with test case 16.9:12.

    Solution: This failure occurs due to timing issues on the test system. Re-run the Wave Driver test. Do not interact with the test system until the test completes. Focus on the test window must be maintained.

     

    Program: General, USB Controller, Network Device, System

    13.2 - USB test devices do not wake from sleep mode

    Issue: USB devices capable of generating a wake event, such as mice and keyboards, do not wake the system from sleep mode when running the following tests:

    • USB Device Wake Up test
    • LAN Device Wake Up test
    • [FoxFire] PCI 3.3 Volt Auxiliary Power Load test

    Solution: Enable the test device to remotely wake the system with the following procedure:

    1. From the Windows desktop, click Start, and then click Control Panel.
    2. In the Control Panel window, click Performance and Maintenance.
    3. In the Performance and Maintenance window, click System.
    4. In the System Properties dialog box, click the Hardware tab, and then click Device Manager.
    5. In the Device Manager window, select the test device you want to wake the system.
    6. On the Action menu, click Properties.
    7. In the Properties dialog box for the selected device, click the Power Management tab.
    8. Select the Allow this device to bring the computer out of standby check box, and click OK.
    9. Close all windows.
    10. Start Test Manager and run the test.

    Program: Systems

    13.3 - USB Device Framework test not required for systems

    Issue: The test procedure documentation erroneously lists the USB Device Framework test for the Systems test category in the Windows XP HCT 10.0.

    Solution: Do not run the USB Device Framework test if testing a system. The USB Device Framework test is not required for the Systems test category in the Windows XP HCT 10.0.

    Program: Desktop System, Mobile System

    13.4 - Systems must be tested with an audio device installed

    Issue: Desktop systems and mobile systems must be tested with an audio device installed prior to HCT installation. If Test Manager is installed on a test system that does not have an audio device installed, the Full Duplex test will access violate and fail, and then display a Full Duplex Test message box with the following text:

    Full Duplex Test has encountered a problem and needs to close. We are sorry for the inconvenience.

    Solution: You must un-install Test Manager and install an audio device in the test system in order to complete HCT testing.

    Program: Desktop System, Mobile System, Server

    13.5 - Several ACPI tests may cause an Access Violation if the test system does not support system states S1, S2, S3, and S4

    Issue: The following ACPI tests may cause an access violation (AV) if the test system does not support any system states (including S1, S2, S3 and S4):

    • ACPI Stress - Device I/O (Varied RTC)
    • ACPI Stress - Device I/O (Extended)
    • ACPI Verifier

    Solution: If the test system AV's while running the tests listed above then it is possible that none of the required system states are implemented in the test system BIOS. Ensure that the test system BIOS implements one or more of the required system states as described in the Windows Logo Program for Hardware Requirements version 2.0 (available from http://www.microsoft.com/hwdev/winlogo).

    Note: No system states are required for servers.

    Program: Desktop System, Mobile System, Server

    13.6 - ACPI Verifier fails if the OEMTableID field in the test system's ACPI BIOS is empty

    Issue: The ACPI Verifier test will cause an access violation (AV) when run on a test system using an ACPI BIOS with an empty OEMTableID field in the Fixed ACPI Description Table (FADT).

    Solution: Re-run the ACPI Verifier test with a kernel debugger attached to the test system. Use the "!fadt" debugger command to view the FADT and verify that the OEMTableID field is empty.

    To remedy this issue the ACPI BIOS must be updated. OEMs are required to supply a valid string in the OEMTableID field in the FADT ACPI table as required by the Advanced Configuration and Power Interface Specification version 2.0.

    Program: Mobile System

    13.7 - Int 13H extensions instructions for mobile systems that cannot boot from a USB floppy

    Issue: Mobile systems that use the same drive bay for both a swappable CD-ROM drive and a swappable floppy drive will fail the Int 13H extensions test because the HCT CD and boot floppy must both be available to the test system for the test to pass.

    Solution: One external USB floppy drive must be connected to the test system when Test Manager is installed to solve this issue. The steps taken to solve the issue depend on whether the test system can boot from a USB floppy drive:

    For systems that can boot from an external USB floppy drive

    • Insert one blank formatted floppy disk into the external USB floppy drive before running the Int 13h Extensions test.

    For systems that cannot boot from an external USB floppy drive

    1. Insert one blank formatted floppy disk into the external USB floppy drive before running the Int 13h Extensions test.
    2. Start Test Manager
    3. At the Test Manager window in the Available Tests for Selected Test Category pane, select Int 13H Extensions, and then click Add Selection.
    4. Click Start Tests.
    5. When the test system powers down, insert the swappable internal floppy disk drive back into the system, and insert the boot disk into this drive.
    6. Power on the test system.

       The test system will boot from the boot disk in the internal floppy disk drive and run the Int 13H Extensions test, and then the test system will power off.

    7. Remove the swappable internal floppy disk drive from the test system and replace it with the swappable CD-ROM drive, so that the configuration of the test system matches the original configuration when the test was started.
    8. Insert the boot disk into the external USB floppy drive.
    9. Power on the test system and start test manager.
    10. When the test is completed, view test log files.

    Program: "Supported" Client System

    13.8 - Illegal Imports test is not required

    Issue: The Illegal Imports test has been removed from the "Supported" Client System test category.

    Solution: Ignore the instructions to run the Illegal Imports test in the "Supported" Client System test procedures.

    Program: Desktop System, Mobile System

    13.9 - Voice modems may cause access violations when running the ACPI Stress - Device I/O (Varied RTC), ACPI Stress - Device I/O (Extended), ACPI Verifier and Driver Verifier tests if no audio device is installed

    Issue: Voice modems that are identified by the test system as the primary audio device may cause an access violation if no other audio device is installed.

    Solution: Install an audio device in the test system.

    Systems Errata

    Program: Desktop System

    Errata ID: 400

    Test & Log: Mixer Driver test; Mixdrv32.log

    Title: Mixer driver test fails on Japanese, Chinese and Korean versions of Windows XP

    Issue: The mixer driver test will fail test systems running the Japanese, Chinese and Korean versions of Windows XP. The following failure is reported in mixdrv32.log:

    MIXERCONTROLs returned using MIXER_GETLINECONTROLF_ONEBYID and _ALL flags don't compare

    Solution: This is an acceptable failure for test systems running the Japanese, Chinese and Korean versions of Windows XP. Note that you encountered this issue when making your submission.

    Program: Desktop System, Mobile System, Server

    Errata ID: 401

    Test & Log: ACPI Stress - Device I/O; Pmte.log

    Title: The ACPI Stress - Device I/O test fails on test systems that include PS2 ports but ship with a USB keyboard and mouse

    Issue: The ACPI Stress - Device I/O (extended) and ACPI Stress - Device I/O (varied RTC) tests will fail if the test system includes PS2 ports but ships with USB keyboard and mouse. The ACPI Stress - Device I/O test will fail when it examines the PS2 port and is unable to find a device connected to it. The following failure will appear in Pmte.log:

    Prob=CM_PROB_DEVICE_NOT_THERE
DevDesc=Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Test Interface=(null)
PnP Interface=?ACPI#PNP0303#4&37307686&0#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
Skipping device because it has a problem Prop=CM_PROB_DEVICE_NOT_THERE

    Solution: This is an acceptable failure if the test system does not have devices connected to the PS2 port(s).

     

     

    14.0 - Unclassified

    

    Unclassified Testing Issues

    Programs: Universal

    There are no testing issues for this program.

    Program: UPS

    14.1 - Serial PnP Compliance test not required

    Issue: The Serial PnP Compliance test is not required for the UPS test category.

    Solution: Do not run the Serial PnP Compliance test for UPS devices with the Windows XP HCT 10.0.

    Unclassified Errata

    Program: Universal

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.

     

    Note: The program category previously known as Miscellaneous has been renamed to Universal.

    Contact WHQL Miscellaneous Device Test support at mischelp@microsoft.com for detailed information on testing your Universal product using the Windows XP HCT 10.0 Release Candidate.

    Program: UPS

    There are no errata items for this program. For additional program-specific information, see the Windows Hardware Quality Labs Device Home Page.