Device Driver Loader and Tux Extender
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The Device Driver Loader and Tux Extender (DDLX), Ddlx.dll, is a set of tools that extend the capabilities of the Tux test harness. DDLX allows the dynamic-link library (DLL) for your test to operate in either an application or a Device.exe address space.
When using Tux alone, your test DLL loads into the address space for Tux. However, when using DDLX in combination with Tux, Ddlx.dll loads into the address space for Tux. Ddlx.dll registers your test DLL as a device driver in the Device.exe address space and provides an interface to your test DLL. This approach allows your test DLL to run in the Device.exe address space while also taking advantage of the functionality that Tux provides.
When your test DLL executes and returns values to DDLX, DDLX accepts the return codes and translates them into valid return codes for Tux. DDLX provides a way for Tux and your test DLL to communicate across different address spaces.
The following command line shows the syntax for running a test using Ddlx.dll.
tux –d ddlx –c "-d test_dll –i device_index -c parameters "
In this command line, test_dll is the name of the test library, device_index is the index of the device, and parameters represents additional parameters. The -d ddlx –c parameters outside of the quotation marks are parameters for Tux. These parameters instruct Tux to load Ddlx.dll into the process space for Tux and then pass the entire string enclosed in quotation marks to Ddlx.dll.
The list of parameters for Ddlx.dll enclosed in quotation marks does not require a space, a command line option, and its argument. However, you must insert a space between each command line option. The following command line lacks spaces between the elements, and so is not acceptable.
tux -d ddlx -c "-dtest.dll-i2" (NOT ACCEPTABLE)
The following table shows the parameters for DDLX.
| Parameter | Description |
|---|---|
-d test_dll |
File to register. If you do not specify this option, DDLX attempts to load Generic.dll. |
-i device_index |
Device index for the driver. If you do not specify this option, DDLX uses a value of 1. |
-c parameters |
Additional parameters for test_dll to pass on to the device driver being tested. |
The following command line shows the syntax for a sample test.
tux –o –d ddlx –c "-d test.dll –i 2 –c 1 2 3"
In this example, the device driver being tested receives the "1 2 3" string as a command line.
If you do not need to specify a device index or any additional command line parameters, you can omit the quotation marks and the –d parameter. The following command line shows the syntax for this scenario.
tux –o –d ddlx –c test.dll
Note
The command line for DDLX supports a maximum of 16 arguments and 128 characters.