Presentation is loading. Please wait.

Presentation is loading. Please wait.

WHQL Update Conference May 1999. WHQL Update Conference Agenda Welcome Welcome WHQL Overview and Status WHQL Overview and Status Submission Process Submission.

Similar presentations


Presentation on theme: "WHQL Update Conference May 1999. WHQL Update Conference Agenda Welcome Welcome WHQL Overview and Status WHQL Overview and Status Submission Process Submission."— Presentation transcript:

1 WHQL Update Conference May 1999

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

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

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

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

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

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

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

9 What We Dont Do… Common Misperceptions Write or change the Systems Design Guide Write or change the Systems Design Guide Make marketing decisions Make marketing decisions Write all the tests Write all the tests Incorporate passing drivers into OS Incorporate passing drivers into OS Implement features in the OS Implement features in the OS Manage the IHVs or OEMs Manage the IHVs or OEMs

10 WHQL Process End to End

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

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

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

14 Self Test Status Testing turnaround times Goal '98'99 Self Test Systems Non-Self Test Systems Self Test Devices7 10 Non-Self Test Devices

15 Self Test Status System Submissions Past 6 months % Complete in # of days Volume Desktop Mobile Reference Server

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

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

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

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

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

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

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

23 Design Guide Transition Servers Hardware Design Guide for Microsoft Windows NT Server 2.0 (SDG 2.0) goes into effect July 1, 1999 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 systems can contain any combination of the following devices SDG 2.0 SDG 2.0 PC 99 PC 99 SDG 1.0 SDG 1.0 PC 98 PC 98

24 WHQL Status Call To Action Give us your feedback! Give us your feedback! Fill out survey please Fill out survey please Visit WHQL web page Visit WHQL web pagehttp://www.microsoft.com/hwtest Prepare for Design Guide transition Prepare for Design Guide transition

25 WHQL Status Questions

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

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

28 Submission Process Flow End to End

29 Non Self-Test vs. Self-Test Comparision Self-Test Non Self-Test 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)

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

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

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

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

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

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

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

37 Submission Status Page

38

39

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

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

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

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

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

45 Hardware Compatibility List

46

47 System Submission Assistant

48

49

50

51

52

53

54

55

56

57

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

59 System Submission Process System Refresh Rules To qualify for a refresh the system must observe the following rules: To qualify for a refresh the system must observe the following rules: HCT Kit – must always use a current HCT kit release. 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 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. Failures due to new test coverage will be listed as warnings in the test report. BIOS BIOS Minor BIOS changes, such as timing issues, are allowed 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 BIOS changes that alter fundamental ACPI, Plug and Play, or power management functionality requires a complete retest under the current guidelines

60 System Submission Process System Refresh rules System Refresh Rules (contd): System Refresh Rules (contd): CPU upgrades CPU upgrades New CPUs must be pin compatible with the original 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. Architecture and/or CPU manufacturer changes will require a complete test-run under the current guidelines. Component changes Component changes Add-in components: New logod Add-in components are allowed without retesting Add-in components: New logod 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 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 New components must be from the same manufacturer and must be pin-compatible with the original component

61 System Submission Process System Refresh Rules System Refresh Rules (contd): System Refresh Rules (contd): For Mobile systems only: For Mobile systems only: TFT display size changes on mobile systems are allowed 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 New docking stations for mobiles must meet the current specification at the time of the refresh

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

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

64

65 Device Test Kits & FAQs

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

67 Submission Process Questions

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

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

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

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

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

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

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

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

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

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

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

79 Non Self-Test Issues Systems System arrives and doesnt boot System arrives and doesnt boot Loose components Loose components Missing CPUs Missing CPUs Missing HDs or no HDs Missing HDs or no HDs SCSI HDs set to same ID number SCSI HDs set to same ID number Power supply not plugged into MB Power supply not plugged into MB BIOS password BIOS password Bad system Bad system

80 Non Self-Test Issues Drivers Missing drivers Missing drivers Drivers that dont install Drivers that dont install Pre-Test the floppys / CDs submitted Pre-Test the floppys / CDs submitted Un-LOGOd driver Un-LOGOd driver Incomplete driver set Incomplete driver set Wrong drivers system components Wrong drivers system components

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

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

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

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

