Modifying the Flash Memory Read/Write and Performance Test (Windows CE 5.0)
The Flash Memory Read/Write and Performance Test executes the tux –o –d flshwear –f command by default. Modify the default command line to specify the device name of the disk to be tested.
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.
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 to 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 modify the Flash Memory Read/Write and Performance Test
| To | Add this command-line parameter |
|---|---|
| Specify the device name of the disk to be tested.
This parameter is required. |
|
| Specify the number of times to repeat each timed operation.
The default value is 2. |
|
| Specify the number of sectors to read or write during each timed operation.
The default value is 1. |
|
| Specify the name of the .csv file to which the test logs data about read performance.
To specify a file in the release directory, use If you do not specify this parameter, the test does not save data about read performance. |
|
| Specify the name of the .csv file to which the test logs data about write performance.
To specify a file in the release directory, use If you do not specify this parameter, the test does not save data about write performance. |
|
| Specify that the test sends an IOCTL_DISK_DELETE_SECTORS command between each timed read/write operation. | |
| Specify that the test opens a handle to the drive 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. Opening a handle by using the OpenStore function 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. |
|
For information about other command-line parameters for Tux.exe, see Tux Command-Line Parameters.
See Also
Flash Memory Read/Write and Performance Test | Flash Memory Read/Write and Performance Test Cases
Send Feedback on this topic to the authors