This directory contains the MS Protocol Manager related files. The
following is a brief introduction to each of these modules, and
their purpose in OS/2 networking. These modules adhere to
Microsoft's : "Network Driver Interface Specification", Version 1.0.1,
(referred to as NDI).

NETBIND.EXE :
	Binds the MS NDI compatible protocols and MAC drivers. 
	This utility should be run at least once after the 
	system boots. Failing to do so would result into 
	inoperational Networking Software.

PRO.MSG	& PROH.MSG :
	MS Protocol-Manager Error Message file, a copy should be
	located in C:\. When an error occures at NETBIND time, you
	may simply type : 

		[C:\] help <error-number> 

	It would display on-line help related to Protocol Manager
	or Netbind problems.

PROTMAN.OS2 :
	This is the MS Protocol-Manager software. It should be the
	first device-driver in a sequence of MS NDI compatible 
	drivers in C:\CONFIG.SYS file.

PROTOCOL.INI :
	The "protocol.ini" file stores configuration and binding 
	information for all the NDI compatible protocol and MAC 
	software modules.

	The file consists of a series of named sections, where
	the section-name is represented in square-brackets 
	(i.e., [seciton-name]).

	Each section extends until another section-name is 
	encountered or end-of-file is encountered. Each line 
	in a configuration section is an expression :
		<config-parameter> = <configuration-value>

	EXAMPLE :

	;----------- Start of PROTOCOL.INI File -----------------

	[SECTION_A]
	; All comments start with a SEMICOLON in COLUMN-ONE of each
	; line. (NOTE : If a semicolon is not in first-column, then 
	; that line is not treated as a comments-line.)

	; All blank-lines are ignored. All configuration-paramters
	; are Upper- or Lower-case insensitive. 

	; "DriverName" is a reserved keyword used to provide
	; Protocol Manager with the name of OS/2 device of this
	; module.
		DriverName	 = SECT_A$

	; "Bindings" is a reserved keyword used to provide
	; Protocol Manager with the name of the NDI modules
	; this module wishes to communicate after system-startup.
		Bindings	 = SECTION_B

	; A decimal configuration-value is provide as a number 
	; starting with 0 ... 9 and optionally preceeded by + or -
		Section_a_param1 = 1000

	; A string configuration-value is provided as a sequence 
	; of alpha-numeric characters enclosed in double-quotes.
		Section_a_param2 = "This is a string"

	; A hexa-decimal configuration-value is provided as a
	; sequence of hexa-decimal digits (0...9, A...F) preceeded
	; by a 0x. (This is the notation used in 'C' programming
	; Language to represent hexa-decimal numbers).
		Section_a_param3 = 0xFF

	; A set of configuration-values can be provided to an array
	; parameter by separating values with spaces, tabs or comma.
		Section_a_param4 = 10, 20, 30, 40

	[SECTION_B]
		DriverName	 = SECT_A$
		Section_b_param1 = 1000
		Section_b_param2 = "This is a string"
		Section_b_param3 = 0xFF
		Section_b_param4 = 10, 20, 30, 40
		Section_b_param5 = -600

	;------------ End of PROTOCOL.INI File ------------------

PROTCHK.EXE :
	This utility enables you to verify the syntax of the 
	protocol.ini file. To check the status of the 
	protocol.ini file, enter the following :

		[C:] protchk /i:\xln\protman

	Note that the command-line option /i: is followed by 
	the path-name of the directory where the protocol.ini 
	file is located.