Category : Recently Uploaded Files
Archive   : INFOPACK.ZIP
Filename : TESTDRV.RTF

{\rtf1\ansi \deff0{\fonttbl{\f0\froman Tms Rmn;}{\f1\fdecor Symbol;}{\f2\fswiss Helv;}{\f3\fdecor ZapfDingbats;}{\f4\fmodern Courier;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;
\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;}{\stylesheet{\s242\tqc\tx4320\tqr\tx8640 \fs20 \sbasedon0\snext242 footer;}{\s243\tqc\tx4320\tqr\tx8640 \fs20 \sbasedon0\snext243 header;}{\fs20 \snext0 Normal;}}
{\info{\title MSCDEX Driver Test Document}{\author John Y. Geer}{\operator John Y. Geer}{\creatim\yr1990\mo8\dy13\hr8\min37}{\revtim\yr1990\mo8\dy13\hr8\min40}{\printim\yr1990\mo8\dy14\hr14\min56}{\version3}{\edmins60}{\nofpages3}{\nofwords66409}
{\nofchars71166}{\vern8310}}\margr1890\widowctrl\ftnbj \sectd \linex0\endnhere\titlepg {\footer \pard\plain \qr\sl240 \fs20 {\b\f2\fs16 TESTDRV Test Utility - Copyright (C) Microsoft Corp. 1990. All rights reserved - page }{\field{\*\fldinst {\b\f2\fs16
page}}{\fldrslt {\b\f2\fs16 3}}}{\b\f2\fs16
\par }\pard\plain \s242\qc\tqc\tx4320\tqr\tx8640 \fs20
\par }{\headerf \pard\plain \s243\qc\tqc\tx4320\tqr\tx8640 \fs20 {\b\f2\fs28 Microsoft MS-DOS CD-ROM Extensions
\par TESTDRV Test Utility
\par 15 August 1990
\par }\pard \s243\tqc\tx4320\tqr\tx8640
\par }{\footerf \pard\plain \qr\sl240 \fs20 {\b\f2\fs16 TESTDRV Test Utility - Copyright (C) Microsoft Corp. 1990. All rights reserved - page }{\field{\*\fldinst {\b\f2\fs16 page}}{\fldrslt {\b\f2\fs16 1}}}{\b\f2\fs16
\par }\pard\plain \s242\qc\tqc\tx4320\tqr\tx8640 \fs20
\par }\pard\plain \fs20 {\fs22
TESTDRV is a rigorous test utility for CD-ROM device drivers to verify that the drivers adhere to specifications. This driver test attempts to fully exercise all possible calls to the device driver and record the driver's progress.
\par
\par }{\plain \b Setup for TESTDRV
\par }
\par {\fs22
TESTDRV assumes that MSCDEX and the appropriate device driver are installed. During initialization, TESTDRV reads the driver profile from the file TESTDRV.PRO which assigns the device status defaults for the test. The following example shows a typical T
ESTDRV.PRO file:
\par \tab
\par }\pard \tx720\tx2520\tx4230 {\f4 \tab ; This is a sample TESTDRV.PRO
\par \tab ; Comments start with ';' and continue to the newline
\par \tab DriverName\tab = MSCD000\tab ; The driver to test (specified as
\par \tab \tab \tab ; argument to the .SYS
\par \tab \tab \tab ; command line
\par \tab WriteDevice\tab = f\tab ; This device is not writable
\par \tab Redbook\tab = t\tab ; This device supports Redbook
\par \tab \tab \tab ; Addressing
\par \tab RawMode\tab = t\tab ; This device supports raw mode data
\par \tab Prefetch\tab = t\tab ; This device supports prefetching
\par \tab AudioControl\tab = t\tab ; This device supports audio channel
\par \tab \tab \tab ; manipulation
\par \tab Audio\tab = t\tab ; This device supports audio/video
\par \tab \tab \tab ; information
\par \tab AudioChannels\tab = 2\tab ; Number of supported audio channels
\par \tab Interleave\tab = f\tab ; This device does not support
\par \tab \tab \tab ; Interleave mode
\par \tab InterleaveSize\tab = 0\tab ; Interleave size (may range between
\par \tab \tab \tab ; 0-255)
\par \tab InterleaveSkip\tab = 0\tab ; Interleave skip (may range between
\par \tab \tab \tab ; 0-255)
\par \tab Eject\tab = t\tab ; This device supports software
\par \tab \tab \tab ; eject requests
\par \tab UPC\tab = t\tab ; This device implements UPC code
\par \tab \tab \tab ; reading
\par \tab Output\tab = HEXDUMP.TXT\tab ; Output hex dumps to this file.
\par \tab \tab \tab ; Blank assignment sends output to
\par \tab \tab \tab ; stdout
\par \tab RedReadSectors\tab = 3:8:3,8:2:4\tab ; List of sectors to read in ReadL
\par \tab \tab \tab ; tests (red book form)
\par \tab HSGReadSectors\tab = 0024180c,00ff3421 ; List of sectors to read
\par \tab \tab \tab ; in ReadL tests (HSG form) hex only
\par
\par \tab ;
\par }\pard {\fs22
\par If the profile variables are not set in the TESTDRV.PRO file, they will default to the values shown above (except for the sector selections).
\par
\par }{\plain \b \page Running TESTDRV
\par }{\fs22
\par To run the test simply install your device driver, initiate MSCDEX, and execute TESTDRV.EXE. The default operation of TESTDRV can be modified through command line flags and arguments. Either a hyphen (-) or a forward slash (/) denotes the flags. The follo
wing command line flags and arguments are available:
\par
\par }\pard \tx720\tx1980\tx2160 {\fs22 \tab filename\tab - Alternate driver profile. (default: TESTDRV.PRO)
\par \tab /A\tab - Attended operation, qualifying interactive tests. (default:
\par \tab \tab unattended operation)
\par \tab /I\tab - Override disk recognition on control disk, (that is, behave as if
\par \tab \tab the disk is unknown even if it is a member of the Test Set).
\par \tab \tab (default: if recognized, several data matching tests are qualified).
\par \tab /T\tab - Terse output, no hex dumps and fewer diagnostic messages.
\par \tab /[#]\tab - Where # is a digit between 0 and 7, the drive number.
\par
\par }\pard {\fs22 In unattended (default) mode, all tests will be verified by both successful completion, given an acceptable request, and successful error recovery, given an unacceptable request. The output has the following format:
\par
\par }\pard \qc {\fs22 [Command Code.Subcommand Code] [Status] [Command[:Subcommand]]:[Test Comment]
\par }\pard {\fs22
\par For example, the test for the location of the driver head may return:
\par
\par }{\f4 \tab 3.1 TESTING IOCTLI:LocHead: Value Corresponds to Q-channel \tab \tab Information.
\par }\pard \tx90 {\f4
\par }\pard {\f4 \tab 3.1 ERROR IOCTLI:LocHead: Value Does not Correspond to
\par \tab \tab Q-channel Information.
\par \tab \tab LocHead returns \tab 1:23:60 [Redbook]
\par \tab \tab Q-channel returns \tab 2:30:45 [Redbook]
\par }{\fs22
\par Commands that return sector data or device dependent data will dump output in hexadecimal. If the disk is a recognized test disk and recognition is turned on (default), sector data will be compared to correct values and only the status returned.
\par
\par }{\plain \b Attended and Unattended Operation
\par
\par }{\fs22 Several calls to the driver cause or report physical changes in the drive unit or require that audio disk information be played through audio channels like conventional audio CD players. These states should be confirmed by an operator. A serie
s of YES/NO queries and simple directions allow the operator to quickly step through these tests. In order to allow for operator-free testing, a set of alternate best-guess tests can be executed instead of the ones that require confirmation. Attended te
sting is a super-set of unattended testing and should be considered the most complete run of the test program. For example, the following sequence occurs in the attended mode:
\par
\par }{\f4 \tab 132 TESTING PlayReq: Can you hear music playing? [Yn]_
\par \tab \tab \{ ..music plays and tester responds 'Y'.. \}
\par \tab 132 TESTING PlayReq: Request Completed Successfully.
\par }\pard \tx720\tx1980\tx2160 {\f4
\par }\pard {\plain \b \page Control Disk Verification
\par }{\fs22
\par The test for verifying read data requires the Microsoft Bookshelf and Microsoft Programmer's Library to be used as control disks. The test procedure reads data from the control disks then compares both raw and cooked da
ta for correspondence with archived data. If the test is run without the control disks, the data read is dumped in hexadecimal and ASCII format to the specified output.
\par
\par }\pard \tx720\tx1980\tx2160 {\plain \b Nonstandard CD-ROM Features
\par }{\fs22
\par }\pard {\fs22
Several driver commands derive their results or actions from hardware dependent features of the driver. Since not all drivers can be supported in a general release, special features of a device driver may not be adequately tested. (For example, write co
mmands apply to few CD-ROM drives and are only minimally supported by error recovery tests.) If the hardware dependent CD-ROM device driver document describes the r
esults of a driver request as undefined, the request will be tested for simple completion and error recovery. Requests that return data will dump the data to the selected output in hexadecimal and readable ASCII format.
\par }}