	      Microsoft TCP/IP Utilities for LAN Manager

			     Version 1.0


		       SUPPLEMENTAL INFORMATION



Copyright 1992 Microsoft Corporation. All rights reserved.

Microsoft, MS, and MS-DOS are registered trademarks and Windows is a
trademark of Microsoft Corporation. 

Operating System/2 and OS/2 are registered trademarks licensed to
Microsoft Corporation. U.S. Patent Number 4955066.


Introduction
------------

This file reflects last-minute information regarding the Microsoft
TCP/IP Utilities for LAN Manager version 1.0.

This file includes the following sections:

	-   Over-the-net installation for diskless workstations or
	    those with low-density floppy drives

	-   Installing/configuring the Microsoft TCP/IP Utilities 
	    from the LAN Manager 2.1 SETUP program

	-   Memory considerations under MS-DOS and Microsoft Windows

	-   Using vbapi.386 and bapidll.exe with third-party Windows
	    terminal emulators

	-   Notes on MS-Kermit


Over-the-net installation of the Microsoft TCP/IP Utilities
-----------------------------------------------------------

Although the Microsoft TCP/IP Utilities for LAN Manager are
distributed on high-density floppy diskettes, it is possible to
install them on LAN Manager diskless workstations, as well as LAN
Manager workstations lacking high-density floppy drives. To prepare
the TCP/IP Utilities for over-the-net installation, it is necessary
to set up a share on a LAN Manager server and to copy the
distribution diskette to that share.


To set up the source directory and share on the server:

	1.  On the server, create the directory that you will use to
	    store the Microsoft TCP/IP Utilities distribution tree.
	    For example:

	    	MKDIR C:\PUBLIC\DIST\TCPUTILS

	2.  Share the server's directory (this will require
	    administrative privileges on the server).  For example:

		NET SHARE TCPUTILS=C:\PUBLIC\DIST\TCPUTILS

	3.  Set the correct access permissions using the NET ADMIN
	    utility or the NET ACCESS command.  (For more information
	    on resource permissions, refer to your LAN Manager 2.1
	    documentation)

	4.  The server is now ready for copying of the distribution
	    diskette.


To copy the distribution diskette to the LAN Manager server from the
server's own high density floppy disk:

	1.  Change into the subdirectory that you will be sharing the
	    Microsoft TCP/IP Utilities from.  For example:

	    	CD C:\PUBLIC\DIST\TCPUTILS

	2.  Insert the Microsoft TCP/IP Utilities distribution
	    diskette into your server's high density floppy
	    drive.

	3.  Copy the distribution diskette to the subdirectory:

		XCOPY A:*.* C: /S /E

	    Where A: is the drive containing the distribution
	    diskette. 

	4.  The server is now prepared for over-the-net installation
	    of the Microsoft TCP/IP Utilities.


To copy the distribution diskette to the LAN Manager server from a
workstation on the network: 

	1.  Establish a session with the LAN Manager server share
	    that has been prepared to copy the distribution diskette
	    to. For example:

	    	NET USE T: \\SERVERNAME\TCPUTILS

	2.  Insert the Microsoft TCP/IP Utilities distribution
	    diskette into your workstation's high density floppy
	    drive.

	3.  Copy the distribution diskette to the server share:

		XCOPY A:*.* T: /S /E

	    Where A: is the drive containing the distribution
	    diskette. 

	4.  The server is now prepared for over-the-net installation
	    of the Microsoft TCP/IP Utilities.


To install the Microsoft TCP/IP Utilities on to your workstation
over-the-network:

	1.  Log on as a LAN Manager user which has permissions to 
	    access server's resources.  For example:

	    	NET LOGON USER PASSWORD

	2.  Establish a session with the server that has been
	    prepared for over-the-net installation of the Microsoft
	    TCP/IP Utilities. For example:

	    	NET USE T: \\SERVERNAME\TCPUTILS

	3.  Run the TCPSETUP program:
	
		T:TCPSETUP

	4.  TCPSETUP will determine whether or not your workstation
	    is running the MS-DOS or OS/2 operating system and copy
	    and configure the appropriate files on your workstation.


Installing & configuring the Microsoft TCP/IP Utilities from the
LAN Manager 2.1 SETUP program
---------------------------------------------------------------

You may access the TCPSETUP program from the LAN Manager 2.1 SETUP
program's "Connectivity" menu.

