     OnNet(TM) version 2.1 for Windows 
  	 Release of March 1996 

                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 
may be used or copied only in accordance with the terms of such license.

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


                                 CONTENTS

1  Installing OnNet version 2.1 for Windows
   1.1  Installing Over Windows NT
          1.1.1  Deleting OEMNXPxx.INF Files from an NT System
          1.1.2  Setting Up Online Help on Windows NT Systems
   1.2  Installing Over Windows95
          1.2.1  Limits to Length of Destination Directory Names
          1.2.2  Running the 3c5x9 Packet Driver with Plug and Play
    1.3  Installing InterDrive 95
    1.4  Installing Over OnNet32
2  Before You Start to Use OnNet Applications   
    2.1  Before You Start to Use InterDrive 95 or InterDrive NT
           2.1.1  Using the RPCINFO and AUTH Commands
    2.2  Before Your Start to Use InterDrive 95
           2.2.1  Case Sensitivity of Login Names
           2.2.2  Case Sensitivity of Filenames in Windows 95
    2.3  Before You Start to Use Mail OnNet
           2.3.1  Before You View Attachments
           2.3.2  Set the TMP Environment Variable for Mail OnNet
    2.4  Before You Start to Use FTP Software Messaging Service
3  New and Removed Applications in OnNet version 2.1
    3.1  New Applications
    3.2  Removed Files and Applications
4  New Functionality in OnNet version 2.1
    4.1  New Integrated TN3270/TN5250 Application
    4.2  New Mail OnNet Features
    4.3  32-bit Mail Transports for Microsoft Exchange
    4.4  New Mosaic Features
    4.5  New KEYview Features
    4.6  New FTP Features
    4.7  New TNVT Features
    4.8  New Dialer Features
    4.9  New and Changed InterDrive 95 Features
           4.9.1  Support for Different Usernames and Passwords
           4.9.2  Alias Support
5  Known Limitations
    5.1  Using InterDrive
           5.1.1  Setting the Hidden File Attribute on Some UNIX Systems
           5.1.2  Unable to Run Executables Whose Extensions Are 
                     Incompatible with the Map Lowercase Setting
           5.1.3  Using the FTP Software Network Driver with the Norton 
                     Desktop Utility and Novell NetWare
           5.1.4  Using the FTP Software Network Driver with IBM 
                     PC-DOS
           5.1.5  Confilict with Afterdark and Windows for Workgroups 
                     Network Driver (WINNET.DRV)
    5.2  Using InterDrive NT
    5.3  Using InterDrive 95
    5.4  Interaction Issues in Context-Sensitive Help
           5.4.1  Distorted Group Box Label
           5.4.2  Interaction with Snap To Feature for Microsoft Mouse
           5.4.3  Context-Sensitive Help on Windows 95
    5.5  Using Dialer
           5.5.1  Inactivity Warning Setting
           5.5.2  Dial-on-Demand Timeout
           5.5.3  Dialer Ignores ignore-dsr=on Parameter
           5.5.4  Using Dialer with NetWare IP
	       5.5.5  Using a Cellular Connection
    5.6  Using Mail OnNet
    5.7  Using FTP Software Internet Messaging Service
    5.8  Using LPD Print Server
    5.9  Help Not Available for Kernel Property Pages
    5.10  FTP Server, the DOS SUBST Command and Windows for Workgroups
    5.11  Using Mosaic
            5.11.1  DDE and First Virtual Authentication
            5.11.2  Viewing Directory Pages
            5.11.3  Mosaic and Austin Computer's DSTN Notebook PCs
            5.11.4  Mosaic Security Protocol Message
            5.11.5  Growstub Error Message
            5.11.6  Attempt to Load URL Failed
            5.11.7  Temporary Windows Swap File
            5.11.8  Using an FTP Software PC/TCP Stack
    5.12  NetWare Server Mapped Disk Access in DOS Session
             Might Cause Windows Exit to DOS and Sometimes
             System Reboot   
    5.13  Using NIS with Windows 95
    5.14  Increasing the Number of Network Descriptors for Use by
             Dialog
    5.15  Using FTP Server and SOCKS Security
    5.16  Using NetBIOS on a Serial Line
    5.17  Using Netscape
    5.18  Using the TSR Kernel and the Comscrpt Command
    5.19  Increasing the Number of Network Descriptors for Use by Dialog
