

	      User Diagnostics Manual (USERDIAG.TXT)

		   V 1.1.0            7/28/93

			 Digiboard, Inc.


			Table Of Contents

1.0  Scope

2.0  Applicable Documents

3.0  Memory Map Utility (DIGIMMAP.EXE)

	3.1  General Description

		3.1.1  Display Conventions
		3.1.2  Keyboard Conventions

	3.2  Functional Description

		3.2.1  BIOS Scan
		3.2.2  RAM Scan
		3.2.3  User Interface

	3.3  Product Limitations


4.0  User Diagnostic Utility (DIGIDIAG.EXE)

	4.1  General Description

		4.1.1  Display Conventions
		4.1.2  Keyboard Conventions
		4.1.3  Supported Product Families For The User Diagnostic's 

	4.2  Functional Description

		4.2.1  General Information Screen
		4.2.2  Main Menu Screen
		4.2.3  Main Help Screen
		4.2.4  System Error Messages

	4.3  PC/Xe Board, PC/Xi Board, and 2Port Board Product Family

		4.3.1  General Information
		4.3.2  Help Screens
		4.3.3  Basic Test Descriptions
		4.3.4  Error Messages

	4.4  MC/Xi Board Product Family

		4.4.1  General Information
		4.4.2  Help Screens
		4.4.3  Basic Test Descriptions
		4.4.4  Error Messages

	4.5  C/X Host Adapter Product Family

		4.5.1  General Information
		4.5.2  Help Screens
		4.5.3  Basic Test Descriptions
		4.5.4  Error Messages



1.0	Scope

	This document contains information related to the User Diagnostics
	package.  All files for this package are contained on the floppy disk,
	and include this document, two executable programs, and release notes.
	This document explains the memory map utility (DIGIMMAP.EXE) and the 
	user diagnostics (DIGIDIAG.EXE).


2.0	Applicable Documents

	PC/Xe (old) Board Installation Guide			DBI  90028600
	PC/Xe (new) Board, PC/Xi board Installation Guide	DBI  90026700
	2Port Board Installation Guide				DBI  90028300
	MC/Xi Board Installation Guide				DBI  90026600
	C/X Host Adapter Installation Guide			DBI  90027700


3.0	Memory Map Utility (DIGIMMAP.EXE)

3.1  	General Description

	The memory map utility is an MS-DOS based executable program that is
 	designed to aid in the installation of DigiBoard hardware by detailing
	locations in memory that are available for the DigiBoard product.

3.1.1  	Display Conventions

	When the memory map utility is executed, a main screen will appear.
	From the main screen, the operator may select a 'help' screen,
	execute the utility, or return to the operating system.

	The upper portion of the screen displays the current version of the
	utility and copyright information.  The middle of the screen displays
	data for operator's current selection.  The lower portion of the
	screen is used for the operator interface.

3.1.2  	Keyboard Conventions

	Three keyboard entries are used by the memory map utility.  <E> is
	used to execute the utility, <F1> displays the 'help' screen, and
	<Esc> is used to return to the operating system.  The utility uses
	the bottom of the screen to prompt the operator for keyboard inputs.

3.2	Functional Description

	DIGIMMAP attempts to locate hardware in the upper 384K of the first
	megabyte of memory of an IBM PC or compatible.  The memory range 
	checked is from A0000H to FFFFFH.  Typical devices in this area may 
	include video ROMs, system ROMs, hard disk adapters, and network
	adapters.  DIGIMMAP performs a ROM scan and a RAM scan to locate 
	hardware residing in upper memory.	

3.2.1	BIOS Scan

	This portion of the utility searches from C0000H to EFFFFH in 2K
	increments by checking the first two bytes of the region for a BIOS
	signature of 55AAH.  If a ROM signature is found, the third byte
	indicates the number of 512 byte sections and the appropriate area
	is marked as unavailable.

3.2.2	RAM Scan

	This is a scan of the memory regions which were unused accoding to
	the previous test.  The RAM scan also breaks memory down into 2K
	sections.  If the section is writable the section is marked as RAM
	as is unavailable for the DigiBoard product.  If it is not writable, 
	another type of ROM check is done, followed by either marking the 
	area as ROM, or available for DigiBoard product installation.  ROMs 
	found in the F0000H to FFFFFH area are considered System ROMs.