85 System Description Form

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

87 Non Self-Test Issues Questions

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

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

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

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

92 Self-Sign Program Windows 2000 implementation Multiport Serial Adpt MultimediaAudioDVD Video Capture GameportPrinter SCSI Adapter Smart Card Reader Display Adapter Hard Drive Controller KeyboardHIDModemMonitorMouse Net Adapter Warn set for the following classes:

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

94 How Verification Works By default this tool will scan Core System Files, all driver files installed in Device Manager, and all printer drivers installed. By default this tool will scan Core System Files, all driver files installed in Device Manager, and all printer drivers installed.

95 How Verification Works 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. 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.

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

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

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

99 Self-Sign Program Reporting Qualified vendor will submit report 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 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 will be done online Reporting required twice a month Reporting required twice a month

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

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

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

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

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

105 Self-Sign Program Questions

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

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

108 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

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

110 Designing-In Compliance S/WTestSpecS/WTestSpec H/WTestSpecH/WTestSpec WHQL Hardware Tests PASS FAIL System Design Guide and Test Specifications co-authored by Microsoft and Intel

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

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

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

114 System Test-IF Coverage Goal: 100% H/W Test Coverage for PC 2001 PC 99 PC 2001 Video 3DPCI ACPI PC Card AGPImage ATA USB Mobile Audio 100%

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

116 System Test-IF Members Philips Components Phoenix Technologies, Ltd. S3, Inc. Silicon Motion, Inc. Sonnetech, Ltd. Toshiba Corporation Trident Microsystems, Inc. Videologic, Ltd. Viewsonic Corporation Xircom Fujitsu, Ltd. Gateway 2000, Inc. IBM Corporation Matrox Graphics, Inc. Micro Design Resources Micron Semiconductor Mitsubishi Electric NEC Computer Systems NeoMagic Corporation nVidia Corporation 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 Current Membership: 30 and Growing!

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

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

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

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

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

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

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

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

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

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

127 System Test Implementers Forum Questions

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

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

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

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

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

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

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

135 On-Board Components Examples for OEMs process OEM may submit integrated devices or have IHVs submit for them OEM may submit integrated devices or have IHVs submit for them OEM may wait until several devices are ready then submit a batch for the reduced fee and two test system method 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 Logos and signed drivers Self-test makes this possible with reduced turnaround of Logos and signed drivers With self-test you know when you will pass With self-test you know when you will pass WHQL auditing will occur out of your cycle WHQL auditing will occur out of your cycle

136 On-Board Components Example of reduced costs System has integrated audio, display, input and LAN 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 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 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 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 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 Expensive pre-production systems may be used, as long as the drivers and firmware are final, and will be exchanged for final product

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

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

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

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

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

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

143 Device & Component Updates Questions

144 Lunch

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

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

147 RAID JBOD RAID ID string in firmware or bios ID string in separate NVRAM No ID string Your Product in search of HCL listing What Category am I? IHV tested? IHV Submitted ? With Hardware? OEM tested? OEM submitted? With Hardware? Logod Product listed on the HCL Yes No Yes No RAID JBOD RAID ID string in separate NVRAM No ID string ID string in firmware or bios Cluster HCL for RAID Systems

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

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

150 Cluster Component Test Standalone 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 Client Network Hub Network Hub for Private interconnect (heartbeat) Shared Storage Device (RAID System) Cluster Node A Cluster Node B Primary Domain Controller, Also used as Client Node in Basic test Environment Shared SCSI BUS, use a hub for Fibre Channel connections Do not Terminate BUS at RAID System Terminate BUS externally at each Node using Y connector

151 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 Client Network Hub Network Hub for Private interconnect (heartbeat) Shared Storage Device (RAID System) Cluster Node A Cluster Node B Shared SCSI BUS, use a hub for Fibre Channel connections Do not Terminate BUS at RAID System Terminate BUS externally at each Node using Y connector

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

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

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

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

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

