WHQL Update Conference May 1999

WHQL Update Conference May 1999

WHQL Update Conference Agenda
Welcome WHQL Overview and Status Submission Process Non Self-Test Issues Self-Sign Program System Test Implementers Forum Device and Component Updates Lunch Cluster Issues Driver Testing & Debugging ACPI System Testing Hands-on Demo Q & A

WHQL Overview and Status Brad Carpenter Group Manager WHQL Windows Operating Systems Division Microsoft Corporation

WHQL Overview and Status Agenda
WHQL Mission Statement What We Don’t Do WHQL Process Submission Status Self-Test Status WHQL & the Internet Test Kits Design Guide Transition Call To Action

WHQL Mission Statement
Ensure that hardware is functional across the Windows family of Operating Systems by providing an efficient and responsive validation process

WHQL Mission Statement Hardware functionality
Ensure that hardware is functional across the Windows family of Operating Systems… Increases end-user satisfaction Reduces support costs Reduces Total Cost of Ownership Accelerates quality of new hardware

WHQL Mission Statement Process
…By providing an efficient and responsive validation process WHQL’s primary objectives are Provide validation against Windows Logo program requirements Provide up-to-date Hardware Compatibility List Provide Digitally Signed Drivers Work with our customers

WHQL Mission Statement Customer relationships
Working with our customers is key We are listening to your feedback on how to improve the WHQL processes WHQL survey handed out

What We Don’t Do… Common Misperceptions
Write or change the Systems Design Guide Make marketing decisions Write all the tests Incorporate passing drivers into OS Implement features in the OS Manage the IHV’s or OEM’s

WHQL Process End to End

Submission Status Total Submissions
On track for 52,000 submissions in ‘99 24,000 in 1998 8000 in 1997 2200 in 1996 Areas of largest growth in 1998 USB Cluster Imaging Motion Video

Self Test Status Total Self-test programs
Self-test means Download and run tests Send in logs & in some cases hardware Logs evaluated for pass/fail Audit may occur 64 total test programs Currently 27 are self-test Key device programs that have gone self-test in recent months: 1394, Audio, Display, Systems, Hard Drive, Keyboard, Imaging, Mouse, Net Adapter, Printing, USB

Self Test Status Program projections
Projected dates for next milestones Analog, ISDN Modem – 6/1/99 Dual Processor – 6/1/99 Motion Video – 6/1/99 IDE CD-ROM – 7/1/99 Multiprocessor – 9/1/99 SCSI CD-ROM – 11/1/99

Self Test Status Testing turnaround times
Goal '98 '99 Self Test Systems 7 36 13 Non-Self Test Systems 30 52 16 Self Test Devices 7 10 10 Non-Self Test Devices 30 35 23

Self Test Status System Submissions
Past 6 months % Complete in # of days Volume 7 10 14 21 30 Desktop 2793 44 19 Mobile 667 45 13 Reference 131 48 8 12 Server 38 62 16 3 1

WHQL & the Internet Short Term
Improve content and synchronize content with other groups Make information easier to find Redesign HCL for increased reliability (6/1/99) Personalized Web page - “My WHQL” (6/1/99) “Status Tickers” (6/1/99) Better & more secure tracking of submission ID’s Testing turnaround times for programs

WHQL & the Internet Long Term
Online submissions from Web page Generate real-time Master ID Electronically sign documents Uploading of logs with backend process validating Hardware sent in parallel to submission Streamlines administrative process Projected completion Q1 2000

Test Kits Feedback Feedback from customers on kits
More predictable Less frequent Better documented Future test kit releases driven by Major OS releases and SP updates New Design Guides New Technologies Clarifying what kits are testing for

Test Kits Upcoming Release
Updated test kits release on 6/1/99 HCT CD STIF ACPI & PCI tests 48 hour stress CD Updated disabler PnP tests LOGO’d components for refresh scenarios Display CD (DCT) Additional D3D tests 35+ Device Test Kits Driver Verifier added

Test Kits Upcoming Release
Enables testing submissions on Windows 2000 Beta3 (RTM 4/29/99) Passing submission with new test kit receives COMPAT designation Windows 98 Second Edition (RTM 5/5/99) Starting 7/1/99 Win9x submissions tested against Win98SE Windows NT® 4.0 SP5 PC99

Design Guide Transition Current
New PC 99 Design Guide goes into effect July 1, 1999 Initial release of PC 99 test kits by June 1 Same Grace periods as last year for components within systems Until Sept 1 ‘99 systems can contain PC 98 components Will get PC 98 designation As of July 1 all new submissions shall meet PC 99 requirements June 30, 1999 is last day for new PC 98 submissions

Design Guide Transition Future
PC 99a Addendum by June 1, 1999 FAQ update only No new requirements PC 2001 will be released Feb 2000 PC 2001 goes into effect July 1st 2001 PC 2001 preview released this month PC 99 and Addenda in effect until June 30th 2001

Design Guide Transition Servers
Hardware Design Guide for Microsoft Windows NT Server 2.0 (SDG 2.0) goes into effect July 1, 1999 SDG 2.0 systems can contain any combination of the following devices SDG 2.0 PC 99 SDG 1.0 PC 98

WHQL Status Call To Action
Give us your feedback! Fill out survey please Visit WHQL web page Prepare for Design Guide transition

WHQL Status Questions

Submission Process Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

Submission Process Agenda
Submission Process Flow Non Self-Test vs Self-Test General Submission Requirements System Submission Assistant System Submission Notes Device Submission Notes Call To Action

