Unclassified Signature Program for WHQL signature

12.3.2.1 WHQL DTM Test Notes
As indicated in the WHQL documentation, before submitting the driver for testing you need to download Microsoft's Driver Test Manager (DTM) (http://www.microsoft.com/whdc/DevTools/WDK/DTM.mspx) and run the relevant tests for your hardware/software. After you have verified that you can successfully pass the DTM tests, create the required logs package and proceed according to Microsoft's documentation.
When running the DTM tests, note the following:
The DTM test class for WinDriver-based drivers should be Unclassified - Universal Device.
The Driver Verifier test is applied to all unsigned drivers found on the test machine. It is therefore important to try and minimize the number of unsigned drivers installed on the test PC (apart from the test driver - windrvr6.sys).
The USB Selective Suspend test requires that the depth of the under-test USB device in the USB devices tree is at least one external hub and no more than two external hubs deep.
The ACPI Stress test requires that the ACPI settings in the BIOS support the S3 power state.
Verify that the /PAE switch is added to the boot flags in the PC's boot.ini file.
The tests submission requires you to provide a *.pdb debug symbol file and an ouput of the PREfast utility (defects.xml). You can find copies of these files for the windrvr6.sys driver in the WinDriverredist directory. When selecting to rename and rebuild the windrvr6.sys driver module, as explained in section 12.2, a new debug symbols file is created for the driver. (The original defects.xml file is also applicable to the rebuilt driver).
Before submitting the file for certification you need to create a new catalog file, which lists your driver and specific INF file(s), and refer to this catalog file from your INF file(s), as explained above [12.3.2].

https://www.jungo.com/st/support/documentation/windriver/910/wdusb_man_mhtml/node71.html

FAQ for Windows Logo Program V. 3.0
https://www.microsoft.com/whdc/winlogo/VistaLogofaq.mspx


Unclassified Signature Program
https://www.microsoft.com/whdc/winlogo/drvsign/dqs.mspx

DTM Audio Fidelity Test

Audio Fidelity Test:
http://msdn.microsoft.com/en-us/library/bb961150.aspx
http://www.microsoft.com/whdc/whql/audiofidelity.mspx

The training video on Fidelity Test:
http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/DTM-AudioFidelityTestingLocal_Training.exe
http://download.microsoft.com/download/f/0/5/f05a42ce-575b-4c60-82d6-208d3754b2d6/DTM-AudioFidelityLogs_Training.exe

The equipment:
Windows Vista Logo Testing
http://ap.com/products/2700/vista_testing
The SYS-2722A-M
Microsoft Corporation has selected the Audio Precision SYS-2722A audio analyzer exclusively for its Windows Vista Logo Program Audio Fidelity tests.
To simplify ordering, Audio Precision has created a special product configuration of the SYS-2722A that includes all the filters and cables required by the Microsoft Driver Test Manager.

The details of test (Chinese):
http://ic.newmaker.com/art_28773.html

Misc Information

1. Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
To enable Driver Verifier by editing the registry, follow these steps: Start Registry Editor (Regedt32). Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriversEdit the REG_SZ key.Set the REG_SZ key to the case-insensitive names of the drivers that you want to test.

2. Why CreateProcess failed in Unicode project with an access violation.
e.g:
CreateProcess( NULL, _T("test.exe"), NULL, ....) will fail with an unhandled exception in a UNICODE project.

MSDN:
The Unicode version of this function, CreateProcessW, can modify the contents of this string. Therefore, this parameter cannot be a pointer to read-only memory (such as a const variable or a literal string). If this parameter is a constant string, the function may cause an access violation.

3. Sometimes you may experience CreateFile failed with error code 5(Access is Denied) .

Security descriptors contain the security information associated with securable objects. For most securable objects, you can specify an object's security descriptor in the function call that creates the object.

Specifying a Security Descriptor From an INF File

http://msdn.microsoft.com/en-us/library/aa377450.aspx

For example, the following INF file snippet would create a registry key to which only administrators and the system have access. Note that this example requires administrative privileges.

 [DDInstall]

AddReg=mydevice.reg

 

[mydevice.reg]

include Registry information here

 

[mydevice.reg.Security]

"D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"

SDDL for Device Objects

http://msdn.microsoft.com/en-us/library/ms794693.aspx