157 Troubleshooting Collect the following log files first: Collect the following log files first: 1. 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 = Spfail.log 3. NETMON sniffs if problem is believed to be network related

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

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

160 Cluster Testing Questions

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

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

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

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

165 Pool Tag Testing Memory Allocated by driver

166 Pool Tag Testing Write Protected Memory Mirror

167 Pool Tag Testing Driver writes beyond its allocated memory = Page Fault Memory Allocated by DriverWrite Protected Memory Mirror

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

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

170 Driver Verifier Testing Start, Run, verifier

171 Driver Verifier Testing Choose which drivers

172 Driver Verifier Testing Track Allocations, IRQLs, Spinlocks

173 Driver Verifier Testing Track paged and non-paged pool

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

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

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

177 Front line debugging Whos at fault If driver writes beyond allocated block of memory a fault will occur 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: If Pool Tag related crash message at top of screen on the test machine will start with either: 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) 0x50 (PAGE_FAULT_IN_NONPAGED_AREA) or or 0xA (IRQL_NOT_LESS_OR_EQUAL) 0xA (IRQL_NOT_LESS_OR_EQUAL)

178 Front line debugging Debug the crash Perform a Stack trace Perform a Stack trace Enter !reload Enter !reload Enter k Enter k Result should look like this Result should look like thisntkrnlmp!RtlpBreakWithStatusInstructionntkrnlmp!KeBugCheckEx+0x1f6ntkrnlmp!MmAccessFault+0x328ntkrnlmp!KiTrap0E+0xba Module!Function....<--- (this is the faulting component) If no symbols are loaded the last line will look like 2040acdf

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

180 Driver Testing & Debugging Questions

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

182 ACPI System Testing Agenda Standalone ACPI Test Suite Standalone ACPI Test Suite Recommended Windows 2000 ACPI Test Matrix Recommended Windows 2000 ACPI Test Matrix Test Tool Demos Test Tool Demos Standalone ACPI Test Suite Standalone ACPI Test Suite System Test Implementers Forum ACPI Test Tools System Test Implementers Forum ACPI Test Tools Call To Action Call To Action

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

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

185 ACPIINST First verifies system capabilities by scanning the registry, playing a.wav file and using the hard disk 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 Copies Test Driver ACPI98.sys over the ACPI system driver ACPI.sys Reboots system Reboots system

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

187 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. 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. 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 Creates Suspender.log

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

189 Suspender Test Wake Method RTC Alarm triggers wake event. 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). 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. 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 verifies that the operating system has issued a proper resume message.

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

191 Suspender Test Wake Method (continued) RTC Alarm triggers wake event. 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. 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. 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. Driver hanging during wakeup is the #1 cause of a system not resuming from sleep. First wake event is to change system LED. First wake event is to change system LED.

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

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

194 Windows 2000 Setup Will enable ACPI mode if the ACPI BIOS is ACPI Compliant and dated after 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 For any system failures that occur, you can run the ACPI Viewer on the Microsoft Windows® 98 operating system to determine the BIOS failures

195 Test Matrix Highlights All Sleep states must suspend and resume with all devices enabled and operational on resume 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 external modem works Resume-on-Ring with PME-equipped machines and PME-capable modems works Resume-on-Ring with PME-equipped machines and PME-capable modems works Resume from USB wake-capable devices works Resume from USB wake-capable devices works

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

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

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

199 Supplemental Stress Testing Should Include Different sleep states (S1-S4) and resumes both in docked and undocked states 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 PC Card network adapters, modems, hard disk sleep states, and peripheral devices

200 ACPI and Power Management Tests to be Completed

201

202

203 Test Tool Demos Standalone ACPI Test Suite Standalone ACPI Test Suite System Test Implementers Forum ACPI Test Tools System Test Implementers Forum ACPI Test Tools

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

205 ACPI System Testing Questions

206 Hands-On Demo

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

208 WHQL Update Conference Questions

209


Download ppt "WHQL Update Conference May 1999. WHQL Update Conference Agenda Welcome Welcome WHQL Overview and Status WHQL Overview and Status Submission Process Submission."

Similar presentations


Ads by Google