Submission Process Flow End to End

Non Self-Test vs. Self-Test Comparision
Who runs Tests You You and WHQL How long does submission take Up to 7 days Up to 30 days Fees $500 (even if multi-function device) $1000(even if multi-function device)

General Submission Requirements What to submit
Complete set of Test Logs Win95, Win98, Win NT 4.0, and Win2000 Use Submission Assistant for systems Completed Agreements & Exhibits Payment for testing Hardware for Non Self-Test Systems

General Submission Requirements WHQL Testing Agreement and Exhibit A
One Fully Executed WHQL Testing Agreement per Company Exhibit A of the Testing Agreement Company should execute Exhibit A downloaded with every Test Kit to amend Testing Agreement to include each specific product

General Submission Requirements Logo License Agreement and Exhibit B
One Fully Executed Logo License Agreement per Company Exhibit B WHQL generates Exhibit B to include products eligible to use the logo Company should execute Exhibit B and return to WHQL

General Submission Requirements Payment
Open Purchase Order Send Original which WHQL keeps on file Easiest form of payment as WHQL Automatically deducts processing fee as submissions received Regular Purchase Order Payable to Windows Hardware Quality Labs WHQL will invoice you for total dollar amount Check Send Original Wire Transfer Send copy of bank’s confirmation to WHQL with submission

General Submission Requirements Shipping Hardware
If you are shipping hardware Ship to correct address and building location If shipping to the United States, use correct: Product Classification Product Valuation Country of Origin Keep good records Write SELF TEST on box if Self-test submission Attach shipping invoice on outside of box

General Submission Requirements Receipt
Upon Receipt of a Submission WHQL sends confirmation within 3 working days will include status Does not include shipping time or customs If you do not receive confirmation within 3 working days, send to with keyword STATUS

General Submission Requirements Status
Turn Around Time from date of complete submission Seven (7) days for Self-Test reports Thirty (30) days for Non Self-Test reports For submission status go to Enter in submission ID “Status Tickers” (6/1/99) Better, more secure tracking of submission ID’s Testing turnaround times for programs

Submission Status Page

General Submission Requirements How to get help for Systems
Systems Technical Questions Send request to If no response in 7 days resend with HELP in subject line Testing Errata, announcements,test descriptions Submission Status Send request to with STATUS REQUEST in subject line

General Submission Requirements How to get help for Devices
For Technical Questions Find list of aliases & FAQs at WHQL Test Kits page List of key device aliases Audio Display (incl. monitors and display adapters) Input Modem - Motion Video (e.g., DVD and Video capture/playback) Network (ATM, LAN, Self-Test, WAN) Printers - Storage devices (incl. Hard disk drives, CD-ROM, DVD-ROM) USB devices and hubs

General Submission Requirements HOLD
Submission Status - HOLD Reasons for HOLD status Missing WHQL Testing Agreement or Exhibit A Missing ANY test logs Missing hardware and/or device drivers for Non Self-Test submissions Not entered into Testing Queue until items received

General Submission Requirements INCOMPLETE
Submission Status - INCOMPLETE Reasons for INCOMPLETE status Missing payment Missing Logo License Agreement Enters Testing Queue but no Test Report and not on HCL until items received

General Submission Requirements Testing Complete
Passing: Test Report Logo Artwork Signed driver and .CAT files Device is listed on Hardware Compatibility List (HCL) Failing:

Hardware Compatibility List

System Submission Assistant

System Submission Process System Refresh Rules
Refresh allows OEMs to upgrade items on a system that was logo’d using the previous design guide, such as CPU speed. PC 97 refreshes end on July 1st 1999. PC 98 refreshes: Begin July 1st End July 1st 2001. Servers are allowed to refresh for two design guides. SDG 1.0 refreshes will last thru SDG 3.0

To qualify for a refresh the system must observe the following rules: HCT Kit – must always use a current HCT kit release. PC97 refreshes must be made with HCT kit versions 8.0, 8.1, or 8.2 Failures due to new test coverage will be listed as warnings in the test report. BIOS Minor BIOS changes, such as timing issues, are allowed BIOS changes that alter fundamental ACPI, Plug and Play, or power management functionality requires a complete retest under the current guidelines

System Submission Process System Refresh rules
System Refresh Rules (cont’d): CPU upgrades New CPUs must be pin compatible with the original Architecture and/or CPU manufacturer changes will require a complete test-run under the current guidelines. Component changes Add-in components: New logo’d Add-in components are allowed without retesting Onboard components: New component must pass WHQL testing and meet the current specification at the time of the system refresh New components must be from the same manufacturer and must be pin-compatible with the original component

System Refresh Rules (cont’d): For Mobile systems only: TFT display size changes on mobile systems are allowed New docking stations for mobiles must meet the current specification at the time of the refresh

System Submission Notes Adding Marketing/Model Names
When sending in a submission Can be added on the original submission using Submission Assistant After System passes testing Send request via to Must be from approved contact name Must reference original ID# Only lower processing speeds can be added as marketing names

Device Submission Notes Info on Web
Device Kits and FAQ’s downloadable off WHQL web site For help check program FAQ and/or program alias

Device Test Kits & FAQs

Submission Process Call To Action
For fastest results, ensure your initial submissions contain Complete set of correct drivers and test logs for all operating systems Completed Submission Paperwork Payment Hardware for non self-test systems Use System Submission Assistant Track status from website

Submission Process Questions

Non Self-Test Issues Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

