
          Copyright 1990-1993 Frontier Technologies Corporation
                          Super-TCP for Windows
                              Release 3.00 
                               README.TXT
                             March 12, 1993


PRECEDENCE:

For information on the Super-TCP for Windows applications, consult
the printed manual after reading this file.  If any discrepancies exist
between the Help files and the printed manual, the Help files will
contain the most up to date information.  If any discrepancies exist
between the Help files or printed manual and this README.TXT file, this
file will contain the correct information.



SERIAL NUMBERS:

Each Super-TCP for Windows package must have its own Serial Number and
Authentication Key.  Both are 9-digit numbers in the form xxx-xxx-xx.  At
the time that Super-TCP is installed, the user will be prompted to provide
a valid Serial Number and its corresponding Authentication Key.
Installation cannot proceed without this information.



INSTALLATION:

- Super-TCP provides an extensively automated install procedure.

- We urge you to read the installation section in the printed manual
  before attempting to install the product.  This will eliminate any
  difficulties you may encounter at a later stage.

- When installing over a Super-TCP for Windows 1.30 or greater
  all information about your system will be saved for you.

- When you are installing over a Super-TCP for Windows 1.2, the mailboxes
  and hosts file will be saved for you.  Before you upgrade please make a
  note of the following information:
    -Internet Address
    -The machine name
    -The address of any Domain Name Servers
    -Address and settings of the SNMP agent
    -Hardware type and parameters

- If using NetWare coexistence with Super-TCP for Windows 1.2, be
  sure to correctly logout of the Novell server before upgrading.
  This is due to the fact that this update supports Novell coexistence
  through 802.3 Raw or "normal" NetWare on ethernet devices.

- If you have commands in your AUTOEXEC.BAT file which must be run after
  Super-TCP for Windows (for example, automatically starting Windows at
  boot-time), you must edit your AUTOEXEC.BAT after installation to move
  those lines after the lines added by the Super-TCP for Windows.



NEW SINCE VERSION 2.00:

- TCP/IP: WinSock - 1.1 draft 3 compliant, except for resetting connection
  when blocking send canceled.

- VxD: Replaces the NETGLUE TSR, Super-TCP for Windows takes up only 3K
  for NDIS, and 0K for Packet and ODI Drivers.

- FTP: 

   1) Now supports the FTP servers supplied by Novell NetWare Servers,
      and Wollongong Pathway Access.

   2) Can confirm on directory removes if preferred.

   3) Supports large directories (unsorted).

   4) Handles local disk space better.

   5) Better error messages.

   6) Supports Novell 3.11 FTP Servers.

- Info: New program, with a Finger client.

- PING: Now supports saving of the settings (command line options take
  precedence over saved options).

- VT320: 

   1) Vt320 support added.

   2) Now supports auto-scaling of some fonts, which allows the user
      to change font sizes simply by resizing the application window. 
      This feature cannot be used on raster fonts.  The feature is 
      not supported in Windows 3.0.

- tn3270: To run tn3270 on at a standard VGA (640x480) resolution, the
  new "FTC Sans Serif-1" font is recommended because it will allow all
  80 columns to be displayed on the screen without use of the scroll bars.

- EMAIL:

   1) MIME capability added.

   2) When using the Reply feature, the original message can be placed
      in the edit field of the new message.

   3) Will correctly Open a message with text attachments.

   4) Attachments in Compose and View Windows.

   5) Direct Insert of file data into Compose edit control is
      no longer available. Use attachment instead.

   6) New Compose options for Expired Time, Deferred Delivery,
      and Priority.

   7) Printing has been enhanced to allow printing from any
      of the Compose, Folder or View windows.

   8) View window shows partial header and allows viewing of
      complete message envelope.

   9) Preferences allows inclusion of a signature at end of Compose
      window note text area.

  10) Preferences are now per-user.

- NNTP:

   1) Network News Reader application added.

   2) Allows 250 root newsgroups. If more are present, the status bar
      shows that the remaining newsgroups are ignored.

- Talk/Talk Server: Support for Sparc compatible talk.