6   Ordering Documentation
         

1  Installing OnNet version 2.1 for Windows

The OnNet CD-ROM includes a folder that has the OnNet (TM) diskette images 
available for drag and drop disk copying or DOS copying. This lets you 
make disks for distribution to workers at your site.

OnNet 2.1 applications are supported over the Microsoft TCPIP-32 3.11b
TCP/IP (Wolverine) stack.

1.1  Installing Over Windows NT

Changes made to the AUTOEXEC.BAT file do not override the value of
the PCTCP variable that is set in the registry.

1.1.1  Deleting OEMNXPxx.INF Files from an NT System

If you delete an OEMNXPxx.INF file from the SYSTEM32 directory, the
entry for its corresponding product does not appear in the Network
Settings dialog box and you cannot upgrade, configure, or remove the
product.

For each product you install on an NT system, when you use the
Control Panel Network Settings dialog box, a file named OEMNXPxx.INF
is created in the SYSTEM32 directory. This file is used to create an
entry in the Add Software list box.  When you remove a product, this
file remains in the SYSTEM32 directory.  If you install many
products, therefore, you will accumulate many versions of the
OEMNXPxx.INF file.

To remove an entry so that it does not appear in the Add Software
list box:

	1. Search all OEMNXPxx.INF files for the title of the product that
        you want to remove.

	2.  Use File Manager to delete that file.

1.1.2  Setting Up Online Help on Windows NT Systems

Currently, if a user installs OnNet on a Windows NT system where
multiple users expect to use the OnNet applications, only the first
user can use the online Help for those applications. The other users
must install OnNet on the same system to be able to use the online
Help. 

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 end users of their NT
systems. After the NT Administrator installs OnNet, each end user
runs the utility to set the appropriate values in the NT Registry. To
obtain the utility, contact your FTP Software technical support
representative.

1.2  Installing Over Windows95

1.2.1  Limits to Length of Destination Directory Names

Although Windows 95 supports long filenames, the OnNet installation
program cannot install the product to a folder name that exceeds the
8.3 DOS filename requirements.

1.2.2  	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), your 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 the documentation provided with the 3c5x9 board for
information about changing this setting.

1.3  Installing InterDrive 95

The IDNPNDI.DLL file cannot be installed if you have the network
property sheets (dialog box) open and are viewing properties for 
InterDrive 95 while you are installing InterDrive 95. To avoid problems 
caused by version mismatch between this file and the other InterDrive files,
close the network property sheets (dialog box) before installing InterDrive 95. 

1.4   Installing Over OnNet32

FTP Software does not recommend upgrading from OnNet32 to OnNet 2.1. If you 
decide to install OnNet 2.1 on a system that is running OnNet32, FTP Software 
suggests you follow these steps:

	1. Install OnNet 2.1 into a separate directory from your OnNet32 directory.

	2. Move all data files, such as the .SCR files used by the Dialer and Telnet
       applications and the SESSION.INI file, to the separate OnNet 2.1 directory.

2  Before You Start to Use OnNet Applications

Read the following sections before you start using OnNet applications.

2.1  Before You Start to Use InterDrive (R) 95 or InterDrive NT

2.1.1  Using the RPCINFO and AUTH Commands

The RPCINFO and AUTH commands are shipped only on the CD-ROM version 
of OnNet; they are not in PC/TCP (R) Network Software or OnNet on diskette.

	RPCINFO      Displays a list of NFS daemons running on the 
                        specified host.

	AUTH            Verifies that NFS authentication is working properly.

These commands, which run only over the FTP Software TCP/IP stack,
are available from FTP Software OnLine Services as a self-extracting
file named nfs-test.exe. You can obtain this file from the FTP Software 
World Wide Web server: ftp://ftp.ftp.com/support/ftpsoft/onnet/v2.0/utils/.