Non Self-Test Issues Agenda
Pre-Test Preparation HW Requirements for Non Self-Test Operating Systems Tested MS System Configuration Testing Non Self-Test Issues Self-Test Issues System Description Form Call To Action

Pre-Test Preparation Specifications
System documentation PCI 2.1, 2.2 specification Hardware design guides PC 9x Server PnP BIOS specification APM 1.2 specification ACPI specification

Pre-Test Preparation Errata
Testing errata Hardware design guide FAQ’s ATAPI specification Serial loopback plug Need this specific piece of hardware NT comm port tests

Pre-Test Preparation Devices for test
Devices need for enumeration tests USB PCI ISA Com port Printer port

What Qualifies As a Non Self-Test Submission
Systems using non self-test processor For most current list Systems with multiple processors Systems with custom HAL Currently implementing HAL Test Kit Available for RTM of Windows 2000

HW Requirements for Non Self-Test Systems (1 of 2)
Server Class system Max memory motherboard can support Boot devices drivers must be on floppies Drivers should be ready to install Storage (RAM x 3) + 2 GB for crashdump tests Two LOGO’d PCI net cards Raid controller If offered by OEM

HW Requirements for Non Self-Test Systems (2 of 2)
Workstation and Basic/Mobile Class Two LOGO’d PCI net cards (non-mobile) 8GB minimum hard drive 4GB minimum for mobile class 64MB memory per processor for Workstation 32MB memory for Basic/Mobile

Operating Systems Tested
Server Class NT 4.0 SP4 Windows 2000 ACPI mode Workstation Class Windows 9x – if supported by OEM Basic/Mobile Windows 98 APM & ACPI mode Windows 95 – if supported by OEM

MS System Configuration Testing Machine Config
Three partitions Boot partition Fat 16 – 2GB minimum NTFS Compressed NTFS Two PCI Net cards Raid configuration for servers MS-DOS/LANMan Only used for lab convenience

MS System Configuration Testing BIOS Settings
BIOS settings that MS may change PnP OS setting NT 4.0 = No Windows 2000 = Yes Win9x = Yes Parallel port set to ECP Serial and Parallel ports set to Auto NT 4.0 sometimes needs these set manually IRQ sharing = Yes

Non Self-Test Issues Systems
System arrives and doesn’t boot Loose components Missing CPU’s Missing HD’s or no HD’s SCSI HD’s set to same ID number Power supply not plugged into MB BIOS password Bad system

Non Self-Test Issues Drivers
Missing drivers Drivers that don’t install Pre-Test the floppy’s / CD’s submitted Un-LOGO’d driver Incomplete driver set Wrong drivers system components

Non Self-Test Issues Firmware / Device
Wrong BIOS version Wrong firmware on controller Missing internal cables Devices present but no cables Wrong speed processor(s) installed

Self-Test Issues Common Mistakes
Testing non-English version of OS Un-readable floppy Always keep a back up No readme.txt file included to explain test failures Must contain test failure explanations Must have Master IDs for components that show as un-LOGO’d in your LOGO’d components test log Failure to run all required tests

System Description Form Project Goals
OEMs describe submitted system Today testers determine contents Process is time consuming OEMs can streamline this process by describing submitted system

System Description Form Details
Accomplished using System Description Form Available soon on OEMs fill in the form and include printed copies with submission Form will initially be optional Date of being a requirement TBD

System Description Form

Non Self-Test Issues Call To Action
Read pre-test documentation Understand hardware requirements for non self-test submissions Make sure submission paperwork, hardware, and drivers complete Leads to shortened test time!! Look for the System Description form on web page soon

Non Self-Test Issues Questions

Self-Sign Program Brad Carpenter Group Manager WHQL Windows Operating Systems Division Microsoft Corporation

Self-Sign Program Agenda
Digital Signature Purpose Windows 2000 Implementation Self-Signing Overview What Can Be Signed Prerequisites Auditing Call To Action

Self-Sign Program Digital signatures purpose
Promote and advance driver quality Improve end-user experience Reduce support costs Reduce Total Cost of Ownership

Self-Sign Program Windows 2000 Implementation
All files verified during setup During device install policy determines warning level Policy Options 0 = IGNORE; all files are installed 1 = WARN; user warned unsigned driver is about to be installed; default policy for Beta3 and RTM 2 = BLOCK; user blocked from installing unsigned driver

Self-Sign Program Windows 2000 implementation
“Warn” set for the following classes: Display Adapter Hard Drive Controller Keyboard HID Modem Monitor Mouse Net Adapter Multiport Serial Adpt Multimedia Audio DVD Video Capture Gameport Printer SCSI Adapter Smart Card Reader

How Verification Works
The File Signature Verification utility is used to detect non-Microsoft signed files. This utility can be accessed via the Start menu, Run, Sigverif or through the MMC under System Information.

By default this tool will scan “Core System Files”, all driver files installed in Device Manager, and all printer drivers installed.

By selecting the “Advanced” tab from the Sigverif menu, and then choosing “View Log”, the user is able to verify the actual Signer of the File.

Self-Sign Program Overview
Signed driver does NOT mean the driver has been LOGO’d WHQL Signature Passed Windows Logo requirement tests Listed on the Hardware Compatibility List OEM/IHV Signature Implies driver has met Logo criteria Driver may or may not be in the WHQL submission process

Self-Sign Program Implementing digital signature
Smart Card required to digitally sign WHQL will provide necessary tools and documentation Smart Card will contain signature Smart Card will be valid for 90 days WHQL auditing program will evaluate vendor for Smart Card renewal

