THE TCP/IP STACK PROVIDED WITH 5PM TERM 3.x FOR WINDOWS
PART I
-----------------------------------------------------------

Our TCP/IP support software includes TCP/IP support for Windows
Sockets version 1.1.  

The Windows TCP/IP Support is implemented in Windows
drivers (DLLs) which are copied from the installation
diskette to the Windows directory. 
Please note that there is NO DNR with this stack.                 
-----------------------------------------------------------

BEFORE INSTALLING THE TCP/IP STACK USING THE 5PM
INSTALLER, PLEASE READ THE FOLLOWING.

-----------------------------------------------------------

	INSTALLING A NETWORK CARD ON YOUR PC
	------------------------------------

Install the network card in the PC as described in the
card manufacturer's manual.

Before starting the hardware installation, switch off the
PC and all connected peripherals and remove the power 
connector from the back.

-------- Testing the network card
¨   Most network cards are provided with test and/or
 diagnostic software. We strongly recommend that you test
 the card for correct functioning by following the
 manufacturer's recommended procedure before installing the
 TCP/IP stack.
¨   However, please do not install the card driver with
the installer provided by the card manufacturer - you
should use ASC’s installer to do this.  This comes with
5PM Term for Windows and you can choose 5PM Term, TCP/IP
Stack or Full Installation when running "install.exe" from
Windows.
¨    In order to carry out a functional test of the
network card, it needs to be connected to an existing
network, or the socket on the adapter should be correctly
terminated. For example, in the case of thin Ethernet,
termination should be done with a "T"-piece and two 50-½
terminating plugs.
¨   Do not go on to ASC’s installation if the test
software reports errors. A failure to observe this can
lead to data loss when using the network, or even damage
to the PC hardware.

-------- Hardware configuration
¨   Before installing the TCP/IP software, you must
 configure your network card with hardware settings which
 are consistent and not conflicting with other adapter
 cards in your PC.
¨   Card configuration options such as memory address is
 either done with jumpers on the card, or with the help of
 the manufacturer's setup program. In both cases you should
 refer to the manufacturer's manual for help.
¨   Typically, each expansion card in your PC is
 allocated a particular "shared memory" address range,
 "hardware interrupt" (IRQ, PC) and one or more "I/O
 addresses" to allow it to communicate with the CPU. In
 order to avoid conflicts between them, all installed cards
 must use different parameters. Whereas in the case of IBM
 PS/2 computers with a Micro-Channel bus, these parameters
 must be determined and configured by software.  This is
 unfortunately not possible with computers using the older
 ISA bus.


               	INSTALLING THE TCP/IP STACK
		---------------------------

¨   ASC’s installer  will take care of installing all the
 needed TCP/IP files for you from the install diskette to
 your hard disk.
¨   Before you start the installation however, please
check the following points and
make sure you note  the configuration of your network card:
	Hardware Interrupt     	(INT)  		 	_______
	I/O Base Address 	(PORT)                	_______
	Shared Memory Address 	(MEM)        		_______
	Memory Size		(MEMSIZE)		_______
	DMA						_______

	Localhost IP Address (Your machine’s address) 	_________________
	Any other information your ethernet card may need:

NOTE that some cards have no configuration parameters.

¨   The TCP/IP files will be installed in a subdirectory
 of your destination directory, so if you install on
 C:\5PM then all your TCP/IP files will be in C:\5PM\CONN.

¨   If errors occur during installation, you should abort
 the installation and start again from the beginning after
 solving the problem.

¨   The installer will  prompt you at the end for an
 addition to your autoexec.bat file. You can skip this by
 clicking Cancel.  If you click Modify in the dialog box,
 the following line will be added to the last line of your
 autoexec.bat:
     call C:\5PM\CONN\STARTNET

 STARTNET is a batch file which loads the files required
 by the ODI driver system. The following example of
 STARTNET.BAT sets the required directory, loads the link
 support layer, loads the link driver (ODI card driver)
 for an SMC Ethernet card, and calls the TCP/IP
 redirector PCS_ODI.:

     set PCSHARE=C:\5PM\CONN
     C:\5PM\CONN\LSL.COM
     C:\ 5PM\CONN \SMCPLUS.COM
     C:\ 5PM\CONN \PCS_ODI.EXE

 The above commands will start the TCP/IP stack
 automatically on booting the PC if you put the
 startnet.bat call into your autoexec.bat file.

¨   The ODI configuration file is called NET.CFG and it
 is modified each time you install.  Values are added to
 the end of the file so you can have more than one Link
 Driver section or whatever you desire.


		ODI NETWORK DRIVERS
		--------------------
ODI (Open Datalink Interface) is the specificaiton of
a standard software interface for low-level drivers
for network interface hardware, for example for 
Ethernet or Token-Ring network cards.

By splitting network drivers into two parts; one part
from the network hardware manufactureer called the
"link driver" (or DOS ODI LAN driver, sometimes
abbreviated to MLID for Multiple Link Interface Driver)
and another part from the software application developer 
which we will call the "protocol stack".  By defining
a standard software interface between the two, it is possible 
to relieve the software developer of the job of adapting
network drivers to a wide range of different types
of network cards.

The link driver interacts directly with the hardware.  
The protocol stack provides the communication between
the link driver and the software application through
a standard interface.  Our TCP/IP Stack combines the 
"client application" itself and the protocol stack into
a single program (PCS_ODI.EXE), which we will call the
TCP/IP re-director.  Novell currently uses two seperate
programs for this purpose (the ODI IPX protocol stack
is IPXODI.EXE and the client shell is NETX.COM).

ODI also offers the option of running more than one 
service (i.e. protocol type) on the same network
card simultaneously.  For example, under ODI, our
TCP/IP protocol and Novell's IPX protocol can run
on the same network card, although it is not 
possible to run the same protocol more than once 
on the same card.

Another driver-like program, the "link support layer"
(or ODI manager, LSL.COM) is used to control the 
communication between one or more protocol stacks (such
as our TCP/IP Stack and IPX) and one or more link drivers
(i.e. one or more network cards).

The link support layer, the link dirver(s) and the TCP/IP
re-director (our pcs_odi.exe) all access the same file (NET.CFG)
when loading.  This allows each one of the above to determine 
their configuration.  NET.CFG is a plain text file and should
normally be present in the same directory as the link driver(s).
NET.CFG is automatically created by the installer with the
correct parameters but you may need to edit it manually if 
you want to run our TCP/IP stack with another protocol.
All protocols must access the same NET.CFG file.

The loading order in the PC is significant!  You must first
load the link support layer (LSL.COM), then the link 
driver(s) (ex: NE2000.COM) and finally the protocol 
stack(s) (ex:pcs_odi.exe).  Then any other network protocols
like (odiipx.com and netx.com).

Our TCP/IP protocol can share the same network card with other
protocols like IPX, LAT, AppleTalk, etc.



		LIST OF ODI DRIVERS
		--------------------

Choose the correct driver for your card.  It will be
copied to your hard disk later when you save your
configuration parameters.
You can extend the list to support more card types if you
have a suitable ODI driver for each of them (see "Making
your own ODI drivers").  See the file drivers.lst for a 
complete list of ODI drivers supplied with this stack.
                   

		ODI LINK DRIVER CONFIGURATION DIALOGS
		-------------------------------------

Please note that when installing the TCP/IP stack, the
network card parameters that you see as the default values
in this dialog are not related in any way to the current
hardware configuration of your network card. Initially,
you will see the default driver parameters as shipped with
our installation diskette. The settings you make are stored
in a configuration file called net.cfg.

-------- Options for the configuration parameters
The available options in the configuration parameters
dialog are enabled or disabled according to the make and
type of the network card you are configuring. For example,
the "Thick or Thin Ethernet" option is only enabled for
network cards which are provided with these two types of
Ethernet connectors.  This information is found in the
cardname.ins file.


-------- Configuring the ODI link driver
For some cards, there may be no configurable parameters at
all, but typically you will need to configure:
the Interrupt Request, I/O base and shared memory address.


-------- Configuring the IRQ, port and shared memory
Specify here the same settings which you set when you
installed the card.
The parameter choices available with each option (e.g.
Interrupt Request) reflect the valid choices for the
chosen card. The currently chosen default value is shown
in the combo list box.
Please select the correct configuration for each of these
parameters then choose OK when you are done.

-------- Go back button
If you decide you made a mistake in choosing the card, 
you can go back to the previous dialog and choose another one.

-------- Exit installer
Select this option to leave the installer at any time.


-------- The Hosts file dialog
This dialog helps create and/or edit the host
configuration file.  For example, the file C:\5PM\CONN\HOSTS,
which specifies your local IP address, gateway address and
contains the list of servers which you want to be able to
access.  An example of this file would be: 

110.1.1.210	LOCALHOST ; This MUST BE HERE
110.1.1.222	ascunix   ; Put in at least one server

NOTE That this is a standard format for both PC and UNIX.


---------------------------------------------

MAKING YOUR OWN ODI DRIVER INSTALLATION FILE

---------------------------------------------
                   
If the installation diskette
does not contain a driver for your card type, and if you
have already obtained a suitable ODI driver for it
(e.g.from the card manufacturer), there are two ways you
can use the driver with the TCP/IP stack provided:
¨   Install a different driver type initially (e.g.
 NE2000) and then edit the appropriate configuration files
 (NET.CFG, STARTNET.BAT and HOSTS) manually. Refer to the
 following section, and to the documentation provided by
 the LAN card manufacturer.  
¨   Prepare your own custom ODI driver ins file or modify the one
provided with the diskette by following the instructions
below.  Once you have prepared the .ins file, copy it onto
the install diskette in the odi directory.

-------- Making a custom ODI driver INS file

In addition to the link drivers themselves (files with the
extension .COM or .EXE), your custom ODI drivers
installation needs to contain a "network card capability
file (ODI)" or a "drvname.ins" file for each of the
drivers on the diskette (this usually has the same base
filename as the driver plus the extension .INS). For
example, the filename of the network card capability file
for the 3C503.COM driver is 3C503.INS.

¨   You also need a file DRIVERS.LST which lists all of
 the drivers that are present on the diskette (see below
 for an example of this file).  This file exists and should
 just be added to if you add your own .ins file and .com
 file.
¨   On the installation diskette, all of the hardware-
dependent ODI components are stored in a single directory
"A:\5PM\CONN\ODI".

¨   DRIVERS.LST is a plain text file with a single line
 entry for each driver. Each line contains four parameters
 separated by commas: the link driver description, version
 and filename, and the name of the network card capability
 file. In the example below, the 3Com Etherlink III/EISA
 uses the same link driver as the standard 3Com Etherlink
 III/EISA (3C509.COM) but it has a different network card
 capability file (3C579.INS), because it has different
 hardware settings.  The following DRIVERS.LST file from
 the installer diskette shows the standard ODI drivers
 which are currently provided with the TCP/IP stack:

Novell/Eagle NE1000, v1.23, NE1000.COM, NE1000.INS
 Novell/Eagle NE1500T, v1.24, NE1500T.COM, NE1500T.INS
 Novell/Eagle NE2000, v1.37, NE2000.COM, NE2000.INS
 Novell/Eagle NE2100, v1.24, NE2100.COM, NE2100.INS
 Novell/Eagle NE3200, v1.10, NE3200.COM, NE3200.INS
 Novell/Eagle NE/2, v1.22, NE2.COM, NE2.INS
 Novell/Eagle NE/2-32, v1.24, NE2_32.COM, NE2_32.INS
 Novell/EXOS 205/215, v1.20, EXOS.COM, EXOS.INS
 3Com EtherLink     3c501, v1.10, 3C501.COM, 3c501.INS
 3Com EtherLink II  3c503, v1.30, 3C503.COM, 3C503.INS
 3Com EtherLink+    3c505, v1.20, 3C505.COM, 3C505.INS
 3Com EtherLink 16  3c507, v1.20, 3C507.COM, 3C507.INS
 3Com EtherLink/MC  3c523, v1.20, 3C523.COM, 3C523.INS
 3Com EtherLink     NW1000, v1.22, NW1000.COM,NW1000.INS
 3Com EtherLink III 3c509, v1.20, 3C509.COM, 3C509.INS
 3Com EtherLink III/EISA 3c579, v1.20, 3C509.COM,3C579.INS
 Schneider & Koch SK-NET G-16, v1.40, SKMLID.COM,SKG16.INS
 Schneider & Koch SK-NET TR-16, v2.04, SKTOK.COM,SKTOK.INS
 Schneider & Koch SK-NET FDDI, v1.21, UPPSODIF.EXE, SKFDDI.INS
 IBM Token-Ring Network Adapter II, v1.12, TOKEN.COM,TOKEN.INS
 IBM Token-Ring Network 16/4 Adapter, v1.12, TOKEN.COM,TOKEN.INS
 IBM Token-Ring Adapter/A, v1.12, TOKEN.COM, TOKEN.INS
 IBM Token-Ring Network 16/4 Adapter/A, v1.12,TOKEN.COM, TOKEN.INS
 IBM PC Network Broadband Adapter II, v1.34, PCN2L.COM,PCN2L.INS
 IBM PC Network Broadband Adapter II/A, v1.34,PCN2L.COM, PCN2LA.INS
 IBM PC Network Baseband Adapter, v1.34, PCN2L.COM,PCN2L.INS
 IBM PC Network Baseband Adapter/A, v1.34, PCN2L.COM,PCN2LA.INS
 SMC/WD EtherCard PLUS Elite, v2.00,SMCPLUS.COM,SMCPLUS.INS
 SMC/WD EtherCard PLUS Elite 16, v2.00,SMCPLUS.COM,SMCP16.INS
 SMC/WD EtherCard PLUS Elite 16T, v2.00,SMCPLUS.COM,SMCP16.INS
 SMC/WD EtherCard PLUS Elite Combo, v2.00,SMCPLUS.COM,SMCP16.INS
 SMC/WD EtherCard PLUS Elite 10T, v2.00,SMCPLUS.COM,SMCP16.INS
 SMC/WD EtherCard PLUS/A MCA, v2.00, SMCPLUS.COM,SMCMCA.INS
 HP EtherTwist NC/16 TP, v4.01, AM2100.COM, AM2100.INS
 HP EtherTwist AM1500T, v4.10, AM1500T.COM, AM1500T.INS
 HP PC Adapter/8/16/16+, v2.00, HPISAODI.COM,HPISAODI.INS
 HP EtherTwist EISA Adapter/32, v1.00, HP32ODI.COM,HP32ODI.INS
Other Network Card,      , NE2000.COM, OTHER.INS
    
The network card capability file which accompanies each
 driver is a plain text file with a flexible syntax, for
 example:
                   HELIOS ODI driver_name
                   *(+param1_name) param1 description
                   value1
                   @value2
                   value3
                   value4
                   value5
                   .
                   .
                   *(+param2_name) param2 description
                   value1
                   value2
                   @value3
                   value4
                   .
                   .
                   
where
driver_name is the base filename of the driver to which
 the configuration applies (e.g. 3C503, if the driver is
 3C503.COM).
param1_name is one of the configurable card parameters
 (e.g. INT) and param1 description is a description of
 that parameter (e.g. "Hardware interrupt"). These are
 the strings you see in the installation program under
 "Configuring parameters".
value1.. ..value2 etc. are the possible values the
 parameter can have (e.g. 2 and 3 for INT2 and INT3)
 These are the choices you will see in the combo list box
 in the dialog box. If the value is preceeded by "@",
 then this is the default value which is prompted.
An alternative syntax is as follows:
                   *(+param2_name) Param2 description
                   value1   string1
                   value2   string2
                   @value3  string3
                   value4   string4
                   
In this case, the choices you are offered in the list box
 in the installer are string1...string4. If you choose
 e.g. string3, then value3 is the value which is
 configured. This can be useful if the driver requires
 that value is specified in measurement units which are
 not easy to visualize, such as memory pages or addresses
 in octal.
The default values suggested in the edit part of the combo
 are those prefixed with a "@" in the network card
 capability file, which also contains a list of the valid
 settings which are displayed.
In the above example, the variable "param1_name"  is
 prefixed with a "+" sign.  There are three other
 "switches" which can preceed the parameter name. The
 following describes all four:
                   "+"Display parameter in ODI driver
                       configuration dialog and include
                       selected value in the Link Driver
                       section of NET.CFG.
                   
                   "-"Display parameter in ODI driver
                       configuration dialog and DO NOT 
                       include the selected value in the 
                       Protocol PCShare section of NET.CFG.
                   
                   "!"Do not display parameter in ODI
                       driver configuration dialog but
                       copy the entire section without
                       change in the Link Driver section
                       of NET.CFG.
                   
                   "%"Do not display parameter in ODI
                       driver configuration dialog but
                       copy the entire section without
                       change in the Protocol PCShare
                       section of NET.CFG.
                   
This allows the network card capability file to:
                   (a)Specify a list of configurable
                       parameters for both the Link Driver
                       and the Protocol PCShare sections
                       of NET.CFG. The former are
                       essential for correct driver
                       configuration and the latter are
                       mainly used to tune the ODI
                       connection for best performance.
                   
                   (b)Include non-configurable parameters
                       which are copied without change to
                       either the Link Driver or the
                       Protocol PCShare sections of
                       NET.CFG.

The following is an example network card capability file
 for the 3Com 3C503 network card:

HELIOS ODI 3C503		; This must be the header of the file
 *(+INT) Interrupt Request
 2
 @3
 4
 5
 *(+PORT) I/O Base Address
 280
 @300
 310
 320
 330
 340
 350
 360
 370
 380
 390
 3A0
 3B0
 3C0
 3E0
 3F0
 *(+DMA) DMA Channel
 @1
 2
 3
 -   NONE
 *(+MEM) Base Memory Address
 C0000
 C4000
 CA000
 CC000
 @D0000
 D4000
 D8000
 DC000
 E0000
 E4000
 EA000
 EC000
 *(-MEMSIZE) Memory Size
 @200     8 Kb               ; this is just extra info
-   NONE
*(+CONNECTOR) Thick or Thin Ethernet
DIX Thick
@-  Thin
*(!DEFAULT) Linkdriver
FRAME ETHERNET_802.3
FRAME ETHERNET_II
Protocol TCP/IP 800 ETHERNET_II
Protocol ARP/IP 806 ETHERNET_II
Protocol IPX 0 ETHERNET_802.3
*(%PCSHare) Protocol PCShare
RXWINSIZE     3


The above example will give a net.cfg file like this:  

Link Support
	Buffers 8 1500
	MemPool 4096
	Max Stacks 6

Link Driver 3C503
	INT   3
	PORT  300
	DMA   1
	FRAME ETHERNET_802.3
	FRAME ETHERNET_II
	PROTOCOL TCP/IP 800 ETHERNET_II
	PROTOCOL ARP/IP 806 ETHERNET_II
	PROTOCOL IPX 0 ETHERNET_802.3

PROTOCOL PCSHARE
	LINKDRV  3C503
	INSFILE  3C503
	MEMSIZE  200
	RXWINSIZE	3


                 
-------- In this example, the interrupt can be configured in the
 installer with values from 2 to 5 (default INT3), the
 port can be configured from 280 to 3F0 (default 300),
 the DMA channel can be configured as 1, 2, 3 or disabled
 (default 1),  and the base memory address can be
 configured from C0000 to EC000 or disabled (default
 D0000).

-------- The memory size can be configured as 8 kB or NONE. In the
 former case, "MEMSIZE 200" is written to the "protocol
 pcshare" section of NET.CFG. In the latter case, there
 is no MEMSIZE entry in the "protocol pcshare" section of
 NET.CFG

-------- The connector type can be configured for "thick" or "thin"
 Ethernet (default "thin"). If you choose "thick", then
 CONNECTOR DIX is written to the Link Driver section of
 NET.CFG. If you choose "thin",  there is no CONNECTOR
 entry in the Link Driver section of NET.CFG.

-------- Accordingly, for this card the following parameter is
 written to the Protocol PCShare section of NET.CFG:
                   RXWINSIZE   3
It cannot be configured with the installer.


-------- The following parameters are written to the Link Driver
 section of NET.CFG:
                   FRAME ETHERNET_802.3
                   FRAME ETHERNET_II
                   Protocol TCP/IP 800 ETHERNET_II
                   Protocol ARP/IP 806 ETHERNET_II
                   Protocol IPX 0 ETHERNET_802.3
                   
They cannot be configured with the installer.

HERE ARE SOME EXPLANATIONS ABOUT PARAMETERS IN THE PROTOCOL PCSHARE SECTION
---------------------------------------------------------------------------
UDPCKSUM	boolean_value
	UDPCKSUM specifies whether to use a checksum
	for UDP data packets or not.  "0" specifies no	
	checksum and "1" specifies "use checksum".
	The default is "0".
	It is normally only necessary to specify a checksum
	for a modem or other non-reliable connection; Ethernet,
	Token-Ring and X.25 connections etc. usually have 
	hardware-based error-checking built in.

MAXMTU		max_transfer_size
	MAXMTU specifies in bytes the size of the IP data
	packets to be used by the TCP/IP software.  The TCP/IP
	specifications is flexible in this respect.  The
	default for MAXMTU is "1500" for Ethernet II and
	"1492" for Ethernet 802.3, Token-Ring and FDDI.  The
	valid range of MAXMTU is 250-21,8454 Bytes (just
	over 21 KB).
	NOTE: MAXMTU * NETBUFS must not exceed 64KB.

NETBUFS		integer_value
	NETBUGS specifies the number of network buffers to be
	allocated and used by our TCP/IP Stack.  The default
	value for this is 3.  (maximum should not exceed 20).

RXWINSIZE	integer_value
	RXWINSIZE specifies the maximum number of data
	packets that can be passed from the server to
	each client throught the network during each transaction.
	This depends on the network card's buffering
	performance. (NOTE: RX is an abbreviation for Receive
	and TX for Transmit).

	The number of packets may need to be limited if the buffer
	size of the network card in the workstation is 
	too small.  RXWINSIZE can be varied to optimize the
	data transfer rate.

	If you set RXWINSIZE to a value which is too high, and
	the network card or PC cannot process the packets fast
	enough and starts dropping them, the resulting packet
	retries will cause a rapid drop of network throughput
	to be about 10% of the normal speed.

	Safe values for RXWINSIZE are:
	
	on-card memory		RXWINSIZE
	-------------------------------------
	8  KB			3
	16 KB			8
	32 KB			16

	The default for RXWINSIZE is 3.

MEMSIZE		integer_value
	MEMSIZE specifies the amount of on-board RAM on the
	network card in KB.

	This parameter is used to exclude the network
	card's shared memory from the memory available
	to Windows and the EMM386 driver.  It is omitted
	from NET.CFG if there is no on-board RAM on the
	network card.  This should be specified in your
	system.ini file starting at address MEM BASE address.

LINKDRV		string
	LINKDRV specifies the base filename of the network
	card's link driver.

INSFILE		string
	INSFILE specifies the base filename of the network
	card capability file.  It is used only for installation
	of the TCP/IP stack.


---------------------------------------------
TCP/IP STACK SOFTWARE FOR DOS AND WINDOWS
---------------------------------------------
The following describes all configuration files
which are relevant to our TCP/IP Stack.  A directory
is created upon installation called 5pm\conn from 
the root directory and contains:
(Assuming your ethernet card is SMCPlus)
HOSTS, NET.CFG, PCS_ODI.EXE, SMCPLUS.COM, SMCPLUS.INS,
LSL.COM, SERVICES, STARTNET.BAT.

The following files are modified upon installation:
AUTOEXEC.BAT:
	The stanard configuration file autoexec.bat loads
	a number of important DOS modules when you boot your
	PC.  The TCP/IP stack installation adds the following
	to this file if you choose so:
		call C:\5PM\CONN\STARTNET.BAT

STARTNET.BAT:
	Startnet.bat, which is created by the installer 
	is called by the autoexec.bat and loads the tcp/ip
	ODI drivers when you boot your PC.  It also loads
	a small program needed by the machine.

	set PCSHARE=c:\5pm\conn
	c:\5pm\conn\lsl.com
	c:\5pm\conn\SMCPlus
	c:\5pm\conn\pcs_odi.exe

NET.CFG:
	Net.cfg is the configuration file for the ODI network
	drivers used by the TCP/IP stack.  It is created and/or
	modified by the installer.  For example, when installing
	a 3COM 503 ethernet adapter card, your net.cfg would be:

	Link Support
		Buffers 8 1500
		MemPool 4096
		Max Stacks 6

	Link Driver 3C503
		INT   3
		PORT  300
		DMA   1
		FRAME ETHERNET_802.3
		FRAME ETHERNET_II
		PROTOCOL TCP/IP 800 ETHERNET_II
		PROTOCOL ARP/IP 806 ETHERNET_II
		PROTOCOL IPX 0 ETHERNET_802.3
	
	PROTOCOL PCSHARE
		LINKDRV  3C503
		INSFILE  3C503
		MEMSIZE  200
		RXWINSIZE	3


HOSTS:
	The hosts file specifies the internet addresses and 
	names of all available TCP/IP servers on your network.
	It also specifies the subnet mask, gateway and your
	local IP address.  It has the following syntax:

	#Internet IP address	Computer name    Aliases/Function
	110.1.1.152		LOCALHOST
	255.255.255.0		submask
	110.1.1.12		ascaux		unixServer	
	110.1.1.170		ascsun		server ; another server
	110.1.1.100		gateway

	The subnet mask is calculated automatically by pcs_odi.ee from 
	"localhost" and does not need to be specified at all in the 
	hosts file if you are using standard class A, B or C addresses.

	The gateway entry, which is also optional, specifies the internet
	address of an internet gateway(if available).  If several gateways
	are specified, only the first one is used.  A gateway host can also
	be a server, but it need not be.  The gateway line should be 
	omitted if no gateways are present or if the gateway is running the
	"routed" daemon.
	