To use the commands, enter the command at a DOS prompt.

2.2  Before You Start to Use InterDrive 95

2.2.1  Case Sensitivity of Login Names

In InterDrive 95, unlike Windows 95, NFS login usernames and
passwords are case sensitive. For example, to an NFS authentication
server, the name Pat and the name PAT are two different usernames.
When you restart Windows 95, the login dialog box might display the
current default username in all uppercase letters. If necessary, type
the username again in the appropriate case to ensure that
authentication works when you try to use shared folders on an NFS
server.

2.2.2  Case Sensitivity of Filenames in Windows 95

The Windows 95 Network Neighborhood does not support browsing through
folders that have the same name but different case.  For example, if
you are browsing through a shared folder with subfolders called TEST,
test, and Test, you can access only the contents of the folder named
TEST. To avoid this situation, you can map the shared folder to a
network drive. After the network drive is mapped, Windows Explorer
and My Computer show the appropriate contents of each folder
regardless of its case.

2.3   Before You Start to Use Mail OnNet

2.3.1  Before You View Attachments

Mail OnNet uses KEYview (TM) as its default file viewer. If you already have 
the full version of  KEYview (version 4.2), Mail OnNet uses that version as the 
default file viewer. Otherwise, Mail OnNet uses the version that comes with your
OnNet installation software.

If you want to use a different viewer application, you must edit
the MAILON.INI file in your OnNet installation 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.   

2.3.2   Set the TMP Environment Variable for Mail OnNet

The DOS environment variable TMP defaults to the root directory on the 
C drive (C:\). If you want the TMP variable to be set to a different 
directory or one on a different drive, you must define the environment 
variable TMP for Mail OnNet. Add the following line to 
your AUTOEXEC.BAT file:

	set TMP=_temp_path_

where _temp_path_ is the complete pathname of the directory into which Mail OnNet can put
temporary data. An example is:

	set TMP=D:\mailon\tmp

2.4   Before You Start to Use FTP Software Messaging Service

When you add a new entry to your address book in the Microsoft
Exchange client, you can select either of two types: the Other
Address type or the Personal Distribution List type. If you select
the Other Address type, and if you are using the FTP Software (R)
Internet Messaging service to send and receive mail, specify SMTP as
the e-mail type for the new address in the New Address tab of the New
Other Address Properties dialog box.

3   New and Removed Applications in OnNet version 2.1 

3.1   New Applications 

OnNet provides the following new Windows applications to help you
with your networking tasks and to let you access Internet resources.

o TN3270/TN5250 combined application
o Launcher
o InterDrive NT

3.2  Removed Files and Applications

The Internet Registration application has been removed from 
OnNet for Windows.

In addition, many sample Dialer scripts have been removed  
from the OnNet for Windows distribution on disk. To obtain these sample 
scripts, visit the FTP Software home page on the World Wide Web at 
http://www.ftp.com/ or connect to the FTP Software anonymous FTP site, 
ftp.ftp.com.

In the next release of OnNet, FTP Software plans to remove support in
the FTP application for TOPS20 detection.

4   New Functionality in OnNet Version 2.1

4.1   New Integrated TN3270/TN5250 application

TN3270/TN5250 is a single program that performs either IBM 3270 or
IBM 5250 terminal emulation. The executable filename is TN3270.EXE.

4.2  New Mail OnNet Features

Mail OnNet now provides a spelling tool  that verifies the spelling of
outgoing messages.

4.3   32-bit Mail Transports for Microsoft Exchange

Mail OnNet includes an information service for the Microsoft Exchange
program known as the FTP Software Internet Messaging service. This
service lets users of the Microsoft Exchange program send and receive
e-mail messages to and from the Internet.

4.4   New Mosaic Features

Mosaic no longer requires the installation of the Windows 32-bit
subsystem and its attendant hard-disk and memory requirements. This
release of Mosaic is a 16-bit version. 

