Microsoft TCP/IP for Windows for Workgroups Release Notes
=========================================================

These release notes provide information to supplement the 
"Microsoft TCP/IP for Windows for Workgroups Installation and 
Configuration Guide. "


Installing Microsoft TCP/IP
---------------------------
If you have installed a previous version of Microsoft TCP/IP for 
Windows for Workgroups (such as the TCP/IP support offered with 
LAN Manager Version 2.2), be sure to remove it using the Network 
option in the Control Panel before running the installation procedure 
described in Chapter 2, "Installing and Configuring Microsoft TCP/IP."

Ensure that you follow the installation procedure carefully and 
that you run the Setup program from the distribution diskette. 
If you try to install Microsoft TCP/IP through the Network option 
in the Control Panel, the installation will not work properly because 
the Setup program may need to install an updated Network option in 
the Control Panel.

Note:  You can run more than one transport on your Windows for 
       Workgroups workstation as long as no more than one transport 
       is marked as exclusive.


If You Will Not Run PING.EXE
---------------------------- 
In order to run the ping utility, you must first run NMTSR.EXE. 
The nmtsr executable is a terminate-and-stay-resident (TSR) program 
that is loaded before the Windows operating system is started. It is 
started with an appropriately placed line in the AUTOEXEC.BAT file.

If, however, you will not run the ping utility and you want to 
remove NMTSR.EXE:

 1. In your AUTOEXEC.BAT file, remove or comment out (add REM to the 
    beginning of the line) the line that loads NMTSR.EXE.

 2. Reboot your computer.


If Microsoft RPC Is Installed
------------------------------
If Microsoft RPC is installed on your system, you must copy RPC16C3.DLL 
from the distribution diskette to your WINDOWS\SYSTEM directory in order 
for Windows Sockets to work properly with Microsoft TCP/IP for Windows 
for Workgroups.


Host File Location
------------------
The Microsoft TCP/IP for Windows for Workgroups Installation and 
Configuration Guide incorrectly states the location of the LMHOSTS 
and HOSTS files. The installation procedure actually places these 
files in your local Windows directory.


PROTOCOL.INI Parameters
-----------------------
The following parameters are optional entries in the [tcpip] section 
of the PROTOCOL.INI file.

   Entry	  Units     Range   Default
   ----------------------------------------
   forcepushbit   integer   0,1         0
   maxlmhosts     integer   0-120     120
   tcpretries     integer   1-17       10


   forcepushbit
	When set to 1, forces the stack to set the push bit on every 
	outgoing packet. Setting this entry to 0, or not specifying 
	this entry at all (default), sets the push bit only on 
	packets as needed.

	If you are having trouble connecting to an IBM mainframe, 
	try setting ForcePushBit=1.

   maxlmhosts
	Specifies the number of entries from the LMHOSTS file 
	that should be loaded into the cache when the workstation 
	is booted.

   tcpretries
	Specifies the length of time your workstation will continue 
	attempting to send a packet. The default, 10, corresponds to 
	approximately 50 seconds. Higher values allow more time for 
	repeated attempts to send the packet, up to a maximum of about 
	six minutes.