Self-Sign Program What can be signed
Drivers can be self-signed without re-submission for .TXT, .HLP, and minor .INF file changes Can not add features How to get new features signed Driver is in WHQL submission process WHQL will sign passing drivers WHQL signed driver must be made public within 30 days of receipt

Self-Sign Program Reporting
Qualified vendor will submit report Device name, manufacturer, marketing name, Master ID of parent device, signing company, date signed, pre-test confirmation, signed driver file set including .CAT file, and test kit used Reporting will be done online Reporting required twice a month

Self-Sign Program Prerequisites
First version of hardware/driver must be in WHQL process Company has track record with WHQL Submissions within previous 90 days must be greater than 90% pass rate Complete submission paperwork

Self-Sign Program Prerequisites
Qualified vendor must provide Staffed testing facility running logo tests Secured location for signing server Company vault, locked room Detailed support information Signed legal documentation Qualified vendor signing drivers are responsible for quality An OEM may sign an IHV driver, but is accountable for meeting Logo criteria

Self-Sign Program Auditing
All OEM/IHV signed drivers must meet Windows Logo requirements 100% of signed drivers may be audited Device/Driver audited will be tested against criteria at time it was signed If hardware not present at WHQL, vendor must provide necessary hardware within 10 days

Self-Sign Program Renewal and revocation
Submissions within previous 90 days must be greater than 90% pass rate All audits of device/driver set pass New smart cards sent 30 days prior to expiration Revocation If device/driver fails to meet renewal criteria self-sign abilities will not be renewed

Self-Sign Program Call To Action
Raise the quality of your submissions to qualify for self-sign program Understand Win2000 Implementation More info on WHQL Self-Sign program More info on Digital Signature -

Self-Sign Program Questions

System Test Implementers Forum
Brad Carpenter Group Manager WHQL Windows Operating System Division Microsoft Corporation

System Test Implementers Forum Agenda
Compliance Overview System Test-IF Update PC 99 Test Walk-through Intel-WHQL Test Framework Current Tests Summary / Call to Action

Designing-In Compliance
Intel and Microsoft recognize that consistent, objective PCxx compliance test tools are needed earlier in the design process in order to Design-In compliance and reduce product cycle time

Current Challenges Meeting the PC xx baseline is difficult...
Design Guide features not always testable Design Guide may lack clear Pass / Fail criteria Test development lags Design Guide release Test and Design Guide interpretations may vary Hard to map test results back to Design Guide

Designing-In Compliance
WHQL Hardware Tests S/W Test Spec H/W PASS FAIL System Design Guide and Test Specifications co-authored by Microsoft and Intel

PC xx Test Specifications
H/W spec co-authored by Intel & MSFT S/W spec by Microsoft Defines objective Design Guide test criteria Declared set of test criteria, or assertions Specifies testable sub-set of assertions Maps to applicable Design Guide features, industry standards, specs, and tools Available earlier in the design cycle Industry Feedback Provided via System Test-IF

Reliable Indicator of Design Guide H/W Compliance
Early PC xx H/W Tests System Test-IF Alpha & Beta releases Developed and supported by Intel Use for early design evaluation & debug Windows® -hosted, similar look/feel to other Intel & Microsoft tests Tests can be run by developer or third party test houses Final test kits from Microsoft WHQL Includes applicable Intel-developed H/W tests Reliable Indicator of Design Guide H/W Compliance

System Test-IF Coverage
Applications Designed For Windows® Logo Operating Systems PCxx SDG Drivers Hardware System Test-IF H/W Test Spec & Test Focus

System Test-IF Coverage
100% PC 99 PC 2001 PC Card AGP Image ATA USB Mobile Audio Video 3D PCI ACPI Goal: 100% H/W Test Coverage for PC 2001

System Test-IF Profile
Open to all interested developers Co-sponsored by Microsoft and Intel Can participate as a member or non-member Membership provides several benefits... Web site at Discussion areas for Test Spec & test feedback Alpha H/W test downloads System Test IF-posted responses to issues Member contact database Free company pass to Test Spec Reviews Invitation to ‘members-only’ events

System Test-IF Members
3Dlabs, Inc. Adaptec, Inc. ATI Technologies, Inc. ASUSTeK Computer, Inc. Compaq Computer Corp. Conexant Systems, Inc. Creative Labs, Inc. Cyrix Corporation Dell Computer Elonex PLC Fujitsu, Ltd. Gateway 2000, Inc. IBM Corporation Matrox Graphics, Inc. Micro Design Resources Micron Semiconductor Mitsubishi Electric NEC Computer Systems NeoMagic Corporation nVidia Corporation Philips Components Phoenix Technologies, Ltd. S3, Inc. Silicon Motion, Inc. Sonnetech, Ltd. Toshiba Corporation Trident Microsystems, Inc. Videologic, Ltd. Viewsonic Corporation Xircom Current Membership: 30 and Growing!

Futures Planning Session June 24-25, San Diego
Agenda: Review draft 0.3 PC 99a H/W Test Spec Targeted coverage: Mobile, USB, AGP, Digital Imaging, Speech Recognition, ATA-66 Future Tools & Test Spec discussion PC 99(a) H/W Test Workshop WHQL Test Kit Workshop Open to All System Test-IF Members

Test Framework H/W tests integrated in Intel Test Harness
PC 99 H/W tests include ACPI, PCI, 3D, & Video Tests are modular and can be run individually Test Harness runs in WHQL Test Manager Clear test assertion PASS / FAIL output Common NTLog reporting format Test failures map directly to H/W Test Spec