Mosaic uses KEYview as its default file viewer. If you already have the full 
version of  KEYview (version 4.2), Mosaic uses that version as the default 
file viewer. Otherwise, Mosaic uses the version that comes with your OnNet 
installation software.

You can obtain regular updates to Mosaic from FTP Software. Regular updates
are available from the FTP Software World Wide Web page at:

	http://www.ftp.com/Browser/upgrade

The following features have been added to this version of Mosaic:

o 	Mosaic Security Framework
	Mosaic's open security framework allows for plug-in security modules.
	Basic Authentication and Simple MD5 modules come pre-installed.

o	Establishing Secure Links to SSL-capable servers
	Mosaic now supports the Secure Socket Layer (SSL) protocol, that enables
	encryption of data (such as credit card numbers).

o 	Hierarchical Hotlist
	The new hierarchical hotlist gives you the option to organize your
	links into groups. Your links appear in a tree structure that
	shows the groups you have created and the Web pages in those groups.
	You can also import existing hotlists from Mosaic and Netscape.

o  Support for HTML 3.0 Extensions
	Mosaic now supports HTML 3.0 extensions such as colored text, tables,
	and alignment of text and images.

o  Caching of Web Pages
	When you access a web page, you can set your Edit preferences to have
	Mosaic cache the page on your disk. You can view the page multiple
	times without waiting for the page to be reloaded from the server.

o  Unsurpassed Performance
	Advanced Display Technology lets you interact with documents in
	multiple windows during download. Text appears immediately,
	allowing you to follow links before the downloads are complete.

o  Inline JPEG Support
	In addition to GIF images, inline JPEG images are now supported.

o  Built-in GIF and JPEG Viewers
	Mosaic's internal image viewer automatically displays standalone GIF
	and JPEG files.

o  Configurable Helper Applications
	Configuring helper applications to support new file types is now
	simpler with an easy-to-use dialog box.

o  Client-Side Image Maps
	Now you can create and use image maps locally without interacting
	with a server. 

o  Toolbar
	A new toolbar provides quick access to frequently used menu commands.

o  Horizontal Scroll Bar on History Dialog Box
	A horizontal scroll bar in the history dialog box allows you to see
	the full text of the URLs.

o  Longer Open URL Dialog Box
	A longer Open URL dialog box allows you to see more of the typed URL. 

4.5   New KEYview Features

The following new features have been added to in this release of KEYview:

o  New Formats:
	HTML viewer
	BINHEX viewer 

o  Image and Graphics Converter Formats (source and destination, unless 
    otherwise noted):
	AMI Draw Graphics (SDW) (source only) 
	Mac PICT (raster content) 
   	Computer Graphics Metafile (CGM) 
   	MacPaint 
   	Encapsulated PostScript (EPS) 
   	Truevision Targa (TGA) 
    WordPerfect Graphics (WPG)
   	WordPerfect Graphics 2.0 (WPG)

o  Integration with Windows Explorer on Windows 95
	The installation program adds KEYview to the menu that appears when
	you point to a file in Windows Explorer and click the right mouse
	button. If you point to KEYview in the menu, you can choose between
	viewing the file in KEYview or using KEYview to compress the file.

4.6   New FTP Features

The FTP client supports non-transparent FTP proxy firewalls.
Firewalls that use non-transparent FTP proxies include the ANS
Interlock firewall and some older versions of Raptor Eagle firewalls. 

FTP also uses the KEYview as its default file viewer. If you already have 
the full version of KEYview (version 4.2), FTP uses that version as the 
default file viewer. Otherwise, FTP uses the version that comes with your 
OnNet installation software.

4.7   New TNVT Features

TNVT now supports operations in full-screen mode. In full-screen
mode, the TNVT application itself (with its screen elements such as
the toolbar, menus, scroll bars, title bars, and the status bar) are
hidden from the user. In this mode, the user is aware only of the
application running in TNVT, and not of TNVT.

TNVT now supports using the Kermit protocol to transfer files during
a TNVT session. TNVT supports both sending and receiving files with
Kermit, when you run the corresponding Kermit command on the remote
host. This version of the TNVT application does not support sliding
windows or long packets when using Kermit.

