

                            Tropic  TCP/IP
                             version 1.1b

                        TCP/IP  protocol stack
                      for Microsoft  Windows 3.1

                          November 30, 1994





DISCLAIMER:

THESE PROGRAMS ARE SHAREWARE AND ARE NOT TO BE RESOLD OR DISTRIBUTED
FOR SALE WITH OTHER PROGRAMS WHICH ARE FOR SALE. THE SOFTWARE IS
PROVIDED AS-IS. THE AUTHORS AND TROPIC SOFTWARE DISCLAIMS ALL
WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. NO LIABILITY IS ASSUMED FOR DAMAGES, DIRECT OR
CONSEQUENTIAL, WHICH MAY RESULT FROM THE USE OF THIS SOFTWARE.


 Copyright 1993-94 by Tropic Software.


All trademarks appearing in this document are property of their
respective owners.




Introduction

TCP/IP is a generic name that has been used to designate a series of
standard communication protocols to interconnect computers. TCP/IP
was, in its beginning, primarily available for computers running UNIX
operating system. Nowadays TCP/IP has gained enormous popularity and
is available for a great variety of machines ranging from small
personal computers to big mainframes. It has become a de facto open
industry protocol standard allowing the interconnection of machines
from different vendors with different operating system to
intercommunicate in a standard, transparent way. Tropic TCP/IP is a
program that provides the TCP/IP protocol for the Windows 3.1
environment. With Tropic TCP/IP you have all the power of an open
protocol allowing your computer the ability to run many applications
before only available for big machines. Tropic TCP/IP also
implements the Winsock 1.1 API. This is a standard interface for
accessing network services. With Tropic TCP/IP, your computer is able
to run any application written in conformance with Winsock 1.1
specifications. Examples of applications are:

 Mail programs

 File Transfer programs

 Remote printing programs

Features

The Tropic TCP/IP offers you the following characteristics:

 Implemented as a DLL: the program is written for Windows operating
  system in contrast with being written for DOS. This means that it
  runs under Windows protected mode and does not use memory in the
  low 1Mb physical address space.

 Winsock 1.1 API: any program compliant with this API should run
  with Tropic TCP/IP.

 Support for multiple interfaces: you may configure several hardware
  interfaces to be used by Tropic TCP/IP.

 BOOTP.

Using Tropic TCP/IP

Tropic TCP/IP is used as a base (known as TCP/IP stack) for many
different types of application. To know if a given network
application can use Tropic TCP/IP, verify if the application is
Winsock 1.1 compliant. If it is, it can be used with Tropic TCP/IP.
Before running any application you need to start Tropic TCP/IP
program. Note that to correctly start Tropic TCP/IP you must have it
installed and configured as described in the installation and
configuration sections that follows.


Installation and Configuration of Tropic TCP/IP

Before Installing Tropic TCP/IP, make sure you have the minimum
hardware and software requirements as described below.

 Hardware Requirements
 
   386 or later IBM PC or compatible computer with 1M of free hard
    disk space
 
   One or more network adapters

 Software Requirements

   DOS 5.1 or later version

   Microsoft Windows 3.1 running in Enhanced Mode

   Packet Driver suitable for the network adapter

   Winpkt

For a discussion of what are packet drivers and where to get them
see appendix A.

After checking the minimum requirements, you can proceed with the
installation of the Tropic TCP/IP files as follows:

 If you have downloaded Tropic TCP/IP from the network in compressed
  zip format, first uncompress the file using an unzip program either
  in a diskette or in a temporary subdirectory in your hard disk.

 Execute the setup program (it is called setup.exe). When running,
  setup will ask for a directory where to install the files. The
  default is C:\TROPIC. You may specify any directory for installation.
  The Setup program will copy all the necessary files to the specified
  directory and will create a program group for Tropic TCP/IP.
 
 Add the directory you had specified for installation to the PATH
command in your AUTOEXEC.BAT file.

To configure Tropic TCP/IP you need first to have the following
information:

 Hostname: the name you want your machine to be called.

 Domain name: the domain name assigned to your network.

 IP Address: the network address assigned to your machine. Notice that
  in a given network, each IP address assigned must be unique.

 Network Mask.

 Name server: the IP address (if any) of the machines that provides
  name resolution services.

 Gateways: if your network is connected to other networks, you need to
  provide the following additional information for each gateway.

   Gateway IP address: the address of the machine in your network that
    is acting as a gateway.

   Destination: the network that may be reached through this gateway.

   Type: the type of the destination. If this gateway is used to connect
    with all network destination, it is of the DEFAULT type.

 Packet driver interrupt number.


Sample configuration session

Let's consider that you have gathered the following information
about your machine and network:

 You have a NE2000 network adapter card,
  installed at base address 0x300, interrupt 5.

 You have got a packet driver for NE2000.
  Also you got the winpkt.com program.

 The name of your machine is Amazon

 Your IP address is 135.135.5.8

 Your domain is tropic.forest.com

 Your name server address is 135.135.5.9

 Your default gateway is 135.135.5.1