WHQL Test Kit Integration
WHQL Test Manager WHQL Test Manager invokes Intel tests Intel tests output NTLog format - same as WHQL tests Intel tests run stand-alone or within Intel test harness

Clear, Objective Indication of Compliance
Test Output Features Log file created with Pass / Fail status Failures are tagged within log file – Failure, – Warning, and – Info tags “Failure explanation” may be appended Output maps to Test Spec assertions Also, lists applicable Design Guide sections Optional verbose debug output Clear, Objective Indication of Compliance

Assertion Keys Map to X-refs in Test Spec
Assertion Mapping Assertion Keys Map to X-refs in Test Spec

Current Tests ACPI Tests
Battery and AC Adapter Processor Power State Transition Docking and Undock Power Management Power Management Timer Thermal Management Processor Throttling Table and Name Space Embedded Controller Global Lock Interrupt 15 Insert/Eject Media Legacy/ACPI State Transition Interrupt Routing Table Lid Switch Multi-processor Table Power & Sleep Buttons Resource Configuration Real-Time Clock Sleep Wake Control

Current Tests PCI Tests
Power Management Register Interface Sub-system and Vendor ID Maximum Completion Time Power Management Voltage Requirements Auxiliary Power PME Signal Routing PME Sleep/Wake State Transitions System BIOS Initialization PCI Test Card required for highlighted tests

PCI Test Card - Required
NEW FoxFire II Adapter Card Monitoring write-latency Monitoring Target Ready (TRDY) latency BIOS allocates resources Power Management Compliance Required now for the following Reference Systems (HCT) Display Adapter (DCT)

System Test Implementers Forum Summary
Microsoft & Intel are working to deliver consistent H/W Test Specs and tests System Test-IF is off to a great start! Critical mass reached w/ OEMs & IHVs We are receiving great industry feedback H/W tests map directly to assertions WHQL Beta test kit available 5/99 Includes applicable System Test-IF PC 99 H/W tests

System Test Implementers Forum Call to Action
Become a System Test-IF member today! Plan to join us in San Diego on June 24-25 Run the Beta H/W tests on your products Review the draft 0.7 PC 99 H/W Test Spec Draft 0.9 available on Web in early May‘99 30-day review for industry comments Send us your feedback: System Test-IF Momentum is Growing!

System Test Implementers Forum Questions

Device & Component Updates Brad Carpenter Group Manager WHQL Windows Operating Systems Division Microsoft Corporation

Device & Component Updates Agenda
MiniPCI Program On-Board Components AC97 and AMR Devices SSID/SSVID Reference Designs Call To Action

MiniPCI Program Overview
Goal is to test MiniPCI devices independent of systems MiniPCI specification not yet ratified Industry needs to first prove interoperability of MiniPCI devices and systems from multiple vendors Three phases testing plan for MiniPCI

MiniPCI Program Phase 1 and 2
Phase 1 - Now MiniPCI devices treated as motherboard devices WHQL will optimize # of systems for test Phase 2- Ratified Spec, Interop Proven WHQL will test MiniPCI devices with 3 “reference” laptop systems All MiniPCI devices shall pass testing in “reference” laptop systems MiniPCI devices will be tested independent of system

MiniPCI Program Phase 3 Phase 3 - After Desktop BIOS and chipsets exhibit same behavior as Reference Laptops (TBD) Reference desktop system w/ a special PCI add-in card to test Mini PCI devices Mini PCI device attaches to special PCI card IHVs will only need to submit the Mini PCI device along with the appropriate drivers For more info see WHQL Modem and Network FAQ's at

On-Board Components Streamlining Validation of Motherboard Components
Key device categories can be tested by vendors through WHQL self-test programs Audio, Display, Input, LAN, etc New “batch” submission process for multiple self-test program devices One fee Two systems Can split up submissions of On-Board Components into batches Don’t have to wait for last component to be ready to submit all at once

On-Board Components Examples for IHV’s process
IHV may work with OEM to implement device on MB then submit to WHQL Receive Logo and drivers are signed OEM may coordinate efforts of several IHV’s One submission for multiple devices at one fee Two systems for all self-test devices submitted Logo’s and signed drivers for all

On-Board Components Examples for OEM’s process
OEM may submit integrated devices or have IHV’s submit for them OEM may wait until several devices are ready then submit a “batch” for the reduced fee and two test system method Self-test makes this possible with reduced turnaround of Logo’s and signed drivers With self-test you know when you will pass WHQL auditing will occur out of your cycle

On-Board Components Example of reduced costs
System has integrated audio, display, input and LAN Before self-test this would involve four $1500, at least two test systems for each device, and take 30 days Total cost = $6000 and 8 systems and 30 days With self-test these can be combined into one $500 and two test systems with at target turnaround of 7 days Total cost = $500 and two test systems, 7 days Expensive pre-production systems may be used, as long as the drivers and firmware are final, and will be exchanged for final product

On-Board Components Validation of Components on Pre-production Motherboards
If device needs to be submitted for logo test before final hardware is available: Firmware and driver must be final shipping version Only cosmetic changes are allowed without re-testing Cover letter stating Changes to be made before ship When final production hardware will arrive at WHQL Final shipping versions must be supplied to WHQL by an agreed upon date WHQL will return pre-production system upon agreement of delivery of production systems.