4.8   New Dialer Features

Dialer now offers you a simpler wizard interface to configure a
connection, and supports connections to remote sites over cellular telephone 
channels by way of a wireless modem. 

Specifically, the Dialer supports Cellular Digital Packet Data (CDPD), 
circuit switched cellular (AMPS US), and GSM. The Dialer provides 
single link and multilink CAPI VxD and DLL support, as well as single link WinISDN
support.

Your OnNet 2.1 installation software provides prewritten script files
for four CDPD devices. The script files, which are identified in the 
[pctcp cdpd modem] section of the MODEM.INI file, are:

o PK210INI.SCR - initialization script for the Sierra Wireless PocketPlus 
   210 CDPD Modem

o PK210BYE.SCT - exit script for the Sierra Wireless PocketPlus 210
   CDPD Modem

o IBMONCM1.SCR - initialization script for the IBM Wireless 
   Cellular/CDPD Modem

o IBMOFCM1.SCR - exit script for the IBM Wireless 
   Cellular/CDPD Modem

o UBION.SCR - initialization script for the PSCI Ubiquity 100/200 
   Cellular Packet device

o UBIOFF.SCT - exit script for the PSCI Ubiquity 100/200 
   Cellular Packet device

o DARTON.SCR - initialization script for the Cincinatti Microwave DART 
  100/100 CDPD Modem

o DARTOFF.SCR - exit script for the Cincinatti Microwave DART 
  100/100 CDPD Modem

4.9   New and Changed InterDrive 95 Features

This release contains many new features that support the multiuser,
multi-network-provider Windows 95 environment. InterDrive 95 takes
advantage of the ability in Windows 95 to customize and save an
entire working environment based on the user who is currently logged
in. This means that individual users can configure their own set of
NFS servers to use in Network Neighborhood, as well as customize and
save their own NFS connections and login settings.

4.9.1   Support for Different Usernames and Passwords

InterDrive 95 includes new features that allow more flexibility with
logging in to NFS connections:

o  If your username and password for NFS connections are different
 	from your Windows 95 username and password, you can set an option
	that prompts for InterDrive 95 login information as well when 
	Windows 95 starts.
   
o  If your username and password are not the same for all NFS
    connections, you can set an option that prompts for user 
    information before each connection. When this option is not set 
    (the default), InterDrive 95 attempts to make new connections 
    using your current login information, without prompting. This 
    setting is useful when a connection would succeed using your 
    current login information, but you want to specify a different 
    login for specific connections. For example, you might want to 
    specify a username that is associated with a different group ID 
    than your default username.   
  
4.9.2   Alias Support

InterDrive 95 now supports aliases, which are a shorthand form, or
label, for a full network path. 

5   Known Limitations

The following items are known limitations with this release of OnNet
for Windows.

5.1   Using InterDrive

5.1.1   Setting the Hidden File Attribute on Some UNIX Systems

On certain UNIX systems (including HP/UX systems), setting the DOS
hidden attribute on a directory can cause the directory to become
unusable from your PC.

InterDrive translates the DOS hidden file attribute to the UNIX
setuid bit.  On some UNIX systems, setting the setuid bit causes the
system to rename the directory by appending a plus sign (+) to it.
The system then hides the directory from standard listing commands
such as UNIX ls and DOS idls.

Because the directory gets renamed, you can no longer access the
directory using InterDrive from your PC. Further, nothing prevents
you from creating another directory or file by the same name as the
old directory, making it seem as if the old directory and all of its
contents have been overwritten.

To recover the renamed directory, log in directly to the UNIX system
or use a program such as Telnet to log in remotely. Then, remove the
setuid bit by entering the command:

	chmod -s dirname+  

where dirname+ is the name of the directory that you want to make
usable again. You must also rename the directory if you want to
remove the plus sign from its name.

5.1.2    Unable to Run Executables Whose Extensions Are Incompatible
            with the Map Lowercase Setting 

