Windows Drivers Certification (WHQL)

Jungo Connectivity‘s professional services unit provides a complete Windows Certification Program (previously known as WHQL) submission service for WinDriver and DriverCore customers.
All the required tests are performed by professional Jungo Connectivity engineers in the company’s dedicated lab, relieving customers of the expense and stress of in-house testing.

Test results are packaged by Jungo Connectivity in the required format and delivered to the customer for submission.

The driver signature certification is the means Microsoft has chosen of ensuring compatibility with its Windows operating systems. It aims to reduce driver and device conflicts by encouraging vendors to develop Windows-compatible drivers.

Setting up the complex testing environment required for Windows Certification Program tests can be a costly and daunting task for unfamiliar users. Jungo provides the necessary facilities and resources as part of its professional services packages to WinDriver and DriverCore customers.

Jungo’s dedicated Windows Certification Program testing lab and highly experienced engineering staff ensure that all tests and submission requirements are performed accurately and according to specification. The submission package includes certification test result for the WinDriver- and/or DriverCore-based host drivers.

Once the submission has been approved by Microsoft, the drivers are certified as Windows Certification Program-tested and the vendor entitled to display Windows Certification Program trademarks on its products.

Devices submitted to Jungo for Windows Certification Program testing undergo a rigorous testing process in a test environment built to Windows Certification Program specifications. The tests include:

Device Path Exerciser Test (Certification)

Plug and Play Driver Test (Certification)

Sleep and PNP (disable and enable) with IO Before and After

Embedded Signature Verification Test

Device Install Check For Other Device Stability

Verify Driver Load Order Group is not WdfLoadGroup

Device Driver INF Verification Test (Certification)

Concurrent Hardware And Operating System (CHAOS) Test

Device Install Check For File System Consistency

Reinstall with IO Before and After

Driver Memory Test

DevFund INF Test

PCI Root Port Surprise Remove Test (PCI devices only)

DevFund Broker Test

TDI filters and LSPs are not allowed

Once all the tests are successfully completed, the Windows Certification Programsubmission package is prepared by Jungo and delivered to the client for submission to Microsoft. Not being the owner of the devices, Jungo is precluded from submitting the package directly.

We use WinDriver PCI for 32-bit Windows, 64-bit Windows, 32-bit x86 Linux, and 64-bit x86 Linux. We have also used it for 32-bit x86 Solaris and 64-bit SPARC Solaris. This tool kit allows us to use a common driver interface for these platforms and greatly simplifies our software API architecture. Basic driver is very easy, advanced features like the kernel plug-in allow optimization of interrupt handling, etc.

Rich WadeAlta Data Technologies

The WinDriver worked out well for us. It took very little time to get the driver working. We have implemented DMA and interrupt.

Tak-kwong NgElectronics Engineer | NASA Langley Research Center

I started using the WinDriver Kit after looking at several other possibilities. All others that I looked at were targeted for Software Engineers with deep background on driver development, which for me being hardware-centric was a big obstacle. When I found the Jungo Tools I initially looked at the online video showing how to drive the kit. When I tried out the real software I was amazed that within ten minutes I had my first driver working and could interact with my custom FPGA-based board.