Active Control Test
Command-line parameter: /acControlCodeFile
The Active Control Test is a customized test that Device Path Exerciser generates for the driver based on the I/O control codes in an input file. This test is designed to exercise the I/O requests that the driver actually supports in practical use. The Active Control Test is available on Microsoft Windows XP and later versions of Windows.
The Active Control Test includes the I/O control codes (no FSCTLs) in the input file, along with numerous variations of those I/O control codes, including randomly generated function codes and function codes numerically higher, lower, and in between those in the file.
Device Path Exerciser sends the device an extremely high volume of customized calls in rapid succession with varying buffer lengths, addresses, and content, varying access requirements, and varying function codes and device types.
To generate an input file of the control codes that the driver supports, you can use the IRP Logging feature in Driver Verifier, which records the I/O control codes that the driver uses during a Driver Verifier test, or you can type the input file in Notepad and customize it for testing or troubleshooting.
The input file for the Active Control Test is a formatted text file. You can use several different methods to generate this file:
- Use the IRP Logging feature in Driver Verifier and DC2WMIParser (dc2wmiparser.exe), a tool included in the Windows Driver Kit (WDK). IRP Logging is supported only on Windows Server 2003 and later versions of Windows.
The IRP logging feature uses WMI software tracing to record incoming and outgoing IRPs that the driver uses during a standard Driver Verifier test. DC2WMIParser interprets the trace log and creates a formatted text file for Device Path Exerciser.
For information about IRP logging and DC2WMIParser, see IRP Logging.
Type the file in a text editor, such a Notepad, or edit the file that DC2WMIParser generates. The file format is described in IRP Logging.
Use other WMI tools, such as WBEMTest, to extract the data from the WMI trace log while Driver Verifier is running. (You will have to write a program or script to format the data.)
The Driver Verifier method is the most convenient. However, because the IRP logging and parsing method samples from a circular log of IRPs and because it attributes IRPs to the driver at the bottom of the driver stack, the output might not accurately reflect the control codes that the driver processes under normal conditions. To ensure the accuracy of the test, review the input file before submitting it to Device Path Exerciser.
Build date: 9/14/2012