========================================================================
                             Co*STAR Network
                               
                              Release Notes
                                                                                                                                               
========================================================================
 
The TCP/IP support under Co*STAR has been enhanced to support the new WINSOCK.DLL 
version 1.1.    Windows For Workgroup users who have installed the TCP/IP option 
should configure Co*STAR to use the "Windows Sockets TCP/IP v.1.1" setting in the 
Network Configuration dialog box.

IMPORTANT:  
Network users must re-select the network configuration using the Commands/Configure 
Terminal/Network menu options in order for Co*STAR to update the files in your 
Windows directory.   The installation program will only update certain network types.  



To install the TCP/IP option for Co*STAR please do the following:

	1) Install Co*STAR using the INSTALL program on the Co*STAR
	Installation Diskette.

	2) Once installed, run the Co*STAR program by clicking on 
	the icon.

	3) Select the Commands/Configure menu option.

	4) Under the 'Network or Port' selection choose TCP/IP.   The
	Network button at the bottom of the dialog box will be disabled
	until TCP/IP is selected as the port.

	5) The Network button at the bottom of the dialog box should
	now be enabled.  If this button does not appear, please re-install
	Co*STAR.

	6) Select the Network button.   A dialog box will appear 
	that will let you enter the network type, the host system name,
	and the IP address of your host computer.  You may need to 
	consult your system administrator for assistance in selecting
	the proper settings.

	7) You may be prompted to insert your Co*STAR Installation 
	diskette.   Some network configurations will require additional
	files to be added into your AUTOEXEC.BAT file. 	If this is necessary, 
	you will be prompted to let Co*STAR edit the AUTOEXEC.BAT file and 
	re-boot your PC.  For the TSR's to work properly, your Windows 
	directory must be located in your DOS PATH statement.

	8) Use Notepad's Search Menu option to locate the requirements 
	for your vendor's network.   The list of supported networks
	is outlined below.



========================================================================
TCP/IPs Supported.
========================================================================
The ensuing pages of this Release Notice specify which TCP/IP stacks are 
supported at this release, the version numbers specifically validated, 
and any pertinent transport-specific information.  In summary the version 
validated are,    


TCP/IP Stacks				Supported Releases
-----------------------------------------------------------------------
3Com 3+Open TCP				v1.1, v1.2 & v2.0
Beame & Whiteside TCP/IP		v2.2, v2.3 & v3.0
digital PATHWORKS for DOS (TCP/IP)	v4.1
D-Link TCP/IP for DOS			v2.0
FTP PC/TCP				v2.04, v2.05 & v2.1
HP ARPA Services for DOS		v2.1
Locus TCP/IP for DOS			v2.0
Microsoft LAN Manager TCP/IP		v2.1 & v2.1a
Novell LAN WorkPlace for DOS		v4.00 & v4.01
Sun PC-NFS TCP/IP			v3.0, v3.5 & v4.0a
Ungermann-BassNet/One TCP/IP		v16.4 & v16.5
Wollongong WIN/TCP for DOS		v4.1.1
Wollongong PathWay Access for DOS	v1.1, v1.1.2 & v2.0
(Generic) Windows Sockets TCP/IP	v1.0 rev C &v1.1
(eg. NetManage Inc TCP/IP, 
Frontier Tech. Super - TCP)




======================================================================
3Com 3+Open TCP
======================================================================

Versions validated:

		v1.1 and v1.2 via M3OPEN.EXE TSR
		v2.0 via M3OPEN.DLL

Notes:

	1. The TCPCONNECTIONS parameter in the (TCPIP) section of 
	PROTOCOL.INI determines the number of concurrent TCP connections 
	allowed by 3Com TCP. 
	
	2. For the gethostname () call to work correctly, you must 
	ensure that the correct name for the local host is present 
	in the PROTOCOL.INI file.  The entry is in the TCPGLOBAL 
	section as indicated below

				[TCPGLOBAL]
				HOSTNAME=localname
	where localname is the name of the local machine name as present 
	in the local hosts file or in the domain name server host file.


======================================================================
Beame & Whiteside TCP/IP
======================================================================
Versions validated:

		2.2, 2.3 and 3.0 via MBW.EXE TSR

Notes:

	1.  If problems are experienced with Beame & Whiteside TCP/IP 
	which seem to indicate data loss or some other degree of 
	unpredictability, then you should try increasing the buffer 
	space for incoming packets configured via the BWCUSTOM utility 
	to, say, 30,000 or 50,000.  A "Printer not ready" error message
	from Beame & Whiteside TCP/IP typically indicates lack of 
	buffer space.

	2.  With early version (eg v2.2), Beame & Whiteside recommends 
	that you use NDIS network interface drivers rather than specific 
	native drivers when running under windows.


