                      	       READ ME
		  OnNet(tm) for Windows Version 2.0
                         Release of July 1995 

				NOTICE
 
The information in this document is subject to change without notice
and should not be construed as a commitment by FTP Software, Inc.

While every effort has been made to assure the accuracy of the information
contained herein, FTP Software, Inc. assumes no responsibility for errors
or omissions.  No liability is assumed for incidental or consequential 
damages resulting from the use of the information contained in this 
document.

The software described in this document is furnished under a license and 
might be used or copied only in accordance with the terms of such license.

(c) Copyright FTP Software, Inc.  1986 - 1995.  All rights reserved.

(c) Copyright Unipalm Limited 1994 - 1995.  All rights reserved. 

(c) Copyright Spyglass, Inc. 1986 - 1995.  All rights reserved.  
(c) Copyright Board of Trustees of the University of Illinois 1993 -1995.
NCSA Mosaic was developed by the National Center for Supercomputing
Applications at the University of Illinois at Urbana-Champaign.  NCSA
Mosaic has been commercially enhanced by Spyglass, Inc.  Enhanced
versions developed and supported by FTP Software, Inc.   

FTP Software, InterDrive, and PC/TCP are registered trademarks and 
OnNet is a trademark of FTP Software, Inc.

Other tradenames, trademarks, or registered trademarks are the property 
of their respective owners.

				 CONTENTS


	1.0 Installing OnNet  
	   1.1 Installation Requirements
	   1.2 Upgrading
	   1.3 Upgrading or Reinstalling to a Different Directory
	   1.4 Upgrading to Switch Between a LAN and Serial Connection
	   1.5 Configuring Multiple Interfaces
           1.6 Installing Over Windows 95
	   1.6.1  InterDrive 95 on Windows 95
	   1.6.2  Obtaining Your IP Configuration Information 
			from a DHCP Server
	   1.7 Installing Over Windows NT
	   1.8 Installing MAPI.DLL for Mail OnNet 
	   1.9 OnNet 2.0 and Services OnNet 1.1.1	  
 	   1.10 Troubleshooting Installation
	2.0 Before You Start to Use OnNet Applications   
	   2.1 Before You Start to Use Mail OnNet
	   2.1.1 Upgrading Mail OnNet Folders
	   2.1.2 Before You View Attachments
 	   2.1.3 Set the TMP Environment Variable for Mail OnNet
	   2.2 Getting Started with TN5250
	   2.3 Converting Customized Keymap Files for TN3270  
	   2.4 Using DHCP with Upgrades from OnNet 1.x
	   2.5 Kernel Name Resolution and Third-Party Applications
	   2.6 TN Negotiating the X-Display Option
	   2.7 Resizing the TNVT Scrollback Buffer
	   2.8 InterDrive and Hidden Directories on Some UNIX Systems
	   2.9 Listed Router Address over a Serial Line
	   2.10 Before You Start to Use SOCKS Security
	   2.10.1  Before You Start to Use SOCKS Security Over X OnNet
	   2.11 Changed Command Line Syntax for FTP
	   2.12 WFTPLIB.DLL and WTELNET.DLL Are No Longer Shipped with OnNet
       	3.0 New Applications in OnNet 2.0 
	4.0 New Functionality in OnNet 2.0   
   	   4.1 New Context -Sensitive Online Help 
	   4.2 New TN3270
	   4.3 New Mail OnNet Features
	   4.4 New Dialer Features
	   4.5 New TNVT Features
	   4.6 Redesigned FTP Application
	   4.7 New Statistics Features
	   4.8 New Network Control and FTP Software Network
	   		Driver Features	
	   4.8.1  Logging In to Network Control and the PC/TCP Network
			Driver Connections
	   4.8.2  Network Control and FTP Software Network Driver:
			Changes to Saved Connection Information  
	   4.8.3  Network Control: Changes to the Functions
	   		Available Through the
			Network Button or the Network Icon 
	   4.8.4  Network Control: Deleting Inactive Connections 
	   4.8.5  Network Control: Preventing Filename Mapping
	   		on a CD-ROM Drive
	   4.8.6  Network Control and FTP Software Network Driver: Turning 
			Autotuning On and Off
	   4.8.7  Network Control: Changing Connection Information
	   4.8.8  FTP Software Network Driver: Enabling Symbolic Links 
	   4.8.9  Network Control and FTP Software Network Driver: 
			User Interface Changes
	   4.9 New Network Control and FTP Software Network Driver Printing
			Features
	   4.9.1 Setting When to Print Options
	   4.9.2 Change to the Print Queues Dialog box 
	   4.10 SOCKS Support
	   4.11 New Kernel Features
	   4.11.1 Switching Between a SLIP (or PPP) Kernel and a LAN Kernel
	   4.11.2 ISDN Support for the Serial VxD Kernel
	   4.11.3 WINISDN.DLL Support
 	   4.11.4 VxD Kernel Support for the NetWare IP 2.0 Interface
	   4.12 DHCP Improvements
	   4.12.1 Writing DHCP and BOOTP Configuration Parameters
			to the PCTCP.INI Configuration File
           4.12.2 Updated List of Configuration File Parameters for
			the DHCP and BOOTP Commands and
			for the DHCP Client
	   4.13 NIS and WINS Support		
	5.0 Changes in the Product Architecture       
	6.0 Known Problems
	   6.1 Unable to Run Executables on NFS Mounted Drive If
			"longfilenames=yes"
	   6.2 Using the Network Control Application with the Norton
	   		Desktop Utility and Novell Netware
	   6.3 FTP Server
               6.3.1 FTP Server and Server Control Applications 
	   6.3.2 FTP Server, the DOS SUBST Command, and 
			Windows for Workgroups
	   6.4 Conflict with Afterdark and Windows for Workgroups 
			Network Driver (WINNET.DRV)
	   6.5 Known Problems with Mosaic
	   6.5.1 Mosaic and WIN32S
	   6.5.2 Mosaic Security Protocol Message
	   6.5.3 Mosaic and Austin Computer's DSTN Notebook PCs	 
	   6.5.4 Attempt to Load URL Failed	 
	   6.5.5 Using WWW Mail Forms	   
	   6.6 Interaction Issue in Context-Sensitive Help
               6.6.1 Distorted Groupbox Label
               6.6.2 Interaction with Snap To Feature for Microsoft Mouse
	   6.7 NetWare Server Mapped Disk Access in DOS Session Might
		  	Cause Windows Exit to DOS 
			and Sometimes System Reboot   
	   6.8 TN5250   
	   6.8.1 TN5250 Video Problems
	   6.8.2 WINHLLAPI and Concurrent TN5250 and TN3270 Sessions
	   6.8.3 TN5250 Keyboard Remapping
	   6.8.4 TN5250 DDE Paste-Link
	   6.8.5 TN5250 Connection Problem
	   6.9 Dialer Inactivity Warning Setting
	   6.10 IDNET Incompatibility
	   6.11 Known Problems on Windows 95
	   6.11.1  Using NIS with Windows 95
	   6.11.2  Windows 95 Applications Unable to Connect
	   6.11.3  Using InterDrive 95 and the Client for Microsoft Networks
	   6.12 Mail OnNet
	   6.13 Running the 3c5x9 Packet Driver with 
			Plug and Play
	   6.14 Configuring NIS
	   6.15 Remote Copy Instability
	   6.16 Retriever
	   6.17 Using the FTP Software Network Driver with IBM PC-DOS
	   6.18 Setting Up Online Help on Windows NT Systems
	   6.19 Installing OnNet on Windows NT Systems Over
	   		an Earlier Version of Interdrive
	7.0 Other Issues
	   7.1 Removing the OnNet Kernel from Windows 95 Systems
	   7.2 TNVT
	   7.2.1 Using Automatic Connection in Dialer and TNVT
	   7.2.2 TNVT and Key Mapping
	   7.2.3 TNVT Keyboard Mapping Files
	   7.2.4 TNVT 8-Bit Terminals and Binary Mode
	   7.2.5 TNVT and VT ID Response
	   7.3 TN3270 
	   7.3.1 Running TN3270 on an Application Server
	   7.3.2 TN3270 and HLLAPI
	   7.4 Serial Tuning Guidelines
	   7.5  Ensuring That the Correct Version of WIN32S Is On Your System
	   7.6 Using LWPE Over Netware/IP with an IBM Token Ring Network Card
	   7.7 Correct Syntax for DOS LPRM Command (on CD-ROM only)
	   7.8 Correct Description of Kernel Configuration Parameter
	8.0 Ordering Documentation
	 

  	     	   

