Metropoli BBS
VIEWER: dgudread.me MODE: TEXT (ASCII)

	This readme file provides instructions for using the DigiBoard OS/2
	Serial Port Test Utility, DGOS2UD.EXE. This utility tests any OS/2
	Serial Device supported by a Physical Device Driver.



	Hardware and Software Requirements -

		Asynchronous Serial Port product.
		OS/2 Device Driver for the product (loaded).
		DGOS2UD.EXE Utility program.
		Single port loopback connector wired as such :

			   Signals				DB-25 pins

			Rx  -> Tx				 2  -> 3
			DTR -> DSR, DCD          20 -> 6,8
			RTS -> CTS, RI           4  -> 5,22


	Test Preparation -

		To prepare for testing a serial port, ensure that the following
		criteria are met :

		- The hardware to be tested is properly installed.
		- The correct device driver has loaded successfully.
		- The loopback test connector is firmly installed on the port's
		  connector or cable.
		- The DGOS2UD.EXE utility is accessible from your hard disk of floppy
		  drive.


	DGOS2UD Execution -

	To start the utility, simply type DGOS2UD from any OS/2 Full Screen
	or Window. You will see a menu from which you can make the following
	choices :

			Select Port
			Short Test
			Continous Test
			Display Error Log
			Log File
			Exit

	Each of the choices are described below :

		Select Port -

		This selection permits you to specify the Serial Port to be tested
		by specifing the port's name. The default name is COM3 since you may
		very likely have the DigiBoard port's starting with this device name.
		If this is not the case, you may simply enter a different name.


		Short Test -

		Selecting this option starts testing the serial port by	running
		a series of tests that will terminate after one full pass. These
		tests check that all modem control outputs and inputs function
		properly. Data transmission and	reception is also test at different
		combinations of baud rates, data bits, stop bits, and parity bits.
		At each combination, 10 bytes are transmitted and checked for correct-
		ness after reception. Also, the port is tested at it's maximum baud
		rate with transmission of 10 kilobytes of data.


		The baud rates tested are as follows :

		110,150,300,600,1200,1800,2400,4800,9600,19200,38400,57600 and
		115200 with the following exceptions :

						  Product					Highest Baud Rate

			Non-Intelligent Serial Ports  (e.g COM2)      19200
			DigiBoard's PC/X Boards						  19200
			DigiBoard's COM/Xi Boards                     19200
			DigiBoard's C/X Concentrators                 57600

			The baud rates are limited due to product capabilities.


		Continuous Test -

		This test is just a continuous cycle of short test executions.
		When you select this option, you may choose wether the test will
		stop when an error is encountered or just continue testing until
		you manually stop it.


		Display Error Log -

		This selection allows you to view the record of errors for the
		test just executed. The error log records the following types of
		errors :

			Receive Errors - These errors indicate that not all the data
				was received.

			Transmit Errors - These errors indicate that not all the data
				was transmitted.

			Data Integrity Errors - These errors indicate that the received
				data was incorrect.

			Receive Overrun Errors - These errors indicate that the hardware
				lost receive data.

			Receive Queue Overrun Errors - These errors indicate that the
				driver did not have enough buffer space to store the
				received data.

			Parity Errors - These error indicate that the hardware detected
				a parity error on a received byte.

			Framing Errors - These error indicate that the hardware detected
				a framing error on a received byte.

			Modem Signal RTS/CTS Errors  &
			Modem Signal DTS/DSR Errors - These errors indicate a failure
				occured with the indicated modem control line pair.

		Log File -

		This option allows you to enable or disable the logging of data
		transmission errors to a disk file in your current directory. This
		error file has the name PORT#.ERR, where # is the com ports number
		(e.g. 2 for COM2). The errors are appended to the log file with a
		time/date stamp and a record of the erroneous data.


		Exit -

		Select this option to exit the utility.


	Error reporting -

		During the Short Test or the Continuous Test with Stop On Error
		selected, all errors will be presented to you in a red error message
		box with a description of the error and the test parameters. If you
		are running Continuous Test with no error stops, ann error indication
		will be posted at the bottom of the screen.


	Pass Indications -

		If your port has passed the diagnostic tests, there will be no
		errors reported in the Error Log and you may assume that the
		hardware and driver are functioning properly.

[ RETURN TO DIRECTORY ]