- NFS Client (Windows):
	
   1) Full support for Windows 3.1 Long File name functionality, allowing
      you to manipulate UNIX files entirely from File Manager.

      In Windows 3.1, File Manager displays a new menu: the Network menu.
      This menu contains the item View Long Filenames which enables you 
      to view long filenames in addition to standard DOS-length 
      filenames. Note that the standard filename format will be used for
      all local drives and any network drive mounted BEFORE starting 
      Windows. Only the drives mounted from Windows (including the drives
      that get auto-reconnected when starting Windows) have the option of
      being viewed in the long filename format. 

      The long filename feature is especially useful for drives mounted
      on UNIX Servers. By default, any drive mounted from Windows will be 
      displayed with the long filename option enabled. If the window 
      associated with the drive is the active window and you uncheck View
      Long Filenames under the Network menu, the contents of the Window 
      will be redisplayed using the standard DOS filename conventions. 
      Files whose names do not fit the DOS conventions will be displayed 
      with mapped filenames. Clicking on View Long Filename again toggles 
      the status back to the long filename convention.

      To view and change the attributes of any network file in the UNIX 
      format, select the file in the active window, then choose Properties
      from the File menu. File Manager pops up a dialog which displays the
      attributes of the file which are known to DOS. Clicking the Network
      button allows you to access other attributes, such as the ids of the
      owner and group of the file, the time and date of creation, last
      access and last modification, and the read, write and execute
      permissions for user, group and others. You may change uid, gid and
      the file permissions subject to the usual UNIX file protection
      mechanisms.

   2) The user is able to set the default file protections (at mount time)
      for files created on the remote drive mounted through File Manager.

   3) NFS is now able to permanently mount drives (with or without
      confirmation) at Windows startup. The protections remain the same
      as those set by the user who initially mounted the drive.

-NFS Server (Windows): 

   1) Messages are now logged in the Master Services window when clients
      try mounting to a SuperTCP NFS Server. If General message logging
      is enabled, user mounting and unmounting is logged. If Warning
      message logging is enabled, security violations are logged.

   2) The Super-TCP NFS Server may be mounted by a Unix client:

        a) On the PC running our NFS server, a user needs to be created
           (or given) the UID and GID of 0 and 1, respectively. (The 
           UID=0 and GID=1 correspond to the root (or super) user on 
           the Unix client; the root user is the only user allowed to
           mount remote directories.) This user also needs to have his
           access changed to include at least the List Directory option. 
           (If the user does not have List Directory access, the user
           will not be able to successfully mount the remote drive 
           from the Unix client.

        b) Login as the root account (or type "su"). Then at Unix prompt
           type the following:

           If you are using Interactive or SCO Unix, try:

                mount  -f  NFS  host:drive_letter:/   /foo

           If you are using SunOS or Ultrix, try: 

                mount  -t NFS  host:drive_letter:/   /foo

           If neither of these work, try: 

                mount  host:drive_letter:/   /foo



PERFORMANCE PROBLEMS:

If you are experiencing performance problems, please refer to the 
following list of posssible causes and solutions:

 1) TSR kernel: The DLL kernel is much faster than the TSR kernel 
    when you are using Windows programs.

 2) FTP progress bar: Use Preferences and turn off "Show Progress of 
    File Transfer".

 3) FTP ASCII mode: Binary mode is much faster (UNIX needs to convert
    ASCII files).

 4) Network load: Someone else on the network may be responsible for
    heavy traffic. Many people do not realize that the transfer rate 
    is very much determined by the network.

 5) Load on local and remote machines: Speed may be reduced if many 
    programs are running on the local Windows system and/or on the
    remote machine. Many times people do not know what is happening 
    on the machine they are connected to.

 6) Ethernet Card: Speed can vary depending on the type of ethernet
    hardware you are using. For example, the NE1000 is very slow (80K 
    bytes/sec) compared to the latest 3COM 3c509 (400+K bytes/sec).

 7) Disk drives: Speed can vary depedning on the disk drive and disk
    cache program you are using. For example, disabling SMARTDRV (disk
    cache) can reduce throughput by 50% or more. 

 8) TCP Window size: By increasing TCP Maximum Window value, more data
    can be outstanding on the network. This value can be changed by 
    using the SetupTCP program: "TCP/IP Configuration" under the 
    Advanced "TCP/IP Parameters" section. (Default values: TSR 2048, 
    DLL 6144. The DLL can go as high as 16384)

 9) NFS: If the NFS Client is not necessary, disable it.

10) Driver Type: Packet Drivers are fastest, NDIS drivers are most
    reliable, ODI drivers are slow (usually about 3 times slower than
    Packet Drivers).

11) RIP: If only one gateway is available (and it is known), then 
    disable RIP if it not needed. RIP may make very large routing 
    tables that must be looked at on every packet.



APOLOGIES:

We believe that Super-TCP Version 3.00 is one of the most complete
and easiest products in the Windows networking arena.  However, there are
certain limitations which we could not fix by the production time.
We apologize for any inconvenience these limitations may cause.  We are
continuing to work on each of these issues.

- FTP: On a few systems, FTP has the potential to stop responding after
  a period of time; the network or Windows may have to be restarted.

- Upon complete uninstallation, FTCINST.LOG and FTCDRIVE.INI will be left
  in the Windows directory. 

- Windows For Workgroups: This version will not support the NFS client
  and NetPrint applications in Windows for Workgroups.  All other 
  applications are supported.

- tn3270: Under certain conditions (font point size, video display, 
  tn3270 hosts, etc.) italic and bold italic fonts may appear distorted.
  Instead, choose a regular or bold (non-italic) font.