Troubleshooting the Storage Device Block Driver Performance Test
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
- 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 Windows Embedded CE 6.0 Test Kit (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. - The test starts by displaying basic information about the storage device, containing the name of the device, the handle of the device, the number of sectors on the device, and the number of bytes per sector. The test does not give information about cylinders, heads, sectors, and flags, because this information is not relevant to the Storage Device Block Driver Performance Test.
If the device driver does not return an error, the test then shows how many sectors it writes to and how long, in milliseconds, the operation takes to complete. A message indicates that the test is attempting to read from those sectors. If the device driver does not return an error, the test attempts to verify that the data read is correct.
For more details about the content of the log, see Managing Performance Results Using PerfLog. You can choose to write your own parser to convert the raw data or use the default parser, PerfToCsv Tool, provided by Microsoft.
For more troubleshooting help, see Troubleshooting the CETK Tests.