1.0  Installing OnNet 

1.1 Installation Requirements

Processor     For the OnNet VxD implementation:
			386 (or higher)

              For the TSR implementation
	      (available on the CD-ROM distribution):                         
		Standard mode: 286 (or higher)=20
		386 Enhanced mode: 386 (or higher)

Memory        Standard Mode: 1 MB				
(RAM)	      386 Enhanced Mode: 8 MB (4 MB if you do not install Mosaic) 
	      NOTE: To install OnNet 2.0 from DOS, you must have 435K of 
	      conventional memory freely available.
	      
Operating     Microsoft Windows Version 3.1		         
Systems       Microsoft Windows for Workgroups Version 3.11 (or higher)
	      Microsoft Windows 95
	      Microsoft Windows NT

Disk Space 	The amount of disk space required is determined by the
components that you elect to install.  The installation program
displays the required disk space for you. 

NOTE: If you have a temporary swap file, the size of the swap file
can increase and prevent the copying of files to your PC.

1.2  Upgrading

If you are upgrading, exit all OnNet Windows applications before you
run SETUP.EXE.  The VxD kernel, VxD NetBIOS, and VxD InterDrive can 
be loaded during the installation without causing problems.

If you do not close all OnNet applications, the installation program
might not copy all of the OnNet components to your PC.

If you have a windows 3.1 or 3.11 system on which you are running 
OnNet 1.2, and  you plan to upgrade to Windows 95 before installing 
OnNet 2.0 on that system, you must remove the OnNet 1.2 installation 
first, before you install OnNet 2.0.

If you install OnNet 2.0 on a system that has Services OnNet 1.1.1 
installed, Services OnNet will not run.

1.3  Upgrading or Reinstalling to a Different Directory

If you upgrade or reinstall to a different directory, and then delete the 
original directory, OnNet applications might fail.

FTP Software, Inc. recommends that you upgrade or reinstall to the
same directory where the previous version resides.  However, if you
upgrade or reinstall to a different directory, do not delete the
original directory before changing references to the new directory and 
moving the following files to the new directory:

* Configuration files, such as NEWS.INI and MAILON.INI.

* Device drivers (for example, packet drivers and NDIS drivers). 
   NOTE:  This item applies only to systems running PC/TCP 
   software version 2.3 or older.

1.4 Upgrading to Switch Between a LAN and Serial Connection

OnNet 2.0  has the ability to switch between a serial and 
a LAN interface. If you want to use this capability, use
the OnNet Custom installation to define both your LAN and
your serial interfaces.

For previous releases, you might have configured your PC to
switch manually between a LAN and a serial connection by using
more than one PCTCP.INI file. If you want to consolidate your
configuration information in one file,  you can copy
appropriate sections of alternative configuration files into your OnNet
PCTCP.INI file.  The sections that you might want to copy are:

[pctcp comscrpt connection]
[pctcp dial connections]
[pctcp interface n]
[pctcp kernel]

If you click a Dialer icon for a previously configured connection,
and if that configuration information is not in your main PCTCP.INI
file, Dialer displays a message to that effect.  To remedy the
situation, reconfigure your connection through Dialer, or update you
PCTCP.INI file as described above.

1.5 Configuring Multiple Interfaces

The OnNet Express installation lets you configure a 
single interface connection, either a LAN interface or 
a serial interface. If you want to configure both interfaces
and switch between them, use the OnNet Custom installation.

After you configure a first interface during the Custom installation,
choose Add from the Network Interface Summary dialog box, then select
Install a New Driver from the Found Existing Driver dialog box.
Respond to the questions in subsequent dialog boxes.

For detailed information about these dialog boxes, see Chapter 3, 
"Installing OnNet and PC/TCP Software," in the Advanced User's Guide.

1.6  Installing Over Windows 95

If you install OnNet 2.0 over Windows 95 when Microsoft's TCP/IP
stack is installed, the Microsoft TCP/IP stack will be detected by
the installation program. You will be prompted to choose whether to
keep the Microsoft kernel or to remove it. If you decide to use the
Microsoft kernel, only OnNet applications and the InterDrive 95
client will be installed. 

To have the following applications installed on Windows 95,
however,  you must install the FTP OnNet 2.0 kernel: DHCP,
Dialer, Internet Registration, IPTrace, NetBIOS, Ping, and 
SNMP MIB II Agent.  

If you choose to use the OnNet kernel instead of the Microsoft
kernel, or if no TCP/IP stack is installed on a system with Windows
95, OnNet installs its own kernel with a 32-bit Winsock
implementation, the OnNet 2.0 applications, and the InterDrive 95
client.

During the installation on a system with Windows 95, the installation 
program might prompt you to insert Windows 95 installation disks to 
install certain drivers; if you are not so prompted, it is because 
those drivers are already installed on your system.

Refer to Section 5 for information about which OnNet DOS 
applications are installed.

1.6.1 InterDrive 95 on Windows 95

The version of InterDrive installed on Windows 95 is a special 32-bit
VxD called InterDrive 95.  To share network files and printers in
Windows 95, you can use standard Windows 95 menus available from
Explorer and Network Neighborhood; therefore, InterDrive 95 does not
provide the OnNet 2.0 Network Control application.

1.6.2  Obtaining IP Configuration Information from a DHCP Server

If you expect to get your Internet Protocol (IP) configuration 
information, such as the IP address for your PC, from a DHCP 
server, you can choose to do so during the OnNet installation.
During the installation, when the IP Configuration dialog box 
appears, select Obtain Configuration From DHCP Server.

Refer to Chapter 3 of the Advanced User's Guide for
more information.

1.7 Installing Over Windows NT

When OnNet 2.0 is installed over Windows NT, the installation program
installs only OnNet applications. All but the following OnNet
applications are installed on Windows NT systems: DHCP, Dialer,
Internet Registration, IP Trace, LPD Print Server, NetBIOS, Network
Control, Network Time, Retriever, and SNMP MIB II agent.

Refer to Section 5 for information about which OnNet DOS applications are
installed.

1.8 Installing MAPI.DLL for Mail OnNet

If you do not remove the additional MAPI.DLL files already on your system 
before beginning the OnNet 2.0 installation, a message displays that 
prompts you to choose between the MAPI.DLL file shipped with OnNet 2.0 
(used by Mail OnNet), and the MAPI.DLL file that is already on your 
system. Select the MAPI.DLL that is shipped in OnNet 2.0, and which
is used by Mail OnNet. This selection will allow the installation of 
Mail OnNet on your system. 

If you begin to experience difficulties while using Mail OnNet 2.0, you 
should remove any MAPI.DLL file that already exists in your C:\WINDOWS 
or C:\WINDOWS\SYSTEM directories, or in any directory that is listed in 
your PATH statement in the AUTOEXEC.BAT  file.

You will not see Mail OnNet as a selection in the Components dialog box.

1.9 OnNet 2.0 and Services OnNet 1.1.1

Do not install OnNet 2.0 on a system that has Services OnNet 1.1.1.
OnNet 2.0 is incompatible with Services OnNet 1.1.1.

1.10 Troubleshooting the Installation

