Modifying the Storage Device Block Driver API Test (Windows CE 5.0)
The Storage Device Block Driver API Test runs the tux –o –d disktest command on default execution. With the default command line, the test runs on the first enumerated mass storage device that matches the BLOCK_DRIVER_GUID interface and supports the IOCTL_DISK_GETINFO I/O control code (IOCTL) or the DISK_IOCTL_GETINFO IOCTL.
Warning During the test, all information on the storage device is destroyed. The test writes to and reads from sectors on the storage device without preserving the contents of the sectors. Microsoft recommends that you back up data on all cards and disks that are attached to the tested device before running the test.
If you run the unmodified test, it will fail. In the results file you will see a message warning you to back up data on all cards and disks that are attached to the testing device before running the test. It then instructs you to modify the command line by right clicking on the test in the CETK tree control, choosing Edit Command Line, and adding the following switch to the command line:
-zorch
After saving this change, you can run the test successfully. You can also pass this parameter in with Tux's -c command-line parameter.
You can modify the test by editing the command line. To specify one or more of the following optional command-line parameters for this test, use the –c command-line parameter. The -c parameter forces Tux to pass the specified string into the test module. For more information about how to edit the command line for a test, see Editing the Command Line for a Test.
The following table shows the modifications you can make to the test.
| To | Add this command-line parameter |
|---|---|
| Specify the device name of the disk to be tested.
If you do not specify this parameter, the test probes for a mass storage disk on devices |
|
| Force the test to use previous disk I/O control codes (IOCTLs) rather than the current set of IOCTLs.
The previous IOCTLs begin with DISK_IOCTL_ and are not Microsoft® Windows® CE IOCTLs. The current set of IOCTLs begin with IOCTL_DISK_. Many block drivers support both previous and current IOCTLs. You can use this parameter to verify that current and previous IOCTLs work correctly. |
|
| Set the maximum number of sectors per read/write transaction.
Specify this parameter for a storage device according to the physical limit on the number of sectors transferred by the storage device at one time. The default value is 128 sectors. |
|
| Specify that the test opens a handle to the disk by using the OpenStore function instead of the CreateFile function.
Opening a handle by using the OpenStore function is not required to test block driver functionality. However, it is useful for testing a storage device that Filesys.exe loads automatically if you cannot open the storage device as a stream device. For example, you can open a handle to a flash driver for ROM by using the OpenStore function. |
|
| Enable the functionality of the test. Without this parameter, the test will fail. With this parameter, the test will run and destroy all data on the storage devices. | |
For information about other command-line parameters for Tux.exe, see Tux Command-Line Parameters.
See Also
Storage Device Block Driver API Test | Storage Device Block Driver API Test Cases
Send Feedback on this topic to the authors