Because InterDrive allows you to use folders and directories on UNIX
systems, it must have a method for handling multiple files with the
same name but different case.  Its method for handling case
sensitivity is to create mapped names for certain files. By default,
InterDrive treats lowercase filenames as normal and creates mapped
names for files with mixed-case or uppercase names.  This can affect
your ability to run executables, batch files, or command files on a
network drive.

A file on a network drive will be executable only if its filename is
in a case that prevents the name from being mapped. For example, if
you have a file named DOTHIS.BAT on a network drive, and uppercase
and mixed-case name mapping is enabled, InterDrive creates a mapped
name, such as DOTHI~00 for the batch file, and you will not be able
to run it unless you use the mapped name. You can see a listing of
mapped and original filenames when you enter a dir command from a DOS
session.

To avoid this situation, you can rename batch files and executables
to a case that does not get mapped by InterDrive. You can also change
the Map Lowercase setting to reverse the name mapping rules, but this
might have adverse affects on how you see and use the majority of
your files.

5.1.3   Using the FTP Software Network Driver with the Norton Desktop
          Utility and Novell NetWare

The FTP Software 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.

5.1.4   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 might 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.

5.1.5   Conflict with Afterdark and Windows for Workgroups Network Driver 
          (WINNET.DRV)

In Windows, if you have Afterdark enabled, there might be a conflict
with the FTP Software Network Driver 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.   

5.2   Using InterDrive NT

You cannot run InterDrive NT DOS commands from an MS-DOS command
window.

5.3   Using InterDrive 95

The following describes known limitations with using InterDrive 95:

o The net use command cannot mount folders with mixed-case paths.

o The DOS and Windows NFS servers from the FTP Software OnNet Server
   Version 2.0 for DOS/Windows package do not support the use of long
   filenames. If you use InterDrive 95 to connect to resources shared by
   these servers, do not use long filenames in Windows 95.

o The value displayed for Disk Quotas under the Mapped Network Drives
   properties does not represent the user's disk usage and limits as
   presented by the quota command on UNIX servers.  The value displayed
   is the available space on the disk for nonprivileged users.

o Windows 95 does not automatically refresh the display when you
   remove an NFS server from the InterDrive 95 configuration. Use the
   F5 key to force a screen refresh.

o  If, while browsing an NFS server from Network Neighborhood, you recieve the 
    error message:

	    InterDrive Networking, password is incorrect. Try again.

    it means your Windows95 username is not listed in the password file on the 
    server.

    To browse the NFS server, set your username and password for that host or file
    system using the property sheets. Click the host; click Properties, and set the
    username and password on the NFS Attributes property sheet.
  
5.4   Interaction Issues in Context-Sensitive Help

5.4.1   Distorted Group Box Label 

The label text of a groupbox might appear distorted under certain
circumstances after you view, and then dismiss, a context-sensitive
help popup. The cause is 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).

5.4.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 box or item you point to or click.

5.4.3   Context-Sensitive Help on Windows 95

When you click the right mouse button on editable text boxes, Windows
95 supplies a system-defined menu. Menu choices include such items as
Cut, Copy, and Paste. For applications that use context-sensitive
Help, when you click the right mouse button on an editable box, that
system-defined menu appears for a fraction of a second and is then
replaced with the definition help for that box.

To access a menu choice for an editable text box, use the
corresponding keyboard sequence for the command (for example, Ctrl+X,
Ctrl+C, Ctrl+V).

5.5   Using Dialer 

5.5.1   Inactivity Warning Setting

In Dialer, if the inactivity warning is set to the same value as the
inactivity timeout, the inactivity warning dialog box always appears.
If there is any network activity, the dialog box flashes.

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

5.5.2   Dial-on-Demand Timeout

If you specify an IP address (instead of a hostname) for Dial on
Demand and your connection times out, add the following entry to your
PCTCP.INI file:

	[pctcp kernel]
	disable-timeout=yes

5.5.3   Dialer Ignores ignore-dsr=on Parameter

The Dialer program does not respond to the ignore-dsr=on parameter in
the [pctcp serial n] section of the PCTCP.INI file. 