The installation program creates a log file (INSTALL.LOG) that records which
components were installed on the PC. System administrators who understand
the structure of the SETUP.INF and FILES.INF files (as described in Chapter 6,
"Customizing a Centralized Installation and Configuration," of the Advanced
User's Guide) might want to examine the log file in order to troubleshoot any
unexpected results in an installation.

2.0 Before You Start to Use OnNet Applications

Read the following sections before you start using applications in
the OnNet product.

2.1  Before You Start to Use Mail OnNet

2.1.1 Upgrading Mail OnNet Folders

If you are upgrading from a previous version of Mail OnNet, the
application may display a message similar to the following one about 
each of your folders, when you open them for the first time after
the upgrade:

In-Tray format is out of date. Rebuilding list

Mail OnNet 2.0 has a different message index format for mail folders.
This message indicates that Mail OnNet will upgrade the format of
your folders automatically. No messages will be changed or lost. 

2.1.2  Before You View Attachments

Mail OnNet uses components of KEYview version 4.1a as its default file
viewer. If you want to use a different version of KEYview as your
default viewer, or a different  viewer application, you must edit the
MAILON.INI file in your OnNet 2.0 directory to change the default
viewer parameter. The parameter appears in the following
section of the MAILON.INI file:

[Viewers]
default-viewer= c:\pctcp\keyview\keyview4.exe

Replace the pathname specified for the parameter with the pathname of
the viewer application, or with the version of KEYview that you want
to use in place of version 4.1a.
 
2.1.3  Set the TMP Environment Variable for Mail OnNet

You must define the environment variable TMP for Mail OnNet. Add the
following line to your AUTOEXEC.BAT file:

     set TMP=_temp_directory_

where _temp_directory_ is a directory into which Mail OnNet
can put temporary data. An example is:

     set TMP=C:\MAILON\TMP

2.2  Getting Started with TN5250

To start a new emulation session with TN5250, you must first
configure a display session. Otherwise, when you try to create
an emulation session by choosing New from the Session menu,
nothing will happen.

You can think of a display session configuration as a template
for an emulation session. The configuration, or template, holds
information about your monitor (number of columns and color or
monochrome) and the name or IP address of the AS/400 host you
want to connect to.

TN5250 allows the creation of 32 templates and 16 active emulation
sessions. You must create a configuration or template for each
session.  When you start an emulation session over that template, the
template is seized for use by that emulation session only. So be sure
to create enough configurations to handle the number of emulation
sessions you plan to run at one time.

To configure a display session, run the TN5250 Customization program.

To create a new TN5250 display session:

1. Run the Customization program. Double-click the TN5250 Customization
   icon.
   If you have not previously configured a display session, a
   dialog box will give you the opportunity to start the online
   help right away.

2. The Customization window displays a toolbar that contains
   all the icons that you use to configure display sessions.

3. Choose the Display button in the TN5250 Customization window.
   An icon is created.

4. Double-click  the session icon. The TN5250 Customization window opens.

5. In the TN5250 Customization window, configure the session:
   -- Assign a name to the session.
   -- Select the number of columns (80 or 132). If you
      select 132, make sure that the hardware supports 132 columns.
   -- Select the monitor type (monochrome or color).
   -- Assign a hostname or IP address for the session.

6. Choose OK to close the display session.

7. Choose the Save button to save the display session.

8. Close the Customization program. Choose OK to save your changes to
   the display session.

9. Start the TN5250 emulation program by double-clicking its icon
   in the TN5250 program group. See the online help for information
   about using TN5250.

2.3 Converting Customized Keymap Files for TN3270

A conversion tool, FTPCVT.EXE, lets you reuse your customized keymap 
files and sessions from earlier versions of TN3270 with the new 
TN3270 application. 

To run the conversion tool:

1. From the Program Manager File menu, choose Run. 

2. In the Command Line box, type

   <drive>:<onnet dir>\tn3270\ftpcvt.exe

   where <drive> and <onnet dir> are the drive and directory that
   contains OnNet.

   --or--

   Add an icon for the conversion tool to the OnNet program group.

The conversion tool has online help that explains how to use the tool.

The "Getting Started" topic in the online help refers to installing from
disk. Ignore Step 1 (installing from disk), since FTPCVT.EXE is 
installed along with the OnNet 2.0 installation. You can follow 
the rest of the procedure to create an icon for the program group,
if you want.

The online help refers to "connection files"; this is another term
for "session files."

2.4  Using DHCP with Upgrades from OnNet 1.x

If you have a previous version of OnNet on your PC, you must replace
the DHCP Windows application with the VxD DHCP.

NOTE: The DHCP VxD client is intended for use with the OnNet VxD
kernel only.  If you are using the OnNet TSR kernel with Windows, you
will need to use the DOS "dhcp" command after you load the TSR kernel
and before you start Windows.

In OnNet 2.0, the new Windows VxD DHCP client (VDHCP.386) replaces the
Windows DHCP client application (WDHCP.EXE), which was provided in
OnNet 1.x. Although the DHCP client WDHCP.EXE will function over 
the OnNet 2.0 kernel, FTP Software, Inc., strongly recommends you 
replace WDHCP.EXE with the new DHCP VxD client.

To replace the Windows DHCP client WDHCP.EXE with the new DHCP VxD client
(VDHCP.386), follow these steps:

1. If you placed WDCHP in the Windows Startup group, remove WHDCP from 
   that program group.

2. Exit Windows, then unload VXDINIT with the DOS "inet unload" command.

3. If you configured WDHCP to write to the PCTCP.INI file,
   you should edit your PCTCP.INI file and replace the "ip-address="
   parameter written into the section for your interface with the
   following:

     ip-address=0.0.0.0

This change eliminates the possibility of duplicate IP addresses.
A duplicate IP address condition can occur when WDHCP writes the
leased IP address into the "ip-address=" parameter. If the WDHCP
client is restarted after the lease expires, the DHCP server is free
to assign that address to another client, which can result in an
address duplication.

4. In the [pctcp vxdinit] section of your PCTCP.INI file:

    a. Add the "vdhcp=yes" parameter:

       [pctcp vxdinit]
       vdhcp=yes

    b. Remove the "vdhcp=no" parameter if it exists.

5. Run the DOS "vxdinit" command, then start Windows.  
    
   The DHCP VxD client will start automatically.

The VxD DHCP is configured to maximize performance.  See
the Advanced User's Guide for a description of the parameter settings.
Use the Configure application if you want to change any of
 these settings.

2.5  Kernel Name Resolution and Third-Party Applications

To make the TSR kernel smaller, Domain Name System 
(DNS) code was moved out of the kernel into a separate library.

If you are using applications written with the PC/TCP Development Kit
in an earlier version of OnNet that uses the OnNet kernel for
name resolution, keep the following setting in the PCTCP.INI file:

[pctcp kernel] parameter
kernel-does-dns=yes

Setting this parameter to "no" shrinks the kernel by 6.5K.  
Set this parameter to "no" if you do not use old applications that 
require DNS support in the TSR kernel, and you want to free more 
low DOS memory.

2.6  TN Negotiating the X-Display Option

If you have an X-server running on your system, DOS TN.EXE should
negotiate the X-display option.  If it does not, set the following setting
in your PCTCP.INI file:

[pctcp kernel]
pktdrv-loopback=yes

2.7  Resizing the TNVT Scrollback Buffer

When you reset the size of the TNVT scrollback buffer, TNVT 
retains (or saves) only one screen of data containing the last 25 lines
of the scrollback buffer.  Additional lines, previously in your scrollback
buffer are lost,  The 25 lines that are saved, are the first 25 lines in
the new buffer.

By saving only 25 lines when you reset the scrollback buffer,
memory resources are made available for other applications.

2.8  InterDrive and Hidden Directories on Some UNIX Systems

On some UNIX systems, when a directory's sticky bit is set, the directory
is hidden at the system level.  The system appends a plus sign (+) to the 
name of the directory and then hides that directory from standard listing 
commands, such as LS, FTP, and NFS.  Once you have marked a directory 
as hidden using File Manager, you will no longer be able to see the 
directory to change it back, since the directory has been renamed and the 
directory is no longer visible to NFS.

Note that since the directory has been renamed, it is possible to create
a file with the same name that the directory previously was using so it
appears that the directory and all of its contents have been
permanently deleted. The directory is still there, and the FSCK command
will show nothing out of the ordinary.

If you want to recover the directory, log in to the UNIX machine with
TN or TNVT and unset the sticky bit on the directory, as follows:

chmod -s temp+		where "temp" is the name of the
				directory.

Because of this behavior, do not attempt to hide directories within 
File Manager on these UNIX systems.  On standard UNIX systems, 
the directory will not disappear or be renamed, but will simply have 
the sticky bit set. 

2.9  Listed Router Address over a Serial Line

When you use a SLIP or a PPP connection, the Dialer
sets the router's IP address to an arbitrary, fixed value (1.1.1.1).
For a serial connection, this value has no meaning, but merely
serves as a placeholder in the router table.  Values for the router
and subnet mask that are reported by the Statistics tool can be
safely ignored when you are using a serial connection.

2.10 Before You Start to Use SOCKS Security

You must do a custom installation to install SOCKS support.
Refer to the Advanced User's Guide for information about configuring
SOCKS.

The installation program searches for a SOCKS.CNF (SOCKS configuration) 
file on your PC.  If a SOCKS.CNF file is not found, the program copies
a template file named  SOCKS.TXT to your PC.  You can find this file
in the directory identified by the "etc-dir=" entry in the [pctcp general]
section of your PCTCP.INI configuration file.  

Edit the SOCKS.TXT file to provide SOCKS configuration information; 
then rename this file SOCKS.CNF. Refer to the Advanced User's Guide
for more information about the SOCKS.CNF file.

2.10.1 Before You Start to Use SOCKS Security with X OnNet

Before you start to use SOCKS security with any X server application,
such as X OnNet, you must enter a line in your SOCKS.CNF file to
avoid using the SOCKS server for X server connections. For example,
if the remote client that your X OnNet application (or other X server
application) is going to connect to has the IP address 128.127.50.23,
enter the following line into your SOCKS.CNF file:

direct 128.127.50.23 255.255.255.255

This line in your SOCKS.CNF file allows X OnNet to connect 
to the remote system directly, instead of through a SOCKS server.

To connect TCP client applications running on your system 
with their corresponding services running on a remote system, you 
can by-pass SOCKS security and connect to the remote system
directly by entering a line for the direct connection into your 
SOCKS.CNF file. For example, if you want to use REXEC to 
initiate a connection with the remote system whose IP address 
is 128.127.50.50, enter this line into your SOCKS.CNF file:

direct 128.127.50.50 255.255.255.255 eq exec

You can substitute the well known, established port number 
in place of the service name--for example, you could enter the line:

direct 128.127.50.50 255.255.255.255 eq 512

where 512 is the port number used in place of a service name.


2.11   Changed Command Line Syntax for FTP

The WFTP.EXE command line syntax has changed for this release. 

You must convert any pre-existing FTP command files to use the new FTP
command line syntax.

This is the new syntax

  wftp.exe [-s session_name] [-d] [-u user_name] [-k password] 
           [-p port_number] [-h (hostname | IPaddress)] [FTP_command]

To specify a remote hostname, enter this: -h hostname
Not this: -h hostname   hostname

To specify your password, enter this:  -k password      
Not this: -u username [password]

For a detailed description on the new command line syntax see the FTP online
Help topic, "What is an FTP Command Line?"

2.12  WFTPLIB.DLL and WTELNET.DLL Are No Longer Shipped with OnNet

As of OnNet 2.0, the files WFTPLIB.DLL and WTELNET.DLL 
are no longer shipped with OnNet, and have been replaced by
WSFTPLIB.DLL and WSTELNET.DLL, respectively. The
new files use the Winsock interface.

If you have developed an application that uses WFTPLIB.DLL
or WTELNET.DLL, you must convert your application to use
the new .DLL files. For more information on converting your
application, refer to the OnNet Developer's Toolkit Release 3.1
Application API manual.

3.0 New Applications in OnNet 2.0 

OnNet provides a set of new Windows applications to help you with
your networking tasks and to let you access Internet resources.

Mosaic
Gopher+ 
News 
TN5250
Print Client
IPTrace
KEYview
Internet Registration 
Retriever 

Refer to Using OnNet for Windows, the Advanced User's Guide, and the
online Help for more information.

4.0 New Functionality in OnNet 2.0   

4.1  New Context-Sensitive Online Help 

Many applications in this release have context-sensitive Help, an
improved Help system that gives you all of the information that you
need to use an application. Clicking the right mouse button provides
information for the control or entry field where you are working in a
dialog box. 

 Help also provides:

* Step-by-step procedures to help you use an application.
* Explanations of relevant concepts.
* A graphical contents page that provides quick access to information
  that you need.
* Full-text search and retrieval to help you find information that
  you need.

Refer to section 6.6 of this document for more information.

4.2  New TN3270

The TN3270 product that shipped with earlier versions of OnNet has 
been replaced by a new, enhanced TN3270 product. The TN3270 terminal 
emulator for OnNet 2.0 supports the IND$FILE protocol for file transfer, 
3287 printer emulation for printing files on the host from your PC, 
WINHLLAPI calls for programming, Dynamic Data Exchange (DDE) links, 
and a powerful scripting language---with a learn mode---for creating 
your own scripts, such as for logging on to the host.

4.3  New Mail OnNet Features

- The User Interface of Mail OnNet has been revised for version 2.0.  
  You can now change the Mail OnNet configuration from the Mail OnNet 
  Settings menu. 

- Mail OnNet now supports automatic tasks that let you file and organize 
  your messages better.
  
4.4  New Dialer Features

- Dialer now supports high-speed ISDN telephone line connections.
   
   To use ISDN your PC must have the appropriate hardware that
   supports a WINISDN interface. FTP has tested ISDN support with
   ISDN*tek hardware.
  
- Dialer now supports automatic network connection.

When you enable automatic network connection, network applications connect
to the network only as needed. This feature lets you minimize network 
access charges when you connect to the network through a network service 
provider.

4.5  New TNVT Features

- TNVT now supports the SCO-ANSI and VT320 terminal types. 

- TNVT provides support for international keyboards and lets you easily remap
non-English keyboards.  

- New scripting lets you automate routine tasks.  TNVT can create a
script file of your routine TNVT tasks.

4.6  Redesigned FTP Application

The user interface has been significantly improved:

- It provides toolbar buttons for commonly used commands.

- A graphical display of remote and local directories gives the
  application a File Manager look and feel.

-  Most commands provide a drag-right option for specifying  
   the local or remote host session.

-  The File Open command now lets you create a New session.

- It now automatically determines the remote host operating system
   type for remote hosts that support this feature. Remote hosts must
   interpret the SYST command for FTP to determine the type of operating
   system running on the remote host.

- FTP now displays files through the KEYview file viewer application.
(If KEYview is not installed, FTP uses Windows Notepad.) 

- FTP now transfers files in Binary mode (not ASCII) by default.

- You can now minimize FTP while an FTP command file (.TAK file)
   is running. 

This feature lets you use an FTP connection only as needed.
For example, you can run a .TAK file to transfer a file from a remote host at
9:00 daily, and then maximize the FTP icon later if your need to transfer
other files to or from the remote host.

4.7 New Statistics Features

- Session support

You can define the text and graph views and save these settings to a
session. After you save a session, you can reopen and change that
session.  The Session menu replaces the File menu.

- Provides statistics for a serial interface.

- User Interface Enhancements

Statistics provides a toolbar that lets you quickly access frequently
used Statistics commands.  It also provides a status bar for the
display of informative messages.  

A new Graph menu contains the graph customization commands. These
commands were previously in the Settings menu.

The Settings menu provides entries for setting the polling interval,
and for displaying or hiding the toolbar and status bar.

4.8 New Network Control and FTP Software Network Driver Features 

This section applies only when running these programs over Windows 3.1
or Windows for Workgroups 3.11 (or higher). 

4.8.1 Logging In to Network Control and the 
FTP Software Network Driver Connections

The FTP Software Network Driver now prompts for your
network username and password automatically, if InterDrive 
is running when Windows starts. It saves the pair as your
default login information for all subsequent connections to
NFS file systems and printers. It also restores all permanent 
connections, if they do not already exist. 

To disable the automatic login feature, use the Configure
utility to change the InterDrive Fine Tuning parameter called
Automatic Login.  Or, specify "autologin=no" in the [pctcp idrive]
section of your PCTCP.INI file. You might want to do this if you
do not use NFS file sharing and you use only LPR print redirection
from Windows.

4.8.2 Network Control and FTP Software Network Driver:
Changes to Saved Connection Information  
	   
The FTP Software Network Driver no longer automatically saves every
connection that you make.  

Always Make Permanent is disabled by default; and file system and
printer connections that you make by browsing or by directly typing a
network path last only as long as InterDrive is running. If you
decide that you want to save a temporary connection, you can do so by
selecting it, choosing Drive Options or Printer Options from the
Settings menu, then choosing OK.

The recommended way to define and save connections for reuse is to
choose any of the New... commands from the Session menu in the
Connect a Drive or Connect a Printer dialog box.

4.8.3 Network Control: Changes to the Functions Available 
Through the Network Button or the Network Icon 

Choosing the Network button in Network Control or the
Network icon in Control Panel displays the InterDrive options dialog
box, from which you can view and change InterDrive settings. You can
find other functions formerly available through the Network icon as
follows: 

- Login and Logout are now commands on the Session menu in
the Connect a Drive and Connect a Printer dialog boxes.  

- The ability to set default file permissions for a selected file
system is available through the Permissions command on the Settings
menu in the Connect a Drive dialog box.

4.8.4 Network Control: Deleting Inactive Connections 

You can now delete selected, inactive connections using the Delete
Connection command from the Session menu. The previously supported
method of using the Delete key on your keyboard also still works.

4.8.5 Network Control: Preventing Filename Mapping on a CD-ROM Drive

You can prevent filename mapping in a file system on a CD-ROM drive
by selecting the Advanced option called Mount CD-ROM in the Configure
Drive dialog box.

4.8.6 Network Control and FTP Software Network Driver:
Turning Autotuning On and Off

You can turn autotuning on and off for a specific file system by
selecting the Advanced option called Autotune in the Configure Drive
dialog box. 

With autotuning on, InterDrive automatically adjusts read and write
size based on network capacity, kernel configuration, and other
factors, and uses the specified values as maximums. With autotuning
off, read and write size remain constant, as specified.

4.8.7 Network Control: Changing Connection Information

You can no longer change the name of currently connected file
systems and printers, and you cannot change the username for a
currently connected NFS printer. You should disconnect the
connection, change the information, then reconnect.

4.8.8 FTP Software Network Driver: Enabling Symbolic Links 

You can enable and disable symbolic link processing with a new
checkbox in the InterDrive Options dialog box. You can also change
this setting for a specific file system using the Configure Drive
dialog box.

4.8.9 Network Control and FTP Software Network Driver:
User Interface Changes

- The User Information command is no longer available from the
Settings menu. To change your default username and password, choose
Login from the Session menu.

- Show Long Filenames has moved from the InterDrive options dialog box
to a command on the Settings menu.

- The format of connection listings in the Connect a Drive and Connect
a Printer dialog boxes has changed. 

Information is now displayed in the following order, from left to right:
o  Local drive letter or redirected printer port
o  (P) indicating whether the connection is permanent
o  printer type (for print connections only)
o  print session or file system name
o  network path

The new format, with network path appearing last, allows for the display
of longer network paths (long paths were previously truncated).

4.9 New Network Control and FTP Software Network Driver Printing
	    Features

4.9.1 Setting When to Print Options

You can no longer set When to Print options from the Configure NFS
Printer dialog box. These options apply to NFS printing from DOS
only, and a DOS graphical user interface is now available to set
them. Type "idnet" at the DOS prompt to start and use the DOS interface.

4.9.2 Change to the Print Queues Dialog Box 

An Other NOS button is available in the Print Queues dialog box so
that you can go directly from this dialog box to the print queue
information of another network operating system. 

4.10   SOCKS Support 

Support for SOCKS security is provided in the TNVT, FTP, and
Mosaic applications.  If your network uses SOCKS security to protect
your network, you can choose SOCKS in the custom installation
program, then configure SOCKS on your PC.  

SOCKS implementation in the OnNet WinSock has transparent SOCKS
support so that any WinSock applications that uses TCP as 
the transport layer uses SOCKS automatically when running over 
the OnNet WinSock.

4.11   New Kernel Features

4.11.1 Switching Between a SLIP (or PPP) Kernel and a LAN Kernel

You can configure both a serial (SLIP or PPP) connection and a LAN
connection for your PC. When you use OnNet, it will use the LAN
configuration, unless you have made a dial-in connection.  If you
are connected with a modem, OnNet uses the serial configuration.

4.11.2 ISDN Support for the Serial VxD Kernel

OnNet now supports high-speed ISDN telephone line connections. 

4.11.3 WINISDN.DLL Support

FTP Software has tested with and verified that the
following ISDN hardware vendors' WINISDN.DLL
implementations work with OnNet 2.0:

- ISDN*tek Cyberspace Freedom Series cards
- ISDN Systems Corporation SecureLink II ISDN Adapter with 
  software version 3.11t or greater

4.11.4 VxD Kernel Support for the NetWare IP 2.0 Interface

LWPE.COM now interoperates well  with the VxD kernel. 

Related changes:

The [pctcp lwpe] section of the PCTCP.INI file no longer requires
a "config-path=" entry. LWPE.COM now obtains the information from the 
NET.CFG file. 

To use LWPE.COM in Windows, for reliable exit from Windows, "configure
stacks=9, 512" in your CONFIG.SYS file.

To enable VxD support for NetWare/IP, add "vlwpe=yes" to the [pctcp vxdinit]  
section of PCTCP.INI.        
                                   
4.12 DHCP Improvements

A VxD DHCP replaces the DHCP Client (WDHCP.EXE).  The DHCP VxD
provides a more seamless integration of DHCP functionality with the
OnNet VxD kernel, and other VxD components.

OnNet that is distributed on CD-ROM also provides a TSR DHCP.  This
component provides automatic lease renewal functionality.  Use the
DHCP TSR only with the TSR kernel (available only on the CD-ROM
distribution). To use the DHCP TSR component, you use the dhcp
command at the DOS prompt.

4.12.1  Writing dhcp and bootp Configuration Parameters to the
         PCTCP.INI Configuration File 

In OnNet 1.2, the DHCP and bootp clients for DOS were changed to
default to not writing configuration parameters to the configuration
(PCTCP.INI) file, without any documented means for altering this behavior.
For OnNet 2.0, the dhcp and bootp commands provide a -w command line
option for writing to the configuration file.

4.12.2 Updated List of Configuration File Parameters for the DHCP
        and BOOTP Commands and for the DHCP Client (in Windows) 

See the DHCP and bootp documentation in the Advanced User's Guide
for this information.

4.13 NIS and WINS Support

OnNet now provides NIS (Network Information Service) and 
WINS (Windows Internet Name Server) support.

WINS from Microsoft requires OnNet 2.0 and VNBEP.386. At
least one Windows NT advanced server with WINS support must
be installed.

To enable WINS support, add the following lines to the
[pctcp netbios-vxd] section of the PCTCP.INI file:

Node-type=H
NBNS-servers-file=pathname

where pathname is the full path and filename of the file
containing the IP address of the WINS computer.


5.0  Changes in the Product Architecture       

The OnNet for Windows Version 2.0 product that is distributed on
CD-ROM provides a full suite of OnNet Windows and DOS applications.
It also provides TSR (terminate-and-stay-resident) kernels, NetBIOS,
InterDrive and DHCP, as well as the VxD version of these components.

On systems running the OnNet kernel over Windows 95, however, the
following OnNet DOS applications distributed on CD-ROM will NOT be
installed:

bootp			idumnt
comscrpt		lwpe
dhcp			NetBIOS
dopredir		onpredir
idprint			predir
idmnt			snmp
idnet

The OnNet for Windows Version 2.0 product that is distributed on
disks provides a complete suite of networking applications for
Windows. It also provides VxD versions of kernels, InterDrive,
NetBIOS, and DHCP, as well as a limited set of networking commands
for DOS. The OnNet DOS applications in the disks release are:

bootp*			dos2unix				
dhcp*			unix2dos
ftpver			idchmod	
idconfig	        idconfig
inet			idls
kdestroy		idprint*
kinit			idmnt*
klist			idumnt*
kpasswd			idutil
lpr
lpq
lprm			
pctcpcfg
rmt
sc			
tar
tnglass			
tftp
ping

*These applications are NOT installed on systems running the OnNet
kernel over Windows 95.

If you have a previous version of PC/TCP or OnNet installed on your
PC, you can use the networking applications for DOS that were
available with that product.

6.0 Known Problems

The following items are known problems with this release of OnNet.

6.1 Unable to Run Executables on NFS Mounted Drive If "longfilenames=yes"

Mapped files will lose the UPPERCASE extension if 
map-lowercase=NO (or the lowercase extension if 
map-lowercase=YES).  Consequently, .BAT, .COM, and .EXE
files will not run.  This is true regardless of the longfilenames
setting, since DOS ultimately uses the mapped name.


6.2  Using PC/TCP Network Control with the Norton Desktop Utility 
      and Novell NetWare

The PC/TCP Network Control application does not work when 
used with both the Norton Desktop utility and Novell NetWare.  
FTP Software, Inc. is pursuing a solution from Symantec
Corporation, developers of the Norton Desktop utility.

6.3  FTP Server 

6.3.1 FTP Server and Server Control Applications 

If you have a file transfer in progress with the Windows FTP Server,
and you attempt to close the Server Control application, Server
Control will not exit cleanly, and you will not be able to reload
Server Control and the servers later.

If you are using the FTP server and have an active file transfer in
progress, first stop the Windows FTP Server, then exit the Server
Control application.

6.3.2 FTP Server, the DOS SUBST Command, and Windows for 
Workgroups

The Windows FTP Server requires the use of the DOS SUBST 
command to limit FTP access to directories; however, the SUBST 
command prevents Windows for Workgroups from starting if 
32-bit disk access is enabled.

6.4 Conflict with Afterdark and Windows For Workgroups
Network Driver (WINNET.DRV)

In Windows, if you have Afterdark enabled, there might be a conflict 
with pctcpnet that might cause the Windows for Workgroups (WfW) 
network file/printer sharing not to work. The workaround is to 
comment out "afterdark" in the SYSTEM.INI file.

6.5 Know Problems with Mosaic

The following sections detail situations that you might encounter
when using Mosaic.

6.5.1 Mosaic and WIN32S

The version of WIN32S shipped with OnNet 2.0 is 1.25.141.0.

When starting Mosaic, a dialog box might appear with one of the
following messages:

     WIN32S Error,
     W32XXX ....

This problem is caused by a version skew in the installed Win32s
subsystem. One or more of the Win32s files in the WINDOWS\SYSTEM or
WINDOWS\SYSTEM\WIN32S directories had "read-only" file protection,
and OnNet's installation program could not update them. The
simplest solution is to make sure that there are NO read-only files
in these two directories.  First, relocate to each of these
directories and run the following command:

ATTRIB -R *.*

Afterwards, reinstall OnNet.

Installing other applications that install Win32s after you install
OnNet can overwrite the version on Win32s that OnNet installed.  To
prevent version skew for OnNet applications, you might need to
re-install OnNet.

When starting Mosaic, a dialog box might appear to display the message

     GROWSTUB
     An error has occurred in your application.
     ....
     ....

The growstub problem is due to a bug in some versions of the Windows
mouse driver (\WINDOWS\SYSTEM\MOUSE.DRV) on some systems. To work
around this problem, remove the POINTER.EXE argument from the LOAD=
line in the  \WINDOWS\WIN.INI file. For example, change

     [windows]
     load=c:\windows\system\pointer.exe
     
     to
     
     [windows]
     load=
	   
6.5.2  Mosaic Security Protocol Message

If you get the following message when you start Mosaic

Could not find DLL for Security Protocol Module:
Digest= Digest_load, digest.dll

you must edit your EMOSAIC.INI file to stop your PC from displaying
this message when you start Mosaic. In the [SecurityProtocols]
section, remove (or comment out) the following line:

Digest=Digest_Load, digest.dll

6.5.3  Mosaic and Austin Computer's DSTN Notebook PCs

Austin Computer's DSTN notebook PCs ship with an old Western Digital
640x480 256-color video driver. This outdated driver causes
corruption of the Mosaic display during the scrolling of 256-color
images in the Mosaic window.  Updating the driver to the newer
version 2.3 resolves the problem. The new Western Digital drivers are
available from Austin Computer's electronic Bulletin Board Service
(BBS), at (512) 339-3582, in the self-extracting zip file named
WDVGAWIN.EXE.

6.5.4  Attempt to Load URL Failed

NOTE:  Some sites are so busy, you might need to try at
another time.

1. Check the connection to the network.

2. Check memory. 

6.5.5 Using WWW Mail Forms
 
If you try to send a WWW mail form in Mosaic, the hourglass appears,  To
remove the hourglass and send the form, press the ESC key.

6.6 Interaction Issues in Context-Sensitive Help

6.6.1 Distorted Groupbox Label 

The label text of a groupbox might appear distorted under certain
circumstances after you view, and then dismiss, a context-sensitive
help popup. This is caused by a low-level bug in the way Windows 
refreshes the window when the popup help is dismissed, and is 
not harmful.  The distorted text can be cleared, if desired, by 
forcing a screen refresh (for example, minimizing and then restoring 
the window).

6.6.2 Interaction with Snap To Feature for Microsoft Mouse 

Context-sensitive Help is unpredictable when the Snap To feature is enabled
in Microsoft Mouse Version 9.0.

With Snap To enabled, the mouse pointer jumps to the default button of any
dialog box.  Clicking the right mouse button for context sensitive Help
produces a Help message for the default button, regardless of which field
or item you point to or click.

6.7 NetWare Server Mapped Disk Access in DOS Session Might Cause
Windows Exit to DOS and Sometimes System Reboot   
   
The problem is related to packet burst support being enabled.  This
is the default on NetWare/IP installation.  To work around this,
disable packet burst support by placing the following entry in the
NET.CFG file under the section "NetWare DOS Requester" as follows:  

    NetWare DOS Requester                                                     
        PB BUFFERS 0                                                          

6.8   TN5250

6.8.1  TN5250 Video Problems

Some video drivers might not display the status line or toolbar icons
properly.  One driver with known problems is the CL-GD5434 Windows
3.1 drivers v1.01.  Workaround: Change the driver to Super VGA,
1024x768, 256-color large fonts.  To test the compatibility of the
video driver being used, use one of the standard Windows drivers that
shipped with Windows, for example, the VGA or Super VGA driver. If
the problem no longer occurs when you are using the standard Windows
video driver, contact the vendor for an updated version of the driver
or obtain the proper driver from the Windows Driver Library (WDL).

6.8.2 WINHLLAPI and Concurrent TN5250 and TN3270 Sessions 

You can run TN3270 and TN5250 emulation sessions concurrently, 
with one exception: when your 3270 or 5250 application uses 
WINHLLAPI calls. The second application that you start will use 
the .DLL that was started with the first application. 

There is a switch that you can use when you start TN5250 so that 
WINHLLAPI is not loaded. To start TN5250 without WINHLLAPI, from 
the Windows File menu choose Run. In the text box enter the following:

run tn5250.exe /x <session_name>

Note that /x must be the first token in the command line.

6.8.3 TN5250 Keyboard Mapping

It is recommended that you keep the host function "Error Reset"
mapped to the LEFT-CONTROL key. The LEFT-CONTROL key is used in
Display Write to select ALT key or CMD key options. If you 
override this LEFT-CONTROL key mapping, you will lose this
Display Write functionality. Also, if you remap Windows 
accelerators, such as ALT+TAB or ALT+F4, Windows functionality
will be lost.


6.8.4 TN5250 DDE Paste-Link

For new sessions that have the name SessionN (where N is a number):
Before creating a DDE paste-link to a new FTP software display
session, you must save the session, end the session, and then 
open it again for the paste-link to work correctly. 

After establishing a DDE paste-link, do not rename the session or
the link will fail. If you wish to rename the session, terminate
the link, save the session, end the session, and then open
the renamed session and re-establish the paste-link.

6.8.5 TN5250 Connection Difficulty

If you have difficulties connecting to a remote host using TN5250, a
workaround might be to change the setting of the "do-slow-start="
parameter in the [pctcp kernel] section to NO:

[pctcp kernel]
do-slow-start=no

Try this setting even if you are using TN5250 over a SLIP or PPP connection.

6.9  Dialer Inactivity Warning Setting

In Dialer, if the inactivity warning is set to the same value as the
inactivity timeout, the inactivity warning dialog box is always
displayed.  If there is any network activity, the dialog box will
appear to flash.

When setting the inactivity warning and inactivity timeout, ensure
there is a significant difference in these two values to prevent this
problem.

6.10  IDNET Incompatibility

The IDNET application is not included in OnNet 2.0 distributed on
disks. If you install over a previous version of OnNet, the
IDNET.EXE and IDNET.HLP files from the previous release remain
on your system.  The previous release version of these two files
are incompatible with OnNet 2.0. Make certain that IDNET.EXE 
and IDNET.HLP have been deleted from your PC.
 
6.11  Known Problems on Windows 95
 
6.11.1   Using NIS with Windows 95

If you run OnNet on Windows 95, and configure NIS support, you must
also configure a domain name server for NIS support to work. To
configure a DNS server in the PCTCP.INI file, add this entry to the
[pctcp addresses] section:

[pctcp addresses]
domain-name-server=<IP_address>

where <IP_address> is the IP address (for example, 128.127.50.100) of
your DNS server.


6.11.2  Windows 95 Applications Unable to Connect

On PCs running a version of Windows 95 that was released
prior to the Windows 95 Build 490, you might find
that some applications, such as Mosaic and Gopher+, 
do not connect.

If you receive a message that an application cannot connect, you
need to verify if two files were renamed by the OnNet installation.
If these files have not been renamed, you must rename these files
in DOS.

1. Search your Windows 95 \WINDOWS directory for
WINSOCK.DLL, and your \WINDOWS\SYSTEM directory 
for WSOCK32.DLL.

If these files are present, you need to rename them.  If they are
already renamed, using the .MS extension, you do not need to complete
the following steps.

2. Boot to DOS.

a. Run Shutdown. 
b. In the Shut Down Windows dialog box,
choose Restart the Computer in MS-DOS mode.
c. Choose Yes.

The computer restarts at a DOS prompt.

3. Move to your \WINDOWS directory.
Rename the WINSOCK.DLL file to WINSOCK.MS

4. Move to your 	\WINDOWS\SYSTEM directory.
Rename WSOCK32.DLL to WSOCK32.MS.

5. Restart Windows.

Your applications should be able to connect.

6.11.3  Using InterDrive 95 and the Client for Microsoft Networks

InterDrive 95 is supported on Windows 95 build 950 or later, but
might not work properly on builds prior to 950. InterDrive 95 will
not work properly on builds 480 through 490 if you are also running
the Client for Microsoft Networks.

To verify which build you are using:

1.  Right-click the My Computer icon.

2. In the menu that appears, click Properties. The build number is the
    last three digits of the version number.

6.12   Mail OnNet

Mail OnNet requires the MAPI.DLL that is shipped with OnNet 2.0 to run. You
cannot use the MAPI.DLL provided by Microsoft and still be able to 
run Mail OnNet. No other MAPI.DLL can appear in your PATH statement 
in the AUTOEXEC.BAT file, or in the C:\WINDOWS or C:\WINDOWS\SYSTEM 
directories.

If you log in to Mail OnNet, then log out again, 2-3% of system
resources might be left in use as a result. To work around this
situation, you can either leave Mail OnNet minimized on your Desktop
and running in the background, or you can restart Windows after
logging out of Mail OnNet.

If you delete a folder that contains no messages, but does contain
other folders which are not empty, be aware that Mail OnNet will
delete all of the folders contained in the folder you are deleting,
as well as the folder itself, and you will not be prompted first to
confirm that each subfolder be deleted.

If you are using the Display Names list of the address book to insert
addresses into the To: or the Cc: headers of a message in a Compose
window, you might only be able to insert 5 names or addresses at a
time.  After selecting 5 names from the address book, you will have
to exit from the address book, then choose Addresses to re-enter the
address book to select more names. As an alternative, you can type
the names into the To: or Cc: headers yourself without using the
address book.

6.13  Running the 3c5x9 Packet Driver with Plug and Play

If you have Plug and Play enabled on your PC, and run the 3c5x9
packet driver (3C5X9PD.COM), you system can become unstable,
requiring a system reset to recover. 

To run the 3c5x9 packet driver, disable Plug and Play on the 3c5x9 board.
See your product documentation for information about changing this
setting.

6.14  Configuring NIS

When you configure NIS on your system, the configuration
program does not insert the correct entries in the PCTCP.INI file.
To use NIS, add the following section to the [pctcp addresses]
section of your PCTCP.INI file:

	nis-server=<server_name>

Also replace the entry name-resolution=NIS, with

	name-resolution=nis

6.15  Remote Copy Instability

Attempting to use Remote Copy without a password might cause the
application to cause a General Protection Fault (GPF).  If you
encounter this situation, you can enter a null password and connect
to the remote host. 

6.16  Retriever 

Retriever does not run on the Windows NT kernel for this release. 
Retriever is not installed on Windows NT systems.

6.17  Using the FTP Software Network Driver with IBM PC-DOS

If you are using the FTP Software Network Driver on a PC that is
running IBM PC-DOS, certain operations may fail, due to conventional
memory allocation problems. Due to faulty interactions between
Windows and PC-DOS, memory allocations can sometimes fail even if
your PC appears to have enough memory. The problem can manifest
itself as a failure to restore permanent connections, or as a message
reporting that InterDrive is not loaded (even though you know that
you have loaded it).

If you suspect that memory allocation problems are causing difficulties
with the Network Driver, free some conventional memory by unloading
any unnecessary drivers or TSRs before you start Windows.

6.18 Setting Up Online Help on Windows NT Systems

If a user installs OnNet 2.0 on a Windows NT system where multiple
users expect to use the OnNet applications, currently only
the first user will be able to use the online help for those applications.
The other users have to install OnNet on the same system themselves
to be able to use the online Help. In addition, if the first user has 
NT Administrator privileges, each additional user sees both
the common group of applications installed by the first
user and the private group that the additional user just installed.

To correct this situation, FTP Software has developed a utility that 
NT Administrators can give to the non-Administrator users of
their NT systems. If the non-Administrator users run the utility after the
NT Administrator installs OnNet 2.0 on their NT system, the NT Registry
will have the appropriate values set up for each of them. To obtain
the utility, contact your FTP Software Technical Support representative.

6.19 Installing OnNet on Windows NT Over an Earlier Version of Interdrive

If OnNet 2.0 is installed on a Windows NT system on which a Beta
version of InterDrive NT is already running, the installation will hang 
after the step that updates the AUTOEXEC.BAT file. The workaround 
is to remove the Beta version of InterDrive NT before you run the 
OnNet 2.0 installation.

7.0 Other Issues

7.1 Removing the OnNet 2.0 Kernel from Windows 95 Systems

If you decide to remove OnNet 2.0 from a Windows 95 system, 
be aware that you can only remove the installed OnNet protocol stack 
and NFS stack from the Windows 95 Network Control Panel. 
This process does not remove OnNet entries from such files 
as SYSTEM.INI, WIN.INI, and AUTOEXEC.BAT; you 
must remove these entries manually.

If you want to remove the OnNet kernel from a system running
Windows 95, follow this procedure:

1. Click the Windows 95 Control Panel's Network icon to display 
    the Network Control Panel window.

2. In the Configuration dialog box, remove all FTP entries from the 
    displayed list of installed network components. When you are 
    finished, choose OK and exit the Network Control Panel.

3. Edit the WIN.INI file on your system to remove the KEYview
    pathname from the "load=" parameter. For example, you 
    would remove C:\PCTCP\KEYVIEW\KWLDMGR.EXE 
    from the following parameter:

	load = c:\mouse\xpoint.exe c:\pctcp\keyview\kwldmgr.exe

4. Edit the WINFILE.INI file and remove the entire "KEYview=" parameter:

	KEYview = c:\pctcp\keyview\kvfm.dll

5. In your AUTOEXEC.BAT file, remove the line that initializes
    the VxD kernel from your OnNet 2.0 directory. For example,
    remove the line:

	c:\pctcp\vxdinit.exe

6. Rename the WINSOCK.DLL file in the OnNet 2.0 directory, so that
    your applications will use the Microsoft WINSOCK.DLL 
    file once you reboot your system.

7. Reboot your system afterwards for your changes to take effect.

7.2  TNVT

7.2.1 Using Automatic Connection in Dialer and TNVT

When you use TNVT together with the Automatic Connection
feature of Dialer, what happens after the connection
disconnects due to a connection timeout depends on whether 
you are using a  PPP or an ISDN line. The different behavior 
is due to the way each responds when a server goes down. 
With ISDN, you must  close the disconnected TNVT session 
and remake a connection.  Over a PPP connection, you are 
able to reconnect for a short  time after a timeout 
without having to log in again.

7.2.2 TNVT and Key Mapping

If you remap a Windows Hot Key, you get both the mappings for
the Hot Key and for the session. 

7.2.3  TNVT Keyboard Mapping Files

Previously, TNVT searched for default keyboard remapping (.DKY) files in the
directory pointed to by the PCTCP environment variable.

Now TNVT searches for these files using the MS Windows API OpenFile, which
searches for files in this order: 

1. The current directory.

2. The Windows directory.

3. The Windows system directory.

4. The directory containing the executable file for the current task. (This is
where TNVT will find the files if the user has done a standard install and has
not moved these files.)

5. The directories listed in the PATH environment variable.

6. The list of directories mapped in a network.

7.2.4  TNVT 8-Bit Terminals and Binary Mode

When 8-bit terminals are selected, the default for TNVT is to use
Binary mode. If you encounter difficulties, try deselecting the Use
Binary Mode with 8-Bit option. Formerly, the solution was to deselect
the Allow VT220 8-Bit option. Now you can have 8-bit TNVT terminals
without binary mode.

All 8-bit TNVT sessions default to Binary mode. If this causes a
problem with the host, use the method described in the previous
paragraph.

7.2.5  TNVT VT ID Response

Now that the VT320 terminal is available, the VT ID box, its
functionality, and the setting name have all been changed. The
"vt220_id" setting saved in SESSION.INI is now "vt -id."  This
setting can be set manually to any of the three IDs, at any time
before or during a session.

7.3 TN3270

7.3.1  Running TN3270 on an Application Server

To run TN3270 on an application server:

1. Install TN3270 on the application server.

2. In the [System Info] section of the TN3270.INI file, set the 
   shared version to 1, as follows:
   [System Info]
   Shared Version=1

3. Copy the TN3270.INI and TN3270.CFG  files from the application 
    server to the client's WINDOWS directory. Edit the TN3270.INI 
    file to customize directories and paths as appropriate for your 
    environment.

7.3.2  TN3270 and HLLAPI

TN3270 supports both EEHLLAPI (level 1.2) with RHLLAPI.DLL
and Windows High Level Language Application Program
Interface (HLLAPI) version 1.1 with WHLLAPI.DLL. 

To use RHLLAPI.DLL, you must initialize the HLLAPI interface
in one of two ways.

-  Load TN3270 with the /i startup option to activate the API
   portion of TN3270. For example:
	TN3270 /i

- HLLAPI sessions can be brought online with Script 
  commands anytime during a 3270 session or by an 
  initialization script.

  The following command line automatically invokes an
  initialization script.:

	TN3270 init/x /i
			
  This causes TN3270 to automatically execute the script
  INIT.SCR on startup. 

An example of INIT.SCR is:

on error
&s=&STARTHLLAPI		 ;* Initialize HLLAPI
quiet session start 3278 ;* Start a second session
wait 1
quiet session start 3278 ;* Start a third session
call 3278		 ;* Get first session online

The Script Variable &STARTHLLAPI initializes HLLAPI
processing for TN3270. Another Script Variable,
&STOPHLLAPI, terminates HLLAPI operations. These
are provided to control when HLLAPI is available and 
making use of memory.

Also notice the CALL command is the last command 
in the script. This is because the CALL command
does not complete until the call is terminated by the
HANGUP command or by user intervention.

You can start TN3270 from within your HLLAPI
application, or instruct the end user to start TN3270,
then invoke your HLLAPI application.

WHLLAPI does not require any special initialization as described
above for RHLLAPI.	    
	    
Short Session names for both RHLLAPI and WHLLAPI are not configurable.
The first session defaults to uppercase "E", and increments to the
next uppercase letter for each successive session.  

RHLLAPI Supported Functions

The following list includes HLLAPI functions supported by TN3270 and
RHLLAPI.DLL. For a full description of HLLAPI functions and
parameters, see the IBM High Level Language Application Program
Interface Programming Guide.

1. Connect Presentation Space
2. Disconnect Presentation Space
3. Send Key
4. Wait
5. Copy Presentation Space
6. Search Presentation Space
7. Query Cursor Posistion
8. Copy Presentation Space to String
9. Set Session Parameters
10. Query Sessions
11. Reserve Presentation Space
12. Release Presentation Space
13. Copy OIA (status line)
14. Query Field Attribute 
15. Copy String to Presentation Space
17. Storage Manager(allocate blocks of memory with HLLAPI)
18. Pause
20. Query System
21. Reset System
22. Query Session Status
23. Start Host Notification 
24. Query Host Update
25. Stop Host Notification
30. Search Field
31. Find Field Position
32. Find Field Length
33. Copy String to Field
34. Copy Field to String
90. Send File(using IND$FILE protocol)
91. Receive File(using IND$FILE protocol)
99. Convert Position to Row/Column or 
      Row/Column to Position

WHLLAPI Unsupported Functions

The following list includes HLLAPI functions not supported by TN3270 and
the WHLLAPI.DLL. For a full description of Windows HLLAPI functions and
parameters, see the Microsoft Windows HLLAPI Specification
version 1.1.

120. Connect Structured Fields
121. Disconnect Structured Fields
122. Query Communication Buffer Size
123. Allocate Communication Buffer
124. Free Communication Buffer
125. Get Request Completion
126. Read Structured Fields
127. Write Structured Fields
	     	
7.4  Serial Tuning Guidelines

The following guidelines apply to all OnNet 2.0 serial connections, 
and are especially important for slower serial environments.
Some combination of one or all of the following parameters should 
result in a performance improvement.  However,  these guidelines 
are merely a starting point, and are not a substitute for testing, adjusting, 
and trial-and-error tuning. 

In the [pctcp kernel] section of PCTCP.INI, use the following 
settings:

[pctcp kernel]
rtt-multiplier=2
slow-link-multiplier=2
do-slow-start=yes
mtu-discovery=no

rtt-multipler=2
A value higher than 1 is usually not necessary.  A 
value of 2 might be helpful, and this is a useful parameter to adjust 
during final tuning.  The kernel calculates the time it takes for one 
packet to travel a round trip over a TCP connection, using this value 
as a multipler.  Therfore, if this value were set to 3, the kernel
would use a value of three times the round-trip time to receive an ACK, 
before retransmission.

slow-link-multiplier=2 
This parameter will not affect a LAN connection but will
improve performance over a serial connection.   The kernel uses 
this value to determine the number of transmitted packets that can be 
outstanding, before receiving an ACK.  This value overrides the 
foreign window size. NOTE: This parameter setting does NOT apply to
serial connections using FTP Software's TSR kernel.

do-slow-start=yes 
This parameter defaults to YES in the OnNet 2.0 kernel
for serial connections.  When set to YES, this forces the kernel to 
determine the correct round trip time.  Set this parameter to NO if 
applications are not prepared to handle a failed send.

mtu-discovery=no 
This parameter might be the only one needed to eliminate 
retransmit problems; at other times it has no effect.  
This parameter forces the maximum segment size (MSS) to be set to 536 bytes.

7.5 Ensuring That the Correct Version of WIN32S Is On Your System

The OnNet 2.0 installation determines the version 
of WIN32S that is installed on your system by looking 
at WINDOWS\SYSTEM\WIN32S16.DLL. When the 
Read-Only attribute is set for any WIN32S files, skewed 
file versions may result during the installation. If you
experience a version skew with your WIN32S files, use 
this workaround:

1. Rename the WINDOWS\SYSTEM\WIN32S16.DLL file.
2. Set all of your Windows files to be not Read-Only with 
    the following command:

    ATTRIB /S -R C:\WINDOWS\*.*

3. Re-install OnNet 2.0. During the installation, make certain
    that you include Mail OnNet or Mosaic in the list of applications
    that will be installed on your system.

By including Mail OnNet or Mosaic in the list of installed 
applications, you are ensuring that the OnNet 2.0 installation 
will install the correct version of WIN32S. 

7.6 Using LWPE Over Netware/IP with an IBM Token Ring Network Card

To use LWPE over Netware/IP with an IBM Token Ring network card, add
the following setting to the NET.CFG file:

Netware DOS Requester
     PB BUFFERS 0

This setting forces the Netware DOS Requester not to use Packet Bursts, which
can cause the system to hang when loading an executable file from a mounted
network drive.

7.7 Correct Syntax for DOS LPRM Command (on OnNet 2.0 CD-ROM only)

The DOS LPRM command line in the Command Reference
and in the Quick Command Reference is incorrectly 
documented; you might only specify a single username.
The correct command line syntax is as follows:

lprm [-q] [-S server] [-P printer] (username |  job#...)
lprm [-? | -version]
 
7.8  Correct Description of Kernel Configuration Parameter

The following description is a correction of the description that
appears in the OnNet 2.0 Configuration Parameters Reference 
for the [pctcp kernel] section:

keepalive-timeout=number

Specifies the number of milliseconds between responses
from a remote host before the kernel terminates its side 
of a TCP connection. If the kernel has received
no reponses from the remote host during the number
of milliseconds specified for the parameter, it sends a packet 
up to three times to the remote host at intervals in  the number of 
milliseconds specified, until it receives a response. If the kernel 
receives no response to any packet, it terminates its side
of the TCP connection.

Default: 60000

8.0 Ordering Documentation

You can purchase supplemental books for OnNet
by calling 1-800-282-4387.  The following printed manuals
are available for separate purchase:

Using Networking Commands in DOS
	Describes how to use OnNet DOS commands
	to perform networking tasks in DOS.

Command Reference
	Describes the OnNet DOS commands, and
	the options for these commands for the
	full suite of OnNet DOS commands.

Configuration Parameters Reference
	Describes configuration entries
	in the PCTCP.INI configuration file.