First thing to do is to install the packet driver files. You do that
while you are in DOS. Edit your autoexec.bat file and insert the
following lines:

ne2000 0x60 5 0x3000
winpkt 0x60

The first line installs the packet driver program with the
information you got for your network card. The value 0x60 is the
packet interrupt vector chosen. The second line installs the program
that allows the packet driver to be used in the Windows environment.
The same value of the interrupt vector (0x60) is used to start the
winpkt program.

You should now install (if you have not done yet) the Tropic package
using the setup program (see above).

Once the installation is complete, run the Tropic custom program and
do the folllowing:

 Select config->routes to config your routing information:
  default,0,135.135.5.1,1.

 Select config->interfaces to config your interface: 96 (this is
  0x60 in decimal), 135.135.5.8, 255.255.255.0

 Select config->nameserver to config your site information: Amazon,
  tropic.forest.com, 135.135.5.9

 Select file->exit to exit the customization.

After you have customized you can run the main Tropic TCP/IP program.


Package Contents

If you downloaded this program in compressed format, the following
list refers to the files after they are uncompressed. The following
files are included in the distribution package:

README.1ST     Brief description and installation instructions
TROTCP.EXE     The main program
CUSTOM.EXE     The customization program
TROPIC.WRI     this file in windows Write format
TROPIC.TXT     this file in text format
ORDER.FRM      Registration intructions and fees
PKTDRVS        Packet driver config file
ROUTES         routing config file
SERVICES       network services description file
RESOLV.CNF     name resolution config file
HOSTS          host name resolution file
PROTOCOL       network protocol description file
BWCC.DLL       Borlandc Custom Control DLL
WINSOCK.DLL    Winsock 1.1 API DLL
WINSOCK.HLP    Winsock 1.1 specification in Windows help format
WINSOCK.H      Winsock 1.1 include file
WINSOCK.LIB    Winsock 1.1 lib


Compatibility

The applications listed below were tested and worked fine with Tropic:

 FTP-Client, version 2.01, John A. Junod;
 QVTNET, version for winsock, V3.9;
 QWS3270, telnet 3270, V1.6;
 WSFNGRD, V1.2, finger deamon;
 CELLO, Legal Informat. Inst., V.101a, Internet Browser.


Troubleshooting

If you find any problem, please contact Tropic Software in the
following e-mail address:

 e.jucah@ieee.org

This does not imply that support is being offered for you. The mainly
purpose of this is for reporting bugs. Anybody whose bug report is
found to be pertinent will be notified of the correction. New
releases will always be made available either trough network
repositories or distribution diskettes.

Please feel free to Tell us everything you like or dislike about this
program in order to let us make it better.


Change Log

 V1.1a - shareware version made publicly available.
 V1.1b	- the features BOOTP and initialization messages were included;
          FIONREAD bug and 15 digit ip address input bug were fixed.


Licensing and Registration

This software is not free. It is shareware. You are granted the right
to test this software for a period of 30 days. After this you have
to register the product (see registration conditions later in this
document) and, if this applies to you, pay the required registration
fee. You may redistribute this program to other persons as long as
you keep the package complete with all the files that are listed in
the Package Contents section in this document.


Registration Fee

Please read the file ORDER.FRM for registration instructions and fees.


APPENDIX A

 What are packet drivers?

 Your computer is physically connected to your network generally
 through a network card. This card is responsible for interpreting
 electrical signals and transforming it in a sequence of bytes
 (normally called a frame) to be used by the network software. The way
 the network card interfaces to the network software depends on the
 card maker. Different cards provides different interfaces. To
 simplify the use of different cards by the same network software a
 small piece of code is placed between the card and the network
 software. This makes all cards appear to interface the same way. This
 piece of code is called a driver code. If the common interface is the
 packet interface, the driver is called a packet driver. The way the
 packet driver interface is accessed is through an software interrupt.
 This is a kind of standard way of accessing third party software
 (like the packet driver). The interrupt is identified by a number
 called the interrupt number. Interrupt numbers stay in the range from
 0x00 to 0xff. By definition, packet driver interrupt number may be
 set to anything in the range of 0x60 to 0x7F. There is not a
 predefined interrupt number for packet drivers. This number is
 specified when the driver is installed (execute). Normally, the value
 0x60 is used as the default value to install the packet driver. In
 some machines this interrupt number may be already in use by some
 other program. In this case any other free number (in the allowed
 range) may be used. Most of the available packet drivers were
 written for DOS running in real mode. In order to make them run in
 the windows protected mode it is necessary to have another small
 piece of software besides the packet driver itself. The purpose of
 this additional software is for compatibility with the windows
 environment.
 

 Obtaining a packet driver

 Chances are that your card maker provide you with a packet driver for
 your card. If this is not your case, you may find packet driver for
 many different types of card in what is called The Crynwr packet
 driver collection. If you have access to internet, you may use FTP to
 get it from the following locations:

  128.252.135.4  : wuarchive.wustl.edu

  141.210.10.117 : oak.oakland.edu

  192.48.96.9    : ftp.uu.net

                                -oo-