3.2.3	User Interface

	The following steps are suggested to run this utility.  

	1.  Boot the system normally.  This brings up the system in its
	    normal configuration.  This should cause the RAM on any adapters
	    to be ON.  If the memory is switched OFF,  DIGIMMAP may not 
	    locate it.

	2.  Place a clean (NO TSR's and NO memory managers) boot floppy in
	    drive A.  Press Ctrl-Alt-Del to reboot the system.  DO NOT use
	    use a hardware reset to reboot as this will typically reset any 
	    adapters in the system.

	3.  Place the utility disk in drive A, and enter DIGIMMAP
	    at the system prompt.

	4.  The main menu will be displayed.

		The following warning messages are displayed.

		Memory managers, used to load drivers and TSRs into the
		DOS high memory area, may cause DIGIMMAP to display incorrect
		results.

		DO NOT run DIGIMMAP under Windows.  Windows uses the high
		memory region, which may cause DIGIMMAP to display incorrect
		results.

		DIGIMMAP does writes to high memory.  This may cause the
		system to lock up.  Do not be alarmed, just reboot the system.

	5.  Pressing <E> from the main menu display will begin the high memory
	    search.  This is a four part process.  First it scans from C0000H
 	    to C7FFFH for video ROMs, then scans C8000H to DFFFFH for general 
	    ROMs, then scans E0000H to EFFFFH for expansion ROMs.  The last 
	    part scans memory from A0000H to FFFFFH for RAM and other ROMs.
	    For this check, a memory write is done to memory locations.

	Messages will appear at the bottom of the screen as the utility goes
	through the four checks.  When these are complete, two maps will be
	displayed.  The list on the left will sequentially display the results
	and the map on the right will display a grid map of the same results.

	These results are an educated guess of the areas in high memory that 
	could be used to install the DigiBoard product.  Make note of the 
	area(s) that are large enough to accomodate the product's memory 
	requirements.

3.3	Product Limitations

	If an adapter has RAM mapped to the high memory area but it only gets
	activated (mapped) upon instruction from the driver (like some
	DigiBoard products) and if this instruction has not been given,
	the adapter may go undetected.

	Any extended memory manager will cause DIGIMMAP to deliver false data.
	Since the memory manager is utilizing the upper memory area itself,
	DIGIMMAP will confuse this usage with hardware RAM areas.  In some
	cases a memory manager will install itself like a BIOS.  That is to
	say, it will contain a 55AAH signature in the first two bytes of its
	driver.

	If a driver loads itself high, DIGIMMAP will have the same difficulties
	with the driver as it has with the extended memory managers.  The
	general rule is to keep the software out of high memory when DIGIMMAP
	is executing.

	DIGIMMAP will try to write to the first byte of each 2K block of 
	memory that is found not to contain ROM.  This could have adverse
	effects on the system if the adapter interprets it as an instruction.
	This is unlikely, but possible.


4.0  User Diagnostic Utility (DIGIDIAG.EXE)

4.1  General Description

	The user diagnostic utility is an MS-DOS based executable program that
 	is designed to aid in the installation and troubleshooting of 
	DigiBoard hardware by performing a series of tests on the board.

4.1.1  Display Conventions

	When the user diagnostic utility is executed, a general information 
	screen is displayed followed by the main screen.  From the main 
	screen, the operator may select a 'help' screen, execute the utility, 
	or return to the operating system.

	There are four sections to the display.  The upper section of the 
	screen displays the current version of the utility and copyright 
	information.  The next section is the parameter selection section.
	The next section displays test results when the diagnostic is 
	executing.  The lower portion of the screen is used for the operator 
	interface.

4.1.2  Keyboard Conventions

	There are multiple keyboard entries for the user diagnostic utility.
	Board parameters have unique keyboard entries.  When all parameters 
	have been entered, press <E> to execute the utility.  Pressing <F1> 
	displays various help screens.  <Esc> is used to return to the 
	operating system.  The utility uses the bottom of the screen to 
	prompt the operator for keyboard inputs.

4.1.3  Supported Product Families For The User Diagnostic's 

	The current release of the user diagnostic supports the PC/Xe boards,
 	PC/Xi boards, ISA 2Port boards, MC/Xi boards,and the C/X host adapter 
	boards.

4.2  Functional Description

	The user diagnostic is a program that will test a DigiBoard for system
	compatability and board reliability.  After all parameters have been
 	entered, the operator may execute the diagnostic.  A configuration
	file (DIGIDIAG.CFG) is written to disk when program execution begins.
	When the program is run again, the configuration information is read
	and displayed for the operator.  The operator can immediately run the
	diagnostics by pressing <E>, or reenter any parameters prior to running
	the diagnostics.

4.2.1  General Information Screen

	This screen gives the operator an overview of how to correctly 
	execute the user diagnostics.  Appropriate warning messages are 
	also displayed.	

4.2.2  Main Menu Screen

	Following the general information, the main screen appears.  This 
	program is designed to support multiple DigiBoard products.  The 
	operator must select a product family displayed at the bottom of the
	screen.

4.2.3  Main Help Screen

	Prior to selecting a product family, pressing <F1> will display a 
	product family information screen.	

4.2.4  System Error Messages

	One of the configuration items that is stored is the system bus type.
	This is either ISA/EISA or Micro Channel(MCA).  If the stored data does
	not match the bus the program has found, the following error message
	is displayed.

	ERROR!  Disk file & diagnostics have found a bus conflict.  ERROR!

	 Disk file reported MCA bus.  Diagnostic reported ISA bus.
				(or)
	 Disk file reported ISA bus.  Diagnostic reported MCA bus.

	 Suggest that the DIGIDIAG.CFG file be erased, then rerun diagnostics.

	When DIGIDIAG.CFG is erased the operator must enter new parameters
	and the new DIGIDIAG.CFG will be written upon execution.  Executing
	the diagnostic again on the same machine should result in no further
	bus conflicts.

4.3  PC/Xe Board, PC/Xi Board, 2Port Board Product Family

	This product family is an intelligent board with an 80186 CPU
	embedded on the board.  It communicates with the host via dual ported
	memory and interrupts.  It supports asynchronous communication with
	2, 4, 8, or 16 ports.

4.3.1  General Information

	The board's dual ported memory must either be 8K, 64K, or 128K.  The 
	diagnostic is run in upper memory below the 1 megabyte boundary.  
	Selecting a memory address range for the board may be assisted by
	the DIGIMMAP.EXE program, which is supplied with this package.

4.3.2  Help Screens

	There are two help screens associated with this product family.
	The first explains each of the parameter entries, and the second is
	a visual duplication of the switch settings for the boards.

4.3.3  Basic Test Descriptions

	There are three basic test areas for this product family.  There are 
	a number of subtests within each basic test, depending on the board 
	type.

	The first basic test is the host's memory test.  The diagnostic 
	writes/reads/compares data written to the board's dual ported memory.
	Various patterns of bytes/words are checked for the entire dual ported
	memory window.  Any failure is considered critical and the tests are
	terminated with error information displayed.  Failure could indicate 
	that a memory conflict exists.  The memory utility (DIGIMMAP.EXE) can 
	be used to find a possible alternative memory window.

	The second basic test begins communicating with the board via the
	selected host base address.  Code is downloaded to the board and a
	response is necessary to post the information.  Other tests include an
	IRQ test, window enable test (2Port), and window select test (2Port).
	Any failure is considered critical and the tests are terminated with 
	error information displayed.  

	The third basic test is the port test.  The parameters allow for a
	single port to be tested.  There are other parameters that are used
	in conjunction with the port test.  The diagnostic package includes an
	RS-232 loopback cable for testing.  The signals that are looped back
	on the supplied cable are TxD to RxD, DTR to DSR & DCD, and RTS to CTS
	& RING.  The PC/Xi has a RS-422 option and a loopback cable must be 
	assembled to perform the external test; the necessary loopback signals
 	are TxD to RxD and RTS to CTS.  The loopback parameter enables the 
	operator to test the port in the internal or external mode.  The 
	loopback cable must be installed for valid test results in the 
	external mode.  When external testing is done, both data and control 
	signals are tested.  In internal mode only data is tested.  Following
	the data tests an interrupt test is performed on the selected port.

	The Continuous parameter allows the option of continually running the 
	port test(s).  The Stop On First Error parameter allows the test to 
	stop when an error is detected.

	The loopback plug for the RJ-45 version consists of a 10-pin RJ-45
	plug wired as follows:
		Pin 3 connected to pins 1 & 8 (RTS to RI and CTS);
		Pin 5 connected to pin 6 (TxD to RxD);
		Pin 9 connected to pins 2 & 10 (DTR to DSR and DCD).

	The loopback plug for the DB-25 version consists of a female DB-25
	connector wired as follows:
		Pin 4 connected to pins 22 & 5 (RTS to RI and CTS);
		Pin 2 connected to pin 3 (TxD to RxD);
		Pin 20 connected to pins 6 & 8 (DTR to DSR and DCD).

	The loopback plug for the DB-9 version consists of a female DB-9
	connector wired as follows:
		Pin 7 connected to pins 9 & 8 (RTS to RI and CTS);
		Pin 3 connected to pin 2 (TxD to RxD);
		Pin 4 connected to pins 6 & 1 (DTR to DSR and DCD).

4.3.4  Error Messages

	There are two places where error messages may appear.  The first
	is at the bottom of the screen in the operator interface section.
	Error messages here relate to parameter entry.  These messages
	typically prompt the operator for another entry or request another
	parameter first.  All parameters must be entered before execution
	can begin.

	The second place error messages appear is is the test information 
	section.  These will be displayed in red with 'Test FAILED' followed 
	by a error message to identify the error.

	Memory Error.  If an error occurs during the host's dual ported 
	memory tests, a message will appear that displays the address 
	(segment:offset), expected/written value, and the read value.  The
	host displays the message as:
		Segment:offset = ????:????. Expected = ????. Read = ????.

	Board Reset Error.  If the memory tests were successful, the host
	attempts to reset the board.  If the board does not reset, the host
	displays:
		Hardware reset error.  Possible I/O port conflict.

	Board Load Error.  If the board resets, the host attempts to 
	communicate with the board by downloading a program (BIOS) and 
	waiting for a response.  If the board does not respond, the host 
	displays:
		BIOS load error.  Possible memory conflict.

	If the BIOS load is successfully, the host displays board information
	including board type, memory available, and ports available.  If
	there were any initialization errors, they will be displayed as:
		Memory errors.
		Port(s) missing.
		Port(s) error.

	IRQ Error.  If an IRQ was selected and an error occurred, a message
	will indicate that the diagnostic did not receive an IRQ from the
	board.  The 2Port board has two additional errors: interrupt 
	acknowledge error, and interrupt pending error.  The host will 
	display the following error message(s):
		The diagnostic did not receive an IRQ.
		Interrupt acknowledge error.
		Interrupt pending error.

	Window Enable Error.  This test is only performed on the 2Port board.
	One or both of the memory enable bits was found to be in error.  The
 	host displays the following message:
		One or both of the memory enable bits are faulty.

	Window Select Error.  This test is only performed on the 2Port board
 	with the 8K window size selected.  An error message with the window 
	(1-8) that failed will be displayed.  A base window select error is 
	also possible.  The displays host the following message(s):
		Window ? select error.
		Base window select error.
		8K windowing feature is faulty.

	Port Errors.  The first error that could appear is that the port
	number selected is outside the range of ports supported by this
	board.  The maximum port number supported by the board is determined
	when BIOS code is downloaded and executed on the board.  The test will
	terminate at this point and display:
		The selected port number is invalid for this board.

	The host sends a command to the board to intitiate the port test.  If
	no response to the command is received, the following message is
	displayed:
		Board communication error during test setup.
		
	If the command is successful, the board begins testing the port.  The
	host has a timeout that requires the board to finish the test in a 
	certain amount of time.  If the host's timeout expires, the following
	message is displayed:
		Port ?? failed.  Test timeout occurred.

	For either the internal or external data test the received data is
	compared to the transmitted data.  If the they do not compare, the
	following message is displayed:
		Port ?? failed.  RX data did not compare with TX data.

	There is a timeout on the board for the transmission and reception of
	data.  If the board's timeout expires, the following message is
	displayed:
		Port ?? failed.  Port timeout occurred during TX/RX of data.

	The control signals are only tested when the loopback connector is
	installed.  Depending on the control signal failure, one of the
	following messages is displayed:
		Port ?? failed.  DCD input signal failed.		
		Port ?? failed.  DSR input signal failed.
		Port ?? failed.  CTS input signal failed.
		Port ?? failed.  RING input signal failed.
		Port ?? failed.  DCD & DSR failed.  Possible DTR failure.
		Port ?? failed.  CTS & RING failed.  Possible RTS failure.
		Port ?? failed.  DCD/DSR/CTS/RING failed.  Port failure.
		Port ?? failed.  General port failure.

	There is a timeout on the board for the completion of the test.
 	If the board's timeout expires, the following message is displayed:
		Port ?? failed.  Test timeout occurred.

	The port interrupt test checks the ability of the selected port to
	generate an interrupt to the CPU on the board.  This is done by
	traansmitting 1 byte of data in internal loopback mode.  If an error 
	occurs, one of the following message is displayed:
		Port ?? failed.  Port interrupt did not occur.
		Port ?? failed.  RX data did not compare with TX data.
		Port ?? failed.  Port timeout occurred during TX/RX of data.

4.4  MC/Xi Board Product Family

	These are intelligent boards with an 80186 CPU embedded on the board.
  	They communicate with the host via dual ported memory and interrupts.
  	They support asynchronous communication with 4, 8, or 16 ports.

4.4.1  General Information

	The board's dual ported memory is 32K.  The diagnostic is run in 
	upper memory below the 1 megabyte boundary.  Selecting a memory 
	address range for the board may be assisted by the DIGIMMAP.EXE 
	program, which is supplied with this package.  When the board is
	installed with the POS program, these values will be used for the
	user diagnostics.

4.4.2  Help Screens

	There is a help screen associated with this product family. It 
	explains each of the parameter entries.

4.4.3  Basic Test Descriptions

	There are three basic test areas for this product family.  There are 
	a number of subtests within each basic test.

	The first basic test is the host's memory test.  The diagnostic 
	writes/reads/compares data written to the board's dual ported memory.
	Various patterns of bytes/words are checked throughout the entire 
	dual ported memory window.  Any failure is considered critical and 
	the tests are terminated with error information displayed.  Failure 
	could indicate that a memory conflict exists.  The memory utility
 	(DIGIMMAP.EXE) can be used to find a possible alternative memory 
	window.

	The second basic test begins communicating with the board via the
	selected host base address.  The board is released from reset and the
	code in the EPROMs is executed and a response is necessary to post 
	the information.  Other tests include an IRQ test and window select 
	test.  Any failure is considered critical and the tests are terminated
 	with error information displayed.  

	The third basic test is the port test.  The parameters allow for a
	single port to be tested.  There are other parameters that are used
	in conjunction with the port test.  The diagnostic package includes an
	RS-232 loopback cable for testing.  The signals that are looped back
	on the supplied cable are TxD to RxD, DTR to DSR & DCD, and RTS to CTS
	& RING.  The PC/Xi board has an RS-422 option and a loopback cable 
	must be assembled to perform the external test; the necessary loopback
 	signals are TxD to RxD and RTS to CTS.  The loopback parameter enables
 	the operator to test the port in the internal or external mode.  The
	loopback cable must be installed for valid test results in the 
	external mode.  When external testing is done, both data and control 
	signals are tested.  In internal mode only data is tested.  Following
	the data tests an interrupt test is performed on the selected port.

	The Continuous parameter allows the option of continually running the 
	port test(s).  The Stop On First Error parameter causes the test to 
	stop when an error is detected.

	The loopback plug for the RJ-45 version consists of a 10-pin RJ-45
	plug wired as follows:
		Pin 3 connected to pins 1 & 8 (RTS to RI and CTS);
		Pin 5 connected to pin 6 (TxD to RxD);
		Pin 9 connected to pins 2 & 10 (DTR to DSR and DCD).

	The loopback plug for the DB-25 version consists of a female DB-25
	connector wired as follows:
		Pin 4 connected to pins 22 & 5 (RTS to RI and CTS);
		Pin 2 connected to pin 3 (TxD to RxD);
		Pin 20 connected to pins 6 & 8 (DTR to DSR and DCD).

4.4.4  Error Messages

	There are two places where error messages may appear.  The first
	is at the bottom of the screen in the operator interface section.
	Error messages here relate to parameter entry.  These messages
	typically prompt the operator for another entry or request another
	parameter first.  All parameters must be entered before execution
	can begin.

	The second place error messages appear is is the test information 
	section.  These will be displayed in red with 'Test FAILED' followed 
	by a message to identify the error.

	Memory Error.  If an error occurs during the host's dual ported 
	memory tests, a message will appear that displays the address 
	(segment:offset), expected/written value, and the read value.  The
	host displays the message as:
		Segment:offset = ????:????. Expected = ????. Read = ????.

	Board Reset Error.  If the memory tests were successful, the host
	attempts to reset the board.  If the board does not reset, the host
	displays:
		Hardware reset error. Possible board I/O port address conflict.

	Board Load Error.  If the board resets, the host attempts to 
	communicate with the board by downloading a program (BIOS) and 
	waiting for a response.  If the board does not respond, the host 
	displays:
		BIOS start error.  Possible memory conflict.

	If the BIOS load is successful, the host displays board information
	including board type, memory available, and ports available.  If
	there were any initialization errors they will be displayed as:
		Memory errors.

	IRQ Error.  If an IRQ was selected and an error occurred, a message
	will indicate that the diagnostic did not receive an IRQ from the
	board.  The host will display the following error message:
		The diagnostic did not receive an IRQ.

	Window Select Error.  An error message with the window (1-8) that 
	failed will be displayed.  A base window select error is also 
	possible.  The host displays the following message(s):
		Window ? select error.
		Base window select error.
		32K windowing feature is faulty.

	Port Errors.  The first error that could appear is that the port
	number selected is outside the range of ports supported by this
	board.  The maximum port number supported by the board is determined
	when BIOS code is downloaded and executed on the board.  The test will
	terminate at this point and display:
		The selected port number is invalid for this board.

	The host sends a command to the board to intitiate the port test.  If
	no response to the command is received, the following message is
	displayed:
		Board communication error during test setup.
		
	If the command is successful, the board begins testing the port.  The
	host has a timeout that requires the board to finish the test in a 
	certain amount of time.  If the host's timeout, expires the following
	message is displayed:
		Port ?? failed.  Test timeout occurred.

	For either the internal or external data test the received data is
	compared to the transmitted data.  If the they do not compare, the
	following message is displayed:
		Port ?? failed.  RX data did not compare with TX data.

	There is a timeout on the board for the transmission and reception of
	data.  If the board's timeout expires, the following message is
	displayed:
		Port ?? failed.  Port timeout occurred during TX/RX of data.

	The control signals are only tested when the loopback connector is
	installed.  Depending on the control signal failure, one of the
	following messages is displayed:
		Port ?? failed.  DCD input signal failed.		
		Port ?? failed.  DSR input signal failed.
		Port ?? failed.  CTS input signal failed.
		Port ?? failed.  RING input signal failed.
		Port ?? failed.  DCD & DSR failed.  Possible DTR failure.
		Port ?? failed.  CTS & RING failed.  Possible RTS failure.
		Port ?? failed.  DCD/DSR/CTS/RING failed.  Port failure.
		Port ?? failed.  General port failure.

	There is a timeout on the board for the completion of the test.
 	If the board's timeout expires, the following message is displayed:
		Port ?? failed.  Test timeout occurred.

	The port interrupt test checks the ability of the selected port to
	generate an interrupt to the CPU on the board.  This is done by
	transmitting 1 byte of data in internal loopback mode.  If an error 
	occurs, one of the following messages is displayed:
		Port ?? failed.  Port interrupt did not occur.
		Port ?? failed.  RX data did not compare with TX data.
		Port ?? failed.  Port timeout occurred during TX/RX of data.


4.5  C/X Host Adpater Product Family

	These are intelligent adapters with an 80186 CPU embedded on the board.
  	They communicate with the host via dual ported memory and interrupts.
  	They support synchronous or asynchronous communication with 2 ports.
	There are six adapters testable with the user diagnostics.  The 
	three earlier version adapters (ISA/EISA/MCA) are RS-422 only.  The
	more recent adapters can select RS-232.  Fault isolation relays are 
	also present in the newer adapters.

4.5.1  General Information

	The adapter's dual ported memory is 32K.  The diagnostic is run in 
	upper memory below the 1 megabyte boundary.  Selecting a memory 
	address range for the adapter may be assisted by the DIGIMMAP.EXE 
	program, which is supplied with this package.  When the adapter is
	installed with the POS program, these values will be used for the
	user diagnostics.

4.5.2  Help Screens

	There are two help screens associated with this product family.
	The first explains each of the parameter entries, and the second is
	a visual duplication of the switch settings for the ISA host adapters.

4.5.3  Basic Test Descriptions

	There are three basic test areas for this product family.  There are 
	a number of subtests within each basic test.

	The first basic test is the host's memory test.  The diagnostic 
	writes/reads/compares data written to the adapter's dual ported memory.
	Various patterns of bytes/words are checked for the entire dual ported
	memory window.  Any failure is considered critical and the tests are
	terminated with error information displayed.  Failure could indicate 
	that a memory conflict exists.  The memory utility (DIGIMMAP.EXE) can 
	be used to find a possible alternative memory window.

	The second basic test begins communicating with the adapter via the
	selected host base address.  Code is downloaded to the adapter and a
	response is necessary to post the information.  Other tests include an
	IRQ test, and window select test.  Any failure is considered critical 
	and the tests are terminated with error information displayed.  

	The third basic test is the port test.  The parameters allow for a
	single port to be tested.  There are other parameters that are used
	in conjunction with the port test.  The terminator plug (part number
	60000388) supplied with the adapter can be used for external loopback
 	testing.  The loopback parameter enables the operator to test the 
	port in the internal or external mode.  The terminator cable must be
 	installed for valid test results in the external mode.

 	The earlier adapters use only RS-422 and the newer adapters have 
	RS-232 selectability.  The newer adapters also have fault isolation 
	relays.  When external loopback is selected on the newer adapters, 
	clicking can be heard due to the testing of the relays.  Data is
	transmitted at 1.2 MB for RS-422 and 57.6 KB for RS-232.

	The Continuous parameter allows the option of continually running the 
	port test(s).  The Stop On First Error parameter allows the test to 
	stop when an error is detected.

	The terminator plug consists of a male HD-15 connector wired as 
	follows:
		Pin 1 to pin 6;
		Pin 2 to pin 7;
		Pin 3 to pin 15;
		Pin 4 to pin 9;
		Pin 5 to pin 10;
		Pin 8 to pin 14;

4.5.4  Error Messages

	There are two places where error messages may appear.  The first
	is at the bottom of the screen in the operator interface section.
	Error messages here relate to parameter entry.  These messages
	typically prompt the operator for another entry or request another
	parameter first.  All parameters must be entered before execution
	can begin.

	The second place error messages appear is is the test information 
	section.  These will be displayed in red with 'Test FAILED' followed 
	by a error message to identify the error.

	Memory Error.  If an error occurs during the host's dual ported 
	memory tests, a message will appear that displays the address 
	(segment:offset), expected/written value, and the read value.  The
	host displays the message as:
		Segment:offset = ????:????. Expected = ????. Read = ????.

	Adapter Reset Error.  If the memory tests were successful, the host
	attempts to reset the adapter.  If the adapter does not reset, the host
	displays:
		Hardware reset error. Possible board I/O port address conflict.

	Adapter Load Error.  If the adapter resets, the host attempts to 
	communicate with the adapter by downloading a program (BIOS) and 
	waiting for a response.  If the adapter does not respond, the host 
	displays:
		BIOS load error.  Possible memory conflict.

	If the BIOS load is successful, the host displays adapter information
	including adapter type, memory available, and ports available.  If
	there were any initialization errors they will be displayed as:
		Memory errors.
		Port(s) missing.
		DMA errors.

	Window Select Error.  The number of windows is either 4 or 16 
	depending on the amount of memory on the adapter (128K or 512K).
	An error message with the window that failed will be displayed.  
	A base window select error is also possible.  The host displays the
	following message(s):
		Window ? select error.
		Base window select error.
		32K windowing feature is faulty.

	Fuse Test Error.  The new host adapters have an auxillary 5 volt 
	supply that is fused.  The condition of these fuses can be tested.  
	If one or both of the fuses are open the following messsage is 
	displayed:
		One or both of the Auxillary 5 volt fuses are open.

	IRQ Error.  If an IRQ was selected and an error occurred, a message
	will indicate that the diagnostic did not receive an IRQ from the
	adapter.  The host will display the following error message:
		The diagnostic did not receive an IRQ.

	The host sends a command to the adapter to intitiate the port test.  If
	no response to the command is received, the following message is
	displayed:
		Board communication error during test setup.
		
	If the command is successful, the adapter begins testing the port.  The
	host has a timeout that requires the adapter to finish the test in a 
	certain amount of time.  If the host's timeout expires, the following
	message is displayed:
		Port ?? failed.  Test timeout occurred.

	For either the internal or external data test the received data is
	compared to the transmitted data.  If the they do not compare, the
	following message is displayed:
		Port ?? failed.  RX data did not compare with TX data.

	There is a timeout on the adapter for the transmission and reception of
	data.  If the adapter's timeout expires, the following message is
	displayed:
		Port ?? failed.  Port timeout occurred during TX/RX of data.

