Presentation is loading. Please wait.

Presentation is loading. Please wait.

WHQL Update Conference April 19 th, 1999 Munich, Germany.

Similar presentations


Presentation on theme: "WHQL Update Conference April 19 th, 1999 Munich, Germany."— Presentation transcript:

1 WHQL Update Conference April 19 th, 1999 Munich, Germany

2 WHQL Update Conference Agenda Welcome Welcome WHQL Status WHQL Status Pre-Submission Requirements Pre-Submission Requirements Submission Requirements & Process Submission Requirements & Process Lunch Lunch Self-Sign Program Self-Sign Program Driver Testing & Debugging Driver Testing & Debugging Q & A Q & A

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

4 WHQL Status Agenda WHQL Mission Statement WHQL Mission Statement Where We are Today Where We are Today Where We are Going Where We are Going System Test Implementers Forum System Test Implementers Forum Design Guide Transition Design Guide Transition MiniPCI Program MiniPCI Program On-Board Components On-Board Components 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 Where We Are Today Submissions 24,000 overall submissions in ,000 overall submissions 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

10 Where We Are Today Self-test programs 64 total test programs 64 total test programs Currently 23 are self-test Currently 23 are self-test Key device programs past year: Key device programs past year: Audio, Display, Hard Drive, Keyboard, Imaging, Mouse, Net Adapter, Printing Planned to be self-test by end of year: Planned to be self-test by end of year: 1394, Analog Modem, CD-ROM, Dual- Proc Systems, Monitor, Motion Video

11 Where We Are Going Internet Re-design of /hwtest/ Web page Re-design of /hwtest/ Web page Make information easier to find Make information easier to find Redesigned HCL for increased reliability Redesigned HCL for increased reliability Personalized Web page - My WHQL Personalized Web page - My WHQL Status Ticker Status Ticker Online submissions from Web page Online submissions from Web page Real-time Master ID Real-time Master ID Hardware sent in parallel to submission Hardware sent in parallel to submission Streamlines administrative process Streamlines administrative process

12 Where We Are Going Test kit feedback Feedback from customers on kits Feedback from customers on kits More predictable, less frequent, better documented More predictable, less frequent, 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

13 Where We Are Going Test kit releases Next test kit release in June 99 Next test kit release in June 99 Updated Kits Updated Kits HCT CD HCT CD Display CD Display CD 35+ Device Test Kits 35+ Device Test Kits Enables testing submissions on Enables testing submissions on Windows 2000 Beta3 Windows 2000 Beta3 Windows 98 Second Edition Windows 98 Second Edition Windows NT ® 4.0 SP5 Windows NT ® 4.0 SP5

14 System Test Implementers Forum Designing-in compliance Consistent and objective test tools help compliance and reduce product cycle time Consistent and objective test tools help compliance and reduce product cycle time Joint Microsoft and Intel hardware test strategy Joint Microsoft and Intel hardware test strategy Deliver objective hardware test specs and tests Deliver objective hardware test specs and tests Tests map to Design Guide requirements Tests map to Design Guide requirements WHQL will incorporate appropriate tests WHQL will incorporate appropriate tests System Test Implementers Forum System Test Implementers Forumhttp://www.systemtest.org

15 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

16 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

17 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

18 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

19 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

20 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 FAQs at For more info see WHQL Modem and Network FAQs at

21 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 programs New Batch submission process for multiple Self-Test programs 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

22 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 arrival of production system WHQL will return Pre-Production system upon arrival of production system

23 WHQL Status Call To Action Please give us your feedback via survey and/or Please give us your feedback via survey and/or Visit WHQL web page Visit WHQL web pagehttp://www.microsoft.com/hwtest Prepare for Design Guide transition Prepare for Design Guide transition MiniPCI vendors prepare for 3 phase testing plan MiniPCI vendors prepare for 3 phase testing plan Visit WQHL web page for more info Visit WQHL web page for more info

24 WHQL Status Questions

25 Pre-Submission Requirements Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

26 Pre-Submission Requirements 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

27 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

28 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

29 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

30 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

31 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

32 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

33 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

34 MS System Configuration Testing Machine Config Three partitions Three partitions Boot partition Fat minimum Boot partition Fat 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

35 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

36 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

37 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

38 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

39 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

40 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

41 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

42 System Description Form

43 Pre-Submission Requirements 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

44 Pre-Submission Requirements Questions

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

46 Submission Requirements & Process Agenda Submission Requirements Submission Requirements Submission Assistant Submission Assistant Submission Process Submission Process

47 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! Use Submission Assistant! Completed Agreements Completed Agreements Testing agreement Testing agreement Legal agreement Legal agreement Payment for testing Payment for testing Hardware for Non Self-Test Systems Hardware for Non Self-Test Systems

48 Submission Assistant

49

50

51

52

53

54

55

56

57

58

59 Submission Process 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 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

60 Submission Process 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

61 Submission Process 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

62 Submission Process 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 Real-time status tickers Real-time status tickers Available in future on WHQL web page Available in future on WHQL web page Tracking both test turn-around times and submissions Tracking both test turn-around times and submissions

63 Submission Requirements & Process Questions

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

65 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

66 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

67 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

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

69 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

70 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

71 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

72 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

73 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

74 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

75 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

76 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

77 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 -

78 Self-Sign Program Questions

79 Driver Testing & Debugging Overview Thomas Wohllaib WHQL Systems Team Lead Windows Operating Systems Division Microsoft Corporation

80 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

81 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

82 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

83 Pool Tag Testing Memory Allocated by driver

84 Pool Tag Testing Write Protected Memory Mirror

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

86 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

87 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

88 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

89 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

90 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)

91 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

92 Pool Tag and Driver Verifier Documents Driver Verifier Spec Driver Verifier Spec Windows NT Debugging Setup Windows NT Debugging Setup

93 Driver Testing & Debugging Call To Action Make your drivers more reliable and more stable Make your drivers more reliable and more 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

94 Driver Testing & Debugging Questions

95 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 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

96 WHQL Update Conference Questions

97


Download ppt "WHQL Update Conference April 19 th, 1999 Munich, Germany."

Similar presentations


Ads by Google