AC97 and AMR Devices Current Status
AMR cards extend motherboard chipset which has a PCI bus ID BIOS must provide unique PCI Subsystem Vendor ID based on the AC 97 codec mfg ID The codec must implement the codec ID BIOS must provide unique PCI Subsystem Device ID assigned by codec mfg based on some additional means E.g. strap unused codec GPIO pins. Standard must be defined for AMR card identification

AC97 and AMR Devices WHQL Testing
Devices on motherboard tested as motherboard devices Proposal for testing devices on Riser card (MR, AMR) will be posted on WHQL web We are currently evaluating best way to test these cards Want to gather feedback before making final decision

SSID & SSVID Registers used to uniquely ID add-in board or sub-system where PCI device is located Required by PCI 2.1 WHQL checks for valid non-zero values Audio example: Submit one large inf with all entries Each additional entry only need to submit inf

Reference Designs WHQL investigating changing Ref Design program
WHQL proposed ideas but feedback ‘no’ Reference Design problem Ref Design is not a final product yet receives LOGO Ref Design implemented on motherboard exposes problems not caught before Need to find way to eliminate problems between ref design and motherboard implementation

Device & Component Updates Call To Action
MiniPCI vendors prepare for 3 phase testing plan For more info see WHQL Modem and Network FAQ's at Take advantage of OnBoard components changes Prepare for AC97 and AMR

Device & Component Updates Questions

Cluster Testing Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

Cluster Testing Agenda
Cluster HCL for RAID Systems Cluster HCL for Components Cluster Test Environment Equipment Guidelines Setup Guidelines Troubleshooting Cluster Status for Systems How to Get Cluster Help Call To Action

Cluster HCL for RAID Systems
1 2 3 4 5 Your Product in search of HCL listing What Category am I? Logo’d Product listed on the HCL IHV tested? IHV Submitted ? With Hardware? OEM tested? OEM submitted? With Hardware? RAID RAID Yes Yes ID string in firmware or bios Yes Yes ID string in firmware or bios Yes Yes RAID RAID Yes Yes This slide ID string in separate NVRAM Yes Yes ID string in separate NVRAM Yes No JBOD Yes Yes JBOD Yes Yes No ID string Yes No No ID string

Cluster HCL for Components
Windows Hardware Compatibility List (HCL) 1 2 3 4 Cluster Qualification General Storage Qualification Your Product in search of HCL listing PC98 SCSI, SSA, or Fibre Channel RAID System Cluster Component Qualification Cluster Server System Configuration PC98 SCSI, SSA, or Fibre Channel RAID Controller Includes RAID Systems, RAID Controllers, & all HBAs. PC98 SCSI, SSA, or Fibre Channel HBA Just a Bunch Of Disks (JBOD) Logo’d SCSI, SSA, or Fibre Channel RAID Device (JBOD) No Cluster Component Qualification Required

Cluster Status for Systems
Devices require two separate qualifications First SDG 1.0 or PC98 qualification Second Cluster component qualification Servers must be LOGO’d SDG1.0 Use the most current HCT CD Down load cluster submission assistant Make cluster self-test submission As of 6/29/99 new submission shall pass Win2000 OS Requirements NT4 = Enterprise Server Win2000 = Advanced Server or Data Center

Cluster Component Test Standalone
Primary Domain Controller, Also used as Client Node in Basic test Environment Must be configured for TCP/IP, DHCP service is optional , any client(s) on this network may be chosen as “Client” for the Validate2Node test Network Hub for Private interconnect (heartbeat) Client Network Hub Shared Storage Device (RAID System) Do not Terminate BUS at RAID System Shared SCSI BUS, use a hub for Fibre Channel connections Terminate BUS externally at each Node using “Y” connector Cluster Node A Cluster Node B

Cluster Component Test Existing Network
Existing TCP/IP based Network, any client(s) on this network may be chosen as “Client” for the Validate2Node test Network Hub for Private interconnect (heartbeat) Client Network Hub Shared Storage Device (RAID System) Do not Terminate BUS at RAID System Shared SCSI BUS, use a hub for Fibre Channel connections Terminate BUS externally at each Node using “Y” connector Cluster Node A Cluster Node B

Equipment guidelines Use LOGO’d systems
300Mhz or better (X86 or Alpha) Minimum 392MB RAM Needed for special pool testing Use only LOGO’d add-in components Both Net Cards need LOGO

Equipment guidelines Connection components
Short “Y” connector at SCSI HBA for proper external termination Don’t rely on onboard HBA termination Bus will not be correctly terminated after failover event Disk ownership will not transfer Test cables before use!

Setup Guidelines Clean installation not necessary for each cluster component test pass When testing Components Swap in only test component Use known ‘good’ cables, terminators, HBAs, etc. Use the fastest, newest test machines available WHQL uses mix of dual & quad processor PII-400 or better

Setup Guidelines NT4 Enterprise or Win2000 AS / DC
Installing cluster service Log on as admin w/ account on both nodes of cluster Both nodes must be in the same domain Cluster IP must be static IP Have shared disks connected and terminated properly Both nodes should see the shared disks before installing cluster services

Troubleshooting Check cables and termination first!
Make sure SCSI HBAs in each node have different SCSI ID’s since they are on same shared bus Heartbeat net cable connected to proper net card Make sure that the “clusterlog” system variable is set/points to existing directory on both nodes Resulting log file contains step by step record of every cluster operation on node Log file is critical for software level debugging Tests must be completed in sequence If phase 1 fails then crash2 node will also fail.