======================================================================
Digital PATHWORKS for DOS (TCP/IP)
======================================================================
Versions validated:

		v4.1 via M3OPEN.EXE TSR

Notes:

	1. This is an OEM version of 3Com 3+Open TCP.  All the comments 
	and caveats regarding 3Com 3+Open TCP apply to digital PATHWORKS 
	for DOS.


======================================================================
D-Link TCP/IP for DOS
======================================================================
Versions validated:

		v2.0 via MLOCUS2.EXE TSR

Notes:

	1.  This is an OEM version of Locus TCP/IP for DOS.  All the 
	comments and caveats re Locus TCP/IP apply to D-Link.

======================================================================
FTP PC/TCP
======================================================================
Versions validated:

		v2.04, v2.05 and v2.1 via MFTP.EXE TSR

Notes:

	1.  The FTP PC/TCP Virtual Device Driver (VxD) is required in 
	order to run other FTP applications alongside VSL-derived 
	applications over FTP TCP/IP.

	2. Ensure that you allocate enough TCP and packet buffers for 
	your application within the FTP kernel.

		e.g. 'kernel - name' -t 16 -p 20 allocates 16 TCP 
		connections and 20 packet buffers.

	3. Device driver entries for IPCUST.SYS and IFCUST.SYS must be 
	configured into CONFIG.SYS even for version 2.1 of FTP PC/TCP 
	which, theoretically, uses the "new" configuration mechanism.

	4. Intermittent problems with FTP when using a packet driver 
	at least at version 7.3.

	5. Once the maximum number of connections has been reached, it 
	may prove difficult to effect any connection thereafter until all, 
	or almost all, connections have been closed.  You are therefore 
	recommended to set the maximum number of connections to a higher 
	value than you will actually need.

	6. UDP sockets cannot be made non-blocking.  This is a problem 
	that is being looked at by FTP.


======================================================================
HP ARPA Services for DOS
======================================================================
Versions validated:

		v.2.1 via MHPARPA.DLL

Notes:

 	1. For the gethostname() call to work correctly, you must ensure 
 	that the correct name for the local host is present in the 
 	TCPUTILS.INI file.  The entry is in the TCPGLOBAL section as 
 	indicated below
 	
		[TCPGLOBAL]
		HOSTNAME=localname

	where localname is the name of the local machine name as present 
	in the local hosts file or in the domain name server host file.

======================================================================
Locus TCP/IP for DOS
======================================================================
Versions validated:

		v2.0 via MLOCUS2.EXE TSR

Notes:

	1. Locus TCP/IP for Dos is a pseudo BSD4.2 implementation.  
	Consequently, only client-side functionality is supported for 
	this transport.  

	2. Configure the number of connections by using the -s argument 
	to the LTCPIP program.

		e.g. LTCPIP -s8 configures 8 connections.
        

======================================================================
Microsoft LAN Manager TCP/IP
======================================================================
Versions validated:

			v.2.1 via M3OPEN.EXE TSR
			v.2.1a via MHPARPA.DLL DLL

Notes:

	1. Ensure that the NUMSOCKETS parameter in the [SOCKETS] section 
	of TCPUTILS.INI is set to the maximum concurrent number of 
	connections required.

	2. Ensure that you invoke the SOCKTSR.EXE TSR situated in 
	the \LANMAN\ARPA directory.

	3. For the gethostname() call to work correctly, you must ensure 
	that the correct name for the local host is present in the 
	TCPUTILS.INI file.  The entry is in the TCPGLOBAL section as 
	indicated below

			[TCPGLOBAL]
			HOSTNAME=localname

	where localname is the name of the local machine name as present 
	in the local hosts file or in the domain name server host file.
                                
                                
                                
                                
======================================================================
Novell LAN Workplace for DOS
======================================================================
Versions validated:

		4.00 and 4.01 via MNOVLWP.DLL

Notes:

	1. If more than 20 UDP and TCP sockets are allocated in total 
	in NET.CFG then it may be found that no UDP sockets are accessible.

	2. Novell LAN Workplace for DOS will only work successfully when 
	running Windows in enhanced mode.

	3. The device VTCPIP.386 must be present in the [386Enh] section 
	of the SYSTEM.INI file situated in the Windows directory, as 
	mandated in the Novell Lan Workplace for DOS documentation.  
	Failure to do so will cause a General Protection fault in 
	Windows.  This is a common problem.
         
         
         