5.5.4  Using Dialer with NetWare IP

To use the Dialer with NetWare IP, your system must have Windows for
Workgroups installed. This configuration requires two files that are in
the Windows for Workgroups distribution: SERIAL.386 and VCOMM.386.

5.5.5  Using a Cellular Connection

There is no support for cellular PIN numbers. To use Dialer with a
cellular telephone or modem, you need to receive a PIN-exempt account
from your cellular service provider.

If your cellular account includes a call waiting feature, you might
experience problems during your connection if another call is
received. If this feature can be disabled through your cellular phone
or modem and your cellular service provider, you should disable it.
This will ensure that you do not experience any disruptions during
the connection related to another incoming call.

5.6  Using Mail OnNet

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.

Caution: If you delete a folder that contains no messages, but does
contain other folders that 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.

You will be unable to nest Mail OnNet folders within other folders
beyond 8 levels. This usually means that the directory path to the
location of your folders, C:\PCTCP\YOUR_ID\FOLDERS (where 
YOUR_ID is the name of your personal folder that stores all of your 
folders and messages), already takes up 3 of the 8 levels allowed by DOS,
leaving you with 5 levels below the \FOLDERS subdirectory. If you try 
to go beyond that level, Mail OnNet displays an error message and the
folder is not created.

Caution: Do not use any program other than Mail OnNet to manage your
messages and folders.

If the network terminates unexpectedly and Mail OnNet generates a
general protection fault (GPF), you must restart Windows.

5.7   Using FTP Software Internet Messaging Service

Properties - General Tab

o  If you get the following error message while attempting to connect to an 
	Internet mail server:

  	Cannot find details of host MyHost1

	where MyHost1 is an example of the name of your mail server, which
	you specified for the InBound  Mail Server or the OutBound Mail Server 
	settings, you must change the settings. Instead of specifying a hostname 
	for each of these settings, specify the IP address of the mail server.

Properties - MIME Tab

o 	Make certain that the default settings of the System and the User 
   	Configuration Files are as follows:
   	System File: C:\pctcp\send.prf
   	User File: C:\pctcp\user.prf

o 	The character set encodings are set to the following default
   	settings, and cannot be changed:

    Secondary Character Set: US-ASCII
    7-Bit Text: 7-bit
    8-Bit Text: 8-bit

o 	The Show Encoding Warnings setting is turned on, and cannot 
   	be turned off. Because it is always turned on, you might receive a 
   	warning each time that there is a problem with the MIME encoding or 
   	decoding of messages.

5.8   Using LPD Print Server

In Windows 95, you cannot view jobs in a printer queue by clicking
the Queues button in the LPD Print Server status window. The LPD
Print Server relies on Windows Print Manager for queue information,
and Print Manager no longer exists in Windows 95.  To view the status
of jobs in a printer queue, double-click the printer icon.

5.9   Help Not Available for Kernel Property Pages

For this release, context-sensitive help for kernel property pages
has not been implemented. For information about kernel properties, 
see the OnNet "Advanced User's Guide." 

5.10   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.

5.11   Using Mosaic

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

5.11.1   DDE and First Virtual Authentication

Mosaic 16-bit Browser does not support DDE and
First Virtual Authentication.

5.11.2  Viewing Directory Pages

You might encounter problems when exiting from Mosaic after
viewing a directory page with the browser.

Restart the browser to resume normal operation.

5.11.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.

5.11.4   Mosaic Security Protocol Message

You receive the following message when you start Mosaic,

	Could not find DLL for Security Protocol Module:
	FirstVirtual=fv Load,fv.dll

Edit the 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:

	FirstVirtual=fv Load,fv.dll

5.11.5  Growstub Error Message

When starting Mosaic, a dialog box might display this message:

	GROWSTUB
	An error has occurred in your application.

The growstub problem is due to a defect 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:

	[windows]
 	load=
	   
5.11.6   Attempt to Load URL failed

This message usually appears when a site is busy. Some sites are so busy, 
you might need to try another time.