Troubleshooting Collect the following log files first: Clusterlog
Environment variable “clusterlog” must be set to a filename, usually cluster.log Set clusterlog = %windir%\cluster\cluster.log To set cluster log size in MB Set clusterlogsize = 20 Spfail.log NETMON sniffs if problem is believed to be network related

How to get Cluster Help Send the following to WolfHCT@Microsoft.com
log files system config info problem statement Must send logs with problem statement Clusterlog file from each node in cluster Submission related or procedural questions should be sent to

Cluster Testing Call To Action
Components Test with LOGO’d system & components Check cables & termination first Systems Get SDG1.0 designation Use cluster submission assistant Test with Windows 2000 Beta 3

Cluster Testing Questions

Driver Testing & Debugging Overview Brad Carpenter Group Manager WHQL Windows Operating Systems Division Microsoft Corporation

Driver Testing & Debugging Agenda
Overview Pool Tag Testing Driver Verifier Testing System Setup for Debugging Front Line Debugging Call To Action

Driver Testing & Debugging Overview
Tools added to Windows 2000 kernel for testing drivers Pool Tag Driver Verifier Improve Reliability and Stability Increases end-user satisfaction Reduces support costs Reduces Total Cost of Ownership

Pool Tag Testing What is it
Enables kernel mode testing of drivers Uses write protected memory pages to trap memory allocation errors Memory allocations come from the Special Pool Enabled by new API exAllocatePoolWithTag() Each driver has a “tag” associated with its memory allocation for tracking

Pool Tag Testing Memory Allocated by driver

Pool Tag Testing Write Protected “Memory Mirror”

Pool Tag Testing Driver writes beyond it’s allocated memory
Memory Allocated by Driver Write Protected “Memory Mirror” = Page Fault

Driver Verifier Testing What is it
Additional kernel tool only in Windows 2000 Integrated into WHQL June test kit release Can be run currently outside test kits Builds on Pool Tagging functionality in NT4 Easy user interface to turn on Catches the following driver problems Multiple releases of memory, spinlock’s, IRQL’s Use of un-initialized variables Touching pageable code at raised IRQL or while holding spinlock

Driver Verifier Testing What is it
All pool allocations from special pool Allows for catching memory corruption Allows for low memory testing, injecting random memory failures If driver is unloadable, validates all memory associated with driver has been freed Critical test for PnP drivers

Driver Verifier Testing Start, Run, “verifier”

Driver Verifier Testing Choose which drivers

Driver Verifier Testing Track Allocations, IRQL’s, Spinlocks

Driver Verifier Testing Track paged and non-paged pool

Driver Verifier Testing Bug Check Codes
IRQL_NOT_LESS_OR_EQUAL (0xA) PAGE_FAULT_IN_NONPAGED_AREA (0x50) ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE) SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (0xC1) BAD_POOL_CALLER (0xC2) DRIVER_VERIFIER_DETECTED_VIOLATION (0xC4) DRIVER_CORRUPTED_EXPOOL (0xC5) DRIVER_CAUGHT_MODIFYING_FREED_POOL (0xC6) TIMER_OR_DPC_INVALID (0xC7) IRQL_UNEXPECTED_VALUE (0xC8) DRIVER_VERIFIER_IOMANAGER_VIOLATION (0xC9) PNP_FATAL_ERROR (0xCA) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) PAGE_FAULT_IN_FREED_SPECIAL_POOL (0xCC) PAGE_FAULT_BEYOND_END_OF_ALLOCATION (0xCD) DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (0xCE) TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE (0xCF) DRIVER_CORRUPTED_MMPOOL (0xD0) DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1) DRIVER_PORTION_MUST_BE_NONPAGED (0xD3) SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (0xD4) DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (0xD5) DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (0xD6) DRIVER_UNMAPPING_INVALID_VIEW (0xD7) DRIVER_USED_EXCESSIVE_PTES (0xD8) LOCKED_PAGES_TRACKER_CORRUPTION (0xD9) SYSTEM_PTE_MISUSE (0xDA) DRIVER_CORRUPTED_SYSPTES (0xDB) DRIVER_INVALID_STACK_ACCESS (0xDC)

System Setup for Debugging Equipment
2 PC’s running same build For NT4 clean install NT4 build 1381 then install SP5 For Windows 2000 clean installation most recent build available Connect null modem cable from computer under test to computer used as debugger Install latest version of WHQL HCT CD for OS under test Pooltag turned on during install

System Setup for Debugging Final Steps
Modify boot.ini on test machine to turn on debugger Copy debugger executable and support files Add Service Pack support files Add debug component files Set system variables on debugger machine Start kernel debugger

Front line debugging Who’s at fault
If driver writes beyond allocated block of memory a fault will occur If Pool Tag related crash message at top of screen on the test machine will start with either: 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) or 0xA (IRQL_NOT_LESS_OR_EQUAL)

Front line debugging Debug the crash
Perform a “Stack trace” Enter “!reload” <cr> Enter “k” <cr> Result should look like this ntkrnlmp!RtlpBreakWithStatusInstruction ntkrnlmp!KeBugCheckEx+0x1f6 ntkrnlmp!MmAccessFault+0x328 ntkrnlmp!KiTrap0E+0xba Module!Function ....<--- (this is the faulting component) If no symbols are loaded the last line will look like 2040acdf

Driver Testing & Debugging Call To Action
Make drivers more reliable & stable Take advantage of the built in kernel test tools for both NT4 and Win2000 Actively work to debug your drivers Driver Verifier Spec Windows NT Debugging Setup