To install the TCP/IP Utilities from the LAN Manager 2.1 SETUP
program:

	1.  Run the LAN Manager 2.1 setup program and choose the
	    "Connectivity" menu option from the menu bar.  Select
	    "Install..."

	2.  Specify the drive/path of your Microsoft TCP/IP Utilities
	    file tree (this is the drive in which your distribution
	    disk is inserted, or the network drive you have
	    established if you are doing an over-the-net install) and
	    press [return].

	3.  LAN Manager 2.1 setup will invoke the TCPSETUP program
	    and copy and configure the distribution files onto your
	    system.


To configure the TCP/IP Utilities from the LAN Manager 2.1 setup
program: 

	1.  Assuming that you have already installed the TCP/IP
	    Utilities, you can run the LAN Manager 2.1 setup program
	    and choose the "Connectivity" option from the menu bar.
	    You should have the option to choose "Microsoft TCP/IP
	    Utilities v1.0".  Select this option and the LAN Manager
	    2.1 setup program will invoke TCPSETUP. You may now
	    modify your TCP/IP Utilities configuration. Exiting
	    TCPSETUP will return you to the LAN Manager 2.1 setup
	    program.

	Note: It is not necessary to have installed the Microsoft
	TCP/IP Utilities via the LAN Manager 2.1 setup program in
	order to configure them in this fashion. TCPSETUP will
	automatically make the LAN Manager 2.1 setup program aware of
	its installation.


Memory considerations under MS-DOS and Microsoft Windows
--------------------------------------------------------

When installing or configuring the Microsoft TCP/IP Utilities, you
will be required to specify the number of sockets and telnet sessions
you want. Likewise, the LAN Manager SETUP program requires you to
specify the number of NetBIOS sessions that you require. 

NetBIOS sessions, telnet sessions, and sockets buffers are all
allocated when you load the Microsoft TCP/IP transport. Since all of
these buffers are allocated at once, it is possible to configure the
transport to request too many buffers. If you request too many
buffers, you will see the following error message when LOADing
Microsoft TCP/IP:

	NET0110: Insufficient memory to load TCP 1.0 
	         Unloadable TCP 1.0 not loaded.

The appropriate action to take when this error occurs is to reduce
your TCP/IP buffer requirements using TCPSETUP or LAN Manager 2.1
SETUP.  For example, allocate a smaller number of NetBIOS sessions.
We recommend that you request fewer than 25 (combined) sockets,
Telnet and NetBIOS sessions to be sure not to have buffer allocation
problems.

Note: when modifying any of these parameters it is necessary to
re-initialize the TCP/IP transport for your changes to take effect.
This can be done in one of two ways:

	1.  Unload and reload TCP/IP using the LAN Manager 2.1 
	    UNLOAD TCPIP and LOAD TCPIP commands.

	2.  Reboot your workstation


Using vbapi.386 and bapidll.exe with third-party Windows terminal
emulators 
-----------------------------------------------------------------

The files vbapi.386 and bapidll.exe are provided on your Microsoft
TCP/IP Utilities for LAN Manager distribution diskette. Both are
modules which are required by some third-party terminal emulation
programs written to the BAPI specification under Microsoft Windows.

Not all Windows terminal emulators require these modules. See your
terminal emulator's user's guide to determine if either module is
necessary for your particular terminal emulator. For instance, when
running Kermit under the Windows environment, it is not necessary to
have either module present to provide full functionality.

Neither module is copied to your system during the TCP/IP Utilities
installation process.  Both vbapi.386 and bapidll.exe are located in
the \netprog.dos subdirectory on your TCP/IP Utilities distribution
diskette. vbapi.386 is designed for computers running Microsoft
Windows in enhanced-mode, bapidll.exe is designed for computers
running Microsoft Windows in standard-mode.  If your terminal
emulator requires either of these files, you must copy them by hand
from the \netprog.dos subdirectory on the distribution diskette to
your system.


Notes on MS-Kermit
------------------

In order to provide "automatic DPA functionality" under MS-Kermit, we
renamed the actual Kermit program to kerm.exe.  Kermit.exe is
responsible for loading and unloading the necessary Microsoft TCP/IP
modules necessary to run MS-Kermit over TCP/IP. If you wish to run
Kermit *without* loading these modules, simply execute kerm.exe.