This message can also appear if the spelling of the URL path is incorrect, or
if your PC has insufficient available memory. 

5.11.7   Temporary Windows Swap File

If you have a temporary Windows swap file, this swap file could grow and 
cause the copying of files to fail. This is a reported defect, but it is not a common 
occurrence.

5.11.8  Using an FTP Software TCP/IP stack

If you are using an FTP Software TCP/IP stack (such as the stack included in
OnNet), change the following parameters in the VXD kernel section of your 
PCTCP.INI file to these values:

[pctcp kernel-vxd]
large-packets=50
tcp-connections=64

5.12   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                                                          

5.13   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.

5.14   Increasing the Number of Network Descriptors for Use by Dialog

If, while attempting to use the FTP Software Dialog application for
Windows, with the TSR kernel (available on CD-ROM only) you receive
one of the following error messages:

	Cannot open sending network descriptor
	-or- 
	Cannot open receiving network descriptor

you might need to perform either of the following tasks:

Decrease the number of Dialog servers that you are using
concurrently.  Deselect any servers that you are not using for your
current Dialog connection(s). For example, if you are only using the
IRC server, turn off the Talk and Single-Line Message mode servers.
If you are using Single- Line Message mode, deselect the Single-Line
Message (TCP) server, and just use the Single-Line (UDP) server. If
you are using Talk mode, deselect the Old Talk server, and just use
the New Talk server.

Increase the number of TCP and UDP connections available to your TSR
kernel until the number set eliminates the error messages.

By default, the number of TCP and UDP connections that are active for
the TSR kernel is 4 each. You can use the Configure application to
increase the number of connections.

You might need to test increasing values until you no longer receive
the error message. For more information about setting these values,
see the OnNet "Advanced User's Guide." 

5.15  Using FTP Server and SOCKS Security

Your Windows FTP client application might not work with the FTP
server if both the client and the server have SOCKS enabled. The FTP
client will communicate with the FTP server if the server has SOCKS
disabled.

5.16  Using NetBIOS on a Serial Line

To use NetBIOS over a serial connection in Windows 95, you must install 
first a LAN interface (on a system that uses a NetBIOS-based LAN, such as 
Windows for Workgroups) and then a serial interface.

5.17  Using Netscape

If you use Netscape V2.0 Beta 4 and Beta 5, the following message appears 
when you attempt to connect to a web site:

	Network Error: Socket is not connected

Netscape has corrected this behavior in Beta 6 of their product. 

5.18  Using the TSR Kernel and the Comscrpt Command

If you install the CD-ROM version of OnNet 2.1 and are using the TSR kernel
and the comscrpt command to open and close serial line connections to the 
network (rather than use the Dialer application), you cannot run FTP Software
applications under Windows unless you turn off Van Jacobsen (VJ) compression.
(VJ compression is on by default.)

To turn off VJ compression , use the configure command or edit the PCTCP.INI 
file as follows:

	[pctcp interface n]
	vj-compression=off
	vj-compression-auto=off

5.19  Increasing the Number of Network Descriptors for Use by Dialog

If, while attempting to use the FTP Software Dialog application for
Windows, you receive one of the following error messages:

	Cannot open sending network descriptor
   	 -or- 
   	Cannot open receiving network descriptor

you might need to perform either of the following tasks:

Decrease the number of Dialog servers that you are using
concurrently.  Deselect any servers that you are not using for your
current Dialog connection(s). For example, if you are only using the
IRC server, turn off the Talk and Single-Line Message mode servers.
If you are using Single-Line Message mode, deselect the Single-Line
Message (TCP) server, and just use the Single-Line (UDP) server. If
you are using Talk mode, deselect the Old Talk server, and just use
the New Talk server.

Increase the number of TCP and UDP connections available to your TSR
kernel until the number set eliminates the error messages.

By default, the number of TCP and UDP connections that are active for
the TSR kernel is 4 each. You can use the Configure application to
increase the number of connections.

You might need to test increasing values until you no longer receive
the error message. For more information about setting these values,
see the "Advanced User's Guide."


6    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.

