DsVerify - DStreams API Test Suite

Author:  Michael Zarns
Date:    5/20/97

This application performs roughly 100 tests on a DStreams 
Provider driver.  The tests are intended to verify the
driver's implementation and handling of the DStreams API.

This application accepts one commandline option, the device
name to be tested, i.e. digisxb2.  Example:

	dsverify digisxb2

The tests were chosen to exercise error and boundary 
conditions of the API, such as sending a PutMsg on a closed 
stream, or a GetMsg with NULL buffer pointers.  Why?  
Because these are some very likely causes of bugchecks
(bluescreens) from the driver, and they're easy to protect
against - just make sure the drivers passes all tests in 
this application.  In all cases, the requests are expected 
to either succeed or fail gracefully.

An output file is written, DsVerify.log, into the current
working directory, allowing you to review the pass/fail 
status of the various tests.  Progress is written to disk
between every test, so if the DStreams driver bugchecks, 
you can review the logfile to determine exactly which test 
caused the failure.