Driver Testing & Debugging Questions

ACPI System Testing Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

ACPI System Testing Agenda
Standalone ACPI Test Suite Recommended Windows 2000 ACPI Test Matrix Test Tool Demos System Test Implementer’s Forum ACPI Test Tools Call To Action

Standalone ACPI Test Suite
ACPIPack.exe is available on the Testkits web-site at: Should be used for validation of ACPI structures and functionality

ACPIINST Controls the launching and recording of log results from these tests: TreeTest Suspender Dozer Waker ACPI View gives a graphical view of the ACPI namespace objects

ACPIINST First verifies system capabilities by scanning the registry, playing a .wav file and using the hard disk Copies Test Driver ACPI98.sys over the ACPI system driver ACPI.sys Reboots system

TreeTest Tests ACPI Namespace, creates treetest.log
Tests ACPI Objects for proper definition and length. Verifies ACPI Methods are correct. Implementation specific, each system will have a slightly different structure and number of elements.

Suspender Test Overview
Sets Timer to wakeup in 60 seconds and sets the system to the deepest available Sleep-State, typically S1 or if supported S3. After wake-up, suspender verifies the functionality of the system by verifying sound, hard disk operation and other functionality discovered in the registry. Creates Suspender.log

Suspender Test Sleep Method
Call Win32 APIs: Set_Waitable_Timer for 60 seconds with a wakeup flag set. Sets the Operating System Timers Set_System_PowerState Programs the RTC alarm to the earliest wakeup event set in the operating system. Activates ACPI sleep states.

Suspender Test Wake Method
RTC Alarm triggers wake event. ACPI portion of the chipset begins to wake system starting with the system BUS, CPU, and finally triggers a System Control Interrupt (SCI). CPU does not know it was asleep until it sees bits set that indicate that it had gone to sleep. Suspender verifies that the operating system has issued a proper resume message.

Suspender Test Wake Method (continued)
Suspender calls Set_Thread_Execution_State with the ‘display required‘ flag set. ACPI inherently will try to save power at every opportunity. If no user is detected then display will not be activated.

Suspender Test Wake Method (continued)
RTC Alarm triggers wake event. ACPI portion of the chipset begins to wake system starting with the system BUS, CPU, and finally triggers a System Control Interrupt. CPU does not know it was asleep until it sees bits set that indicate that it had gone to sleep. Driver hanging during wakeup is the #1 cause of a system not resuming from sleep. First wake event is to change system LED.

Wakeup Tests Dozer and Waker
Wake on Ring Find a wake-capable modem Set server connection to wakeup machine with a modem connection Test under Windows 98 Second Edition or post-Beta 3 Windows 2000 Wake on LAN Find a wake-capable netcard Set server connection to wakeup machine with LAN connection Test under Windows 98 Second Edition or Windows 2000 Beta 3 RC1

Recommended Minimum Test Matrix for Windows 2000 ACPI and Power Management
Download From Microsoft Website Supported areas to be tested System Power Management Device Power Management Processor Power Management System Events Battery Management System Management Bus Controller

Windows 2000 Setup Will enable ACPI mode if the ACPI BIOS is ACPI Compliant and dated after For any system failures that occur, you can run the ACPI Viewer on the Microsoft Windows® 98 operating system to determine the BIOS failures

Test Matrix Highlights
All Sleep states must suspend and resume with all devices enabled and operational on resume Resume-on-Ring with external modem works Resume-on-Ring with PME-equipped machines and PME-capable modems works Resume from USB wake-capable devices works

Docking (Hot, Warm, & Cold)
When docked, all devices are seen both in the notebook and in the dock: PCI, ISA, R2, and CardBus cards behind the bridge Network and Multi-monitor works after docking Dock-based SCSI devices are read/write capable where appropriate Ten consecutive dock/undocks are accomplished in all configurations without error

Power Management Utilities
User can change power management utilities using the Control Panel: ACPI power button, sleep button, and lid options work according to user selection Battery alarms work according to user selection Device management timers work according to user selection

ACPI Thermal Functionality
CPU throttling occurs at proper intervals Passive and active cooling work at their designated trip points

Supplemental Stress Testing Should Include
Different sleep states (S1-S4) and resumes both in docked and undocked states PC Card network adapters, modems, hard disk sleep states, and peripheral devices

ACPI and Power Management Tests to be Completed

Test Tool Demos Standalone ACPI Test Suite
System Test Implementer’s Forum ACPI Test Tools

ACPI System Testing Call To Action
Download and Run ACPI Standalone Tests ACPIPack.exe at Download and Run Recommended Minimum Test Matrix Download and Run System Test Implementer’s Forum ACPI Tests Test Under Windows 98 Second Edition and Windows 2000 Beta 3

ACPI System Testing Questions

Hands-On Demo

WHQL Update Conference Call to Action
Fill out WHQL Survey and/or Visit Understand hardware requirements for non self-test submissions Pre-Test Devices before submission Run ACPI tests Use Pool Tagging and Driver Verifier to increase driver reliability and stability Raise quality of submissions to qualify for self-sign program Make sure submission paperwork, hardware, and drivers complete

WHQL Update Conference Questions

WHQL Update Conference May 1999

Similar presentations

Presentation on theme: "WHQL Update Conference May 1999"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

WHQL Update Conference May 1999

Similar presentations

Presentation on theme: "WHQL Update Conference May 1999"— Presentation transcript:

Similar presentations

About project

Feedback