======================================================================
Sun PC-NFS TCP/IP
======================================================================
Versions validated:

		v3.0 via MPCNFS.EXE TSR
		v3.5 via MPCNFS2.EXE TSR
		v4.0a via MPCNFS4.DLL

Notes:

	1.  The size of the PC-NFS libraries necessarily linked into the 
	MPCNFS.EXE TSR is extremely large.  To reduce memory occupation, 
	should it be a problem, try using the /c number argument to 
	reduce the number of concurrent sockets managed by the TSR, or 
	switch to the PC-NFS 3.5 or above products.  v3.0 supports 
	a maximum of 8 sockets.

	If you experience problems with Sun PC-NFS v3.01, you should 
	update to v3.5 or later.

	2.  The Sun Resident Transport Module, RTM.EXE, must be loaded 
	prior to invoking Windows with v3.5 or later.  The /HEAP 
	parameter must be specified with RTM.EXE if more than 8 sockets 
	are required.  Each connection consumes 4kb, so RTM /HEAP 
	60 specifies the maximum 15 sockets.

	3. With v3.5, either RNMFILE.EXE or RNMNIS.EXE should be run 
	after RTM.EXE is loaded.  RNMNIS.EXE should be run if you wish 
	to use Yellow Pages (NIS), else use RNMFILE.EXE.

	See sub-directory \RTS\NFS on the release disk for more 
	information from Sun on v3.5.

	4. MPCNFS4.DLL will only work with version 4.0a of PC-NFS.  
	Included with this VSL are some files from Sun, that you may 
	ship with your application, that upgrades any version of 
	PC-NFS to version 4.0a.


	5. Specific TSR command-line arguments:

	Arg		Example		Meaning

	/n		MPCNFS /n256	Packet buffer size, default 512.
					Determines the size of network packets.

	/r		MPCNFS /r512	Read/Send buffer size, default 1024.
					Determines buffer sizes.

	/y		MPCNFS /y	Specifies that Sun Yellow Pages 
					facility NIS is being used.

	

======================================================================
Ungermann-Bass Net/One TCP/IP
======================================================================
Versions validated:

		v16.4 and v16.5 via MNETONE.EXE TSR

Notes:

	1. If you experience intermittent problems with Net/One v16.4, 
	you should update to v16.5 or later.


======================================================================
Windows Sockets TCP/IP Stacks
======================================================================
Versions validated:

	Windows Sockets Version 1.0 Revision C via MWSOCK10.DLL
	Windows Sockets Version 1.1 via MWINSOCK.DLL

Notes:
        1. The following TCP/IP vendors Windows Sockets version 1.1 
        stacks have been validated via MWINSOCK.DLL.

			FTP
			NetManage
			Chameleon
			Frontier Technologies
			Wollongong

	2. The VSL Generic Windows Sockets DLLs are written to expect 
	Windows Sockets compliant stacks conforming to the Windows 
	Sockets specification Version 1.0 Revision C or Version 1.1.  
	However, it is highly unlikely that any vendors will commercially 
	supply a version 1.0 Revision C stack.  We have provided support 
	for this version in case you require it.

======================================================================
Wollongon TCP/IP
======================================================================
Versions validated:

		Win/TCP v4.1.1 via MWINTCP/EXE TSR
		PathWay Access v1.1, 2.0 and 1.12 via MPATHWAY.DLL

Notes:

	1. To successfully run over either of the Wollongong transports, 
	you may find that you need to increase the number of large packet
	buffers configured by Wollongong's CUSTOM program to no less 
	than 20.

	2. Ensure that the number of NETBIOS sessions (sockets) configured 
	by the CUSTOM utility is set high enough.  You need to configure 
	4 more than you actually need, (so 16 will give you 12 connections).
	
        3. You may experience problems with WIN/TCP if greater than 5 
        connections are utilized.  This is due to a problem in the 
        WIN/TCP socket library.

	4. If unreliability is experienced, especially with WIN/TCP, try 
	changing the size of the large packet buffers, configured by 
	Wollongong's CUSTOM program down to 400 or less.

	5. Under conditions of high activity, because send and receive 
	operations share the same buffer space, then send operations can 
	delay long enough to be timed out.  Wollongon are investigating 
	this problem.

	6. You must ensure that your host name has a valid entry in your
	hosts file or, if you are using a name server, that the name 
	server has a valid entry for your machine.  You must also ensure 
	that your host name has been configured using Wollongong's CUSTOM 
	program.
