Command Line Parameters for the Flash Memory Read/Write and 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
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.
Note
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, which 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 command line parameters for the Flash Memory Read/Write and Performance Test.
| Command line parameter | Description |
|---|---|
/disk disk |
REQUIRED PARAMETER Specifies the device name of the disk to be tested (for example, DSK1:). The default is the first disk detected. |
/profile profile |
Limits testing to the devices of the specified storage profile. The default is all profiles. |
/store |
Opens the disk 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. |
/repeat count |
Specifies the number of times to repeat each timed operation. The default value is 2. |
/sectors count |
Specifies the number of sectors to read or write during each timed operation. The default value is 1. |
/rw count |
Specifies the amount of storage space to be tested. This can be expressed as a percentage, as a number of bytes, or as a number of sectors, as follows:
The default value is the total volume of the storage device. |
/log type |
Specifies how to log the output, as follows:
The default value is perflog. |
/readlog filename |
Specifies the location and name of the .csv file to which the test logs data about read performance. To specify a file in the release directory, use \release\filename.csv If you do not specify this parameter, the test does not save data about read performance. |
/writelog filename |
Specifies the location and name of the .csv file to which the test logs data about write performance. To specify a file in the release directory, use \release\filename.csv If you do not specify this parameter, the test does not save data about write performance. |
/fill list |
Specifies a list of filled percent of flash to test. The numbers should be separated by a comma (,) or a white space. For example, /fill 5, 10 tests with the conditions of 5% filled and 10% filled, separately. |
/delete |
Specifies that the test sends an IOCTL_DISK_DELETE_SECTORS command between each timed read/write operation. |