Modifying the CD/DVD-ROM Block Driver Test (Windows CE 5.0)
The CD/DVD-ROM Block Driver Test executes the tux –o –d cdromtest –f command by default. With the default command line, the test runs on the first enumerated CD/DVD ROM drive that matches the BLOCK_DRIVER_GUID interface and supports the IOCTL_CDROM_DISC_INFO and IOCTL_CDROM_READ_TOC I/O control codes (IOCTLs).
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 modify the CD/DVD-ROM Block Driver Test
| To | Add this command-line parameter |
|---|---|
| Specify the device name of the disk to be tested.
If the test cannot open the disk that you specify, the test skips test cases. If you do not specify this parameter, the CD/DVD-ROM Block Driver Test probes for a CD-ROM drive or CD/DVD-ROM drive on devices |
|
| Specify a profile to filter devices for testing.
If you specify a profile, the test runs on each device that responds to the IOCTL_DISK_DEVICE_INFO IOCTL and, in the STORAGEDEVICEINFO structure, returns a profile name matching the name that you specify. By default, the test does not filter devices by profile. |
|
Specify the name of a file that contains an image of the data on the media in the CD/DVD-ROM drive. If the image file that you want to use is in the release directory, specify \release\<file_name>. You can specify an .iso file or other type of CD-ROM or DVD-ROM image.
Test cases 6003 through 6005 use this parameter. The contents of the image file are compared to the actual contents of the media in the drive. If you do not specify this parameter, the test attempts to open the Cdsector.dat file in the release directory. If the test cannot access the release directory on the development workstation, the image file is not used. If you specify this parameter for test case 6101, the test creates an image of the media in the drive and stores the image in the release directory under the specified file name. |
|
| Set the maximum number of sectors that can be read from the disk in any single read request.
Test cases 6003 through 6006 use this value. The default value is 64 sectors. |
|
| Set the maximum number of retry attempts for a failed read operation.
The default value is 5. |
|
| Specify the final sector to read.
Test cases 6003 through 6006 use this value. If you do not specify this value, the test reads until failure. |
|
| Specify that the media in the CD/DVD-ROM drive is a DVD rather than a CD.
This parameter determines the maximum final sector that the test attempts to read. If this parameter is not set, the maximum sector read is 328220. If this parameter is set, the maximum sector read is 3725375. |
|
| Specify that the test opens a handle to the CD/DVD-ROM 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, but might be useful in certain scenarios. |
|
Specify that the test opens a volume handle to the CD/DVD-ROM drive, for example CreateFile("CDROM Drive\VOL:"), instead of CreateFile(""DSK1:").
Opening a volume handle is not required to test block driver functionality, but might be useful in certain scenarios. |
|
For information about other command-line parameters for Tux.exe, see Tux Command-Line Parameters.
See Also
CD/DVD-ROM Block Driver Test | CD/DVD-ROM Block Driver Test Cases
Send Feedback on this topic to the authors