                   README File for NCR DOS and OS2 STARLAN 

INSTALLATION:

The instructions for installing an NCR StarLAN adapter in a PC are included
in the packing box with each adapter and cable.  

The board has only one jumper.  Since this is a test jumper for manufacturing 
only, no jumper changes should be necessary.  No hardware configuration is 
required for IRQ level, port addresses, etc.  (These options are selected
in PROTOCOL.INI.)


HUB CONNECTIONS:

To connect the StarLAN adapters together in a network, use the StarLAN cable
to attach each adapter to the StarLAN hub.  Connect each cable to one of the
hub jacks numbered 1-11.  Do not use the HO jack;  it is used for connecting
multiple hubs.  The hub power cable connector is on the side of the hub.

******************************************************************************
 
         DOS and OS2 NDIS StarLAN MAC Driver Loading Error Messages


SLN001: Invalid Keyword "data" found in PROTOCOL.INI

	You have changed or added an invalid keyword in the protocol.ini 
	file.  Remove the invalid keyword from the file.


SLN002: 

	This error is reserved for future use.


SLN003: DRIVERNAME Keyword not found in PROTOCOL.INI

	The keyword DRIVERNAME must appear in the protocol.ini file in 
	each module section.


SLN004: Drivername "data" was not found in PROTOCOL.INI 

	The drivername must be STARLAN$ in the protocol.ini file.


SLN005: Multiple occurrences of Keyword "data" found in PROTOCOL.INI

	There is more than one occurence of the keyword "data" in the 
	protocol.ini file.  Remove the extra occurences.


SLN006: Parameter on Keyword "data" is required to be an integer

	Integer parameters must start with a numeric digit and not be 
	enclosed in quotes.  Start with an 0x to express a hexadecimal 
	value, otherwise the value is interpreted to be decimal.


SLN007: Parameter on Keyword "data" is required to be a string

	String parameters must start with a non numeric character or must 
	be enclosed in quotes.


SLN008: Parameter "data" on Keyword "data" is invalid

	The integer value you entered for the keyword shown is an invalid 
	number for that keyword.


SLN009: Parameter "data" on Keyword "data" is invalid 

	The string you entered for the keyword shown is an invalid value.


SLN010: Invalid number of parameters on Keyword "data"

	You may have only one parameter for the keyword.  Remove the extra 
	parameter.


SLN011: GetProtocolInfo call failed

	The Protocol Manager did not load properly.  Verify that protman.dos 
	or protman.os2 is specified properly in config.sys and that the 
	referenced protocol.ini file exists.


SLN012: Error communicating with Protocol Manager

	The Protocol Manager did not load properly.  Verify that protman.dos 
	or protman.os2 is specified properly in config.sys and that the 
	referenced protocol.ini file exists.


SLN013: 

          This error is reserved for future use.


SLN014: Could not open Protocol Manager

	The Protocol Manager did not load properly.  Verify that protman.dos 
	or protman.os2 is specified properly in config.sys and that the 
	referenced protocol.ini file exists.


SLN015: Could not register with Protocol Manager

	The Protocol Manager did not load properly.  Verify that protman.dos 
	or protman.os2 is specified properly in config.sys and that the 
	referenced protocol.ini file exists.


SLN016: Error setting IRQ level

	The interrupt you chose for the board may be used by another driver. 
	Check parameters for this and previously loaded drivers.  You may 
	need to select a different value for the INTERRUPT keyword in 
	protocol.ini.  


SLN017: Out of dynamic memory 

	The amount of memory allocated for buffers was too large.  Decrease 
	the values of NUM_GENREQ, NUM_RCV_BUFS, SIZE_RCV_BUFS, and 
	NUM_XMT_BUFS in the protocol.ini file.

 
SLN018: Invalid node address read from LAN ID ROM at "data"

	Your adapter board either is not installed in the PC or it may be 
	defective.  Run the diagnostics program.


SLN019: Invalid DMA straps

	The values for keywords DMA_CHANNEL0 and DMA_CHANNEL1 in protocol.ini
	may be invalid.  Check protocol.ini to ensure that the values for 
	the two keywords are not equal.  If this message is displayed when 
	the default DMA channel values are used, then the board either is 
	not installed or may be defective.  Run the diagnostics program.


SLN020: Diagnostic Failed 

	Your board may be defective.  Run the diagnostics program.


SLN021: Initialization Failed: Timed out waiting for interrupt

	The interrupt you chose for the board may be used by another driver.  
	Check parameters for this and previously loaded drivers.  You may 
	need to select a different value for the INTERRUPT keyword in 
	protocol.ini.  If none of the valid interrupt values work, your 
	adapter board either may not be installed in the PC or it may be
	defective.  Run the diagnostics program.


SLN022: Warning: Keyword "data" in PROTOCOL.INI is ignored in the 7052

	You entered a keyword in protocol.ini which is ignored when running 
	on a 7052 or 7052D.  Use the 7052 Configuration Setup menu for 
	StarLAN to change this parameter.  This message should never occur 
	when the StarLAN card is installed on a PC.


SLN023: Could not get receive buffer

	The values entered for keywords NUM_RCV_BUFS and SIZE_RCV_BUFS in 
	protocol.ini may be invalid.
