

			           READ ME
			    PC/TCP(R) ONNET(tm) 1.2
		                PC/TCP Network Software 3.1

			           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 here in, 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.

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

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

				 CONTENTS


	1. Installing PC/TCP OnNet and PC/TCP Network Software 
	   1.1	Choosing a DOS or a Windows Install
	   1.2	Upgrading
	   1.3	Upgrading or Reinstalling to a Different Directory
	   1.4	Installing with Windows for Workgroups 3.11
		1.4.1 Using the TSR Kernel and netbios.com with WfW 3.11
		1.4.2 Switching from a VxD to a TSR Kernel in a WfW 
		          Environment
	   1.5	Running PC/TCP OnNet with NetWare 3.12 with netx 
                             (or vlm) Loaded
	   1.6	Removing Obsolete Parameters	
		1.6.1  Removing Parameters from the 
		           \WINDOWS\SYSTEM.INI File 
		1.6.2 Removing Parameters from the AUTOEXEC.BAT
		          File  
	   1.7	Changed Parameter in the [pctcp kerberos] Section
	   1.8	Possible Problem With NDIS 1.X, PROTMAN.DOS, 
		and NETBIND
	   1.9	Deleting Files During an Upgrade from PC/TCP 
		Network Software, V2.3
	   1.10	Installing Multiple Kernels and Adding Interfaces
		1.10.1  Installing More than One Type of Kernel
		1.10.2  Installing Both a TSR Kernel and a VxD Kernel
		(OnNet only)
	   1.11	Multiconfiguration Installation in DOS 6.x
	   1.12	Installing PC/TCP with Microsoft Windows 95 
		(Windows 4.0)
	   1.13	Installing PC/TCP in a Shared Windows Environment
	   1.14	TCP and UDP Connections
	   1.15	Installing Services OnNet 1.1 over PC/TCP OnNet 1.2 
	               or PC/TCP 3.1
	   1.16	Additional Configurations for Using COMSCRPT
	2. Kernel Name Resolution and Third-Party Applications
	3. TN Negotiating the X-Display Option
	4. Resizing the PC/TCP Windows TNVT Scrollback Buffer
	5. PC/TCP Windows FTP Server and Server Control Applications 
	6. Conflict with Afterdark and WFW Network Driver (winnet.drv)
	7. Idrive and Hidden directories on Some UNIX Systems
	8. Listed Router Address over a Serial Line
	9. New Functionality for OnNet 1.2 and Network Software 3.1
	   9.1 Network Time, Windows Time Synchronization Client
	       9.1.1 TZ Environmental Variable Examples
	   9.2 NFS Autotuning
	   9.3 Idnet
	   9.4 New Kernel Features
	       9.4.1 New Parameters in the [pctcp kernel] Section of the
		     PCTCP.INI File
	   9.5 Mail OnNet
	       9.5.1 Mail OnNet Requirements
	   9.6 New FTP Features
	       9.6.1 Windows FTP Client Now Supports Take Files
	       9.6.2 FTP Now Defaults to Binary Transfer
	   9.7 Enhanced Windows Dialer
	   9.8 Windows Remote Copy Application
	   9.9 Windows Remote Command Application
	   9.10 New Reference Desk Features
	      9.10.1 Reduced Reference Desk Memory Footprint
	      9.10.2 Installing Reference Desk over a Network
	10. Known Problems
	   10.1 Unable to Run Executables on NFS Mounted Drive if
		      longfilenames=yes
	   10.2  Possible Dialer Hangup During Connection Attempt
	   10.3  Dialer Connection Successful During Teach Mode, but 
	            Fails on Subsequent Attempts
	   10.4  Using PC/TCP Network Control with the Norton 
	             Desktop Utility and Novell Netware
	   10.5  Mounting a File System in Windows
	   10.6  Modified Windows Control Panel 
	   10.7  Reference Section 7.4.1 of Using PC/TCP in Windows 
	   10.8  Defining Printer Connection with a Host Name that 
	            Does Not Exist Causes a General Protection Fault
	   11. Files Removed from this Release

1.  Installing PC/TCP OnNet and PC/TCP Network Software

1.1  Choosing a DOS or a Windows Install

The INSTALL.EXE program in DOS does not install any Windows files and
does not configure the product to run in Windows.  To use PC/TCP in
Windows, you must use the PC/TCP Windows SETUP.EXE program.  For
more information about choosing networking programs during installation in
DOS or in Windows, see the PC/TCP "Getting Started" guide.

1.2  Upgrading

If you are upgrading, exit any PC/TCP Windows applications before
you run SETUP.EXE.  The kernel and other TSRs, such as InterDrive,
can be loaded when you run the Setup program. The VxD kernel, VxD
NetBIOS, and VxD Idrive can also be loaded during the installation 
without causing problems.

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 may 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
moving the following files to the new directory:

* Files to which PCTCP.INI refers that reside in the original directory.
Such files include SESSION.INI, \etc\hosts, password, Kerberos, and all 
files in the \etc directory.

* Configuration files, such as DRIVERS.INF and MAIL-ON.INI.

* Device drivers (for example, packet drivers and NDIS drivers).


1.4  Installing with Windows for Workgroups 3.11

When installing with Windows for Workgroups (WfW) 3.11, you must use
the WfW Network Setup program to install an NDIS driver before
running the PC/TCP SETUP.EXE, if you want to share the LAN driver with
WfW. If you want to use only the PC/TCP serial interface, no NDIS driver
is needed.  You usually install the NDIS driver at the time you install 
Windows for Workgroups.

For PC/TCP Network Software (TSR kernel), choose a Real Mode NDIS
Driver. For PC/TCP OnNet (VxD kernel), choose an Enhanced Mode NDIS
driver (or,if you want to manually switch between the VxD and TSR kernels, 
choose "Real Mode and Enhanced Mode NDIS Driver").  You can also run 
over ODI drivers under WfW with either the TSR or the VxD kernel. If your 
network card has only a Real Mode driver, you can still use the VxD kernel.

Note: Even if you have a Real Mode NDIS driver, under WfW, the PC/TCP
installation will say that it found an NDIS3 driver.  This is expected.  The VxD
kernel communicates with the real mode driver using the NDIS3 interface.
WfW provides the mapping from NDIS3 to NDIS2.

See the installation procedures in the manual "Managing PC/TCP" for
more information.  

1.4.1 Using the TSR Kernel and netbios.com with WfW

If you are using the TSR kernel and netbios.com by loading them in 
your AUTOEXEC.BAT file, you could experience a problem when upgrading 
to WfW 3.11.  The WfW network setup removes any reference to a program
called netbios.com from the AUTOEXEC.BAT file.  

To correct this, manually put the command C:\PCTCP\NETBIOS.COM
back in your AUTOEXEC.BAT file.

1.4.2 Switching from the VxD to the TSR Kernel in a WfW Environment

If you want to switch from the VxD kernel to the TSR kernel, you need
to add the DIS_PKT entry to your SYSTEM.INI file manually; or, you 
can reinstall OnNet and select TSR over VxD, and the installation
program adds the DIS_PKT entry for you.

1.5 Running PC/TCP OnNet with NetWare 3.12 with netx (or vlm) Loaded

When running OnNet with NetWare 3.12 with netx (or vlm) loaded, some 
problems can occur when attempting to remount NFS drives.  After leaving 
Windows, the former NFS assigned drives become unmountable when Windows
is run a second time.

This problem is caused by a problem in Novell's VNETWARE.386.  Novell has
a patch that fixes compatibility issues between the VxD Idrive and NetWare.
The patch is available from Compuserve or from Novell's ftp server 
(ftp.novell.com).

To obtain the file from Compuserve, log in to Compuserve, type GO NSD, 
and download NETFTP.EXE. (Note: As above, you will not be able to see 
this file, but you will be able to copy it.)

To obtain the file from Novell's FTP site, FTP to ftp.novell.com and copy 
the file /pub/netwire/nsd/NETFTP.EXE.  (Note: You will not be able to see
this file in the directory, but you will be able to copy it.)

Questions regarding any difficulty retrieving this file would be best  
answered by Novell.

1.6  Removing Obsolete Parameters 

1.6.1  Removing Parameters from the \WINDOWS\SYSTEM.INI File

The following SYSTEM.INI lines were required in the PC/TCP Network 
Software V2.3 release, but are now obsolete.  The Install program 
removes any of these entries:

	[386Enh]
	device=wfwftp.386
	secondnet=wfwftp.386
	device=vpctcp.386
	secondnet=vpctcp.386

1.6.2  Removing Parameters from the AUTOEXEC.BAT File

Setup, when installing the VxD kernel, removes netbios.com, idrive.exe,
idmnt.exe, idnet.exe, and setclock.exe commands from AUTOEXEC.BAT
because the VxD does not support networking in DOS. If you have other
network commands in AUTOEXEC.BAT, the commands will fail.

If the netbios.com command was in AUTOEXEC.BAT, Setup adds the
parameter vnbep=yes to the [pctcp vxdinit] section of the PCTCP.INI
file. If the idrive.exe command was in AUTOEXEC.BAT, Setup adds the
parameter vidrive=yes to the [pctcp vxdinit] section of PCTCP.INI.
This provides NetBIOS and InterDrive functionality under Windows
using the VxD kernel, if you were previously using this functionality.

If you are using setclock.exe in AUTOEXEC.BAT, you can add the 
NETTIME.EXE program to your startup program group to get the same 
functionality that setclock provides on Windows startup.  Refer to section 
8.1 "Network Time, Windows Time Synchronization Client" in this 
READ ME and the "Using PC/TCP in Windows" guide for more 
information.

1.7 Changed Parameter in the [pctcp kerberos] Section

The directory= parameter in the [pctcp kerberos] section was separated
into two parameters: config-directory and ticket-directory.  This 
separation allows you to put configuration files in more than one 
directory.  See Appendix A of the Managing PC/TCP guide for more 
information.

1.8  Possible Problem with NDIS 1.X, PROTMAN.DOS, and NETBIND

The install and setup programs copy the NDIS 2.xxx redistributable
files PROTMAN.DOS and NETBIND.EXE when you install an NDIS 
driver. If you already have older copies of these NDIS files, and the 
netbind command in AUTOEXEC.BAT does not include a path, the 
netbind command may fail.

The \PCTCP directory is added to the path first.  This causes the new
version of netbind to run, which is not compatible with the old
version of PROTMAN.DOS in the CONFIG.SYS file.

To resolve this, either add the complete path to the old netbind
command, or change the pathname in CONFIG.SYS to use the new
PROTMAN.DOS in the PCTCP directory.

1.9  Deleting Files During an Upgrade from PC/TCP Network 
       Software, V2.3

The install program is conservative in choosing the files it deletes
when upgrading into the same directory. It does not delete the
following old files, which you may want to delete manually:

  aexecftp.bat		autoinst.cwa
  autoinst.exe		autoinst.hlp
  board.dat		config.ins
  ftp.ico			kappconf.cwa
  kappconf.exe		kappconf.hlp
  kappconf.pif		lpq.ico
  lpr.ico			mail.ico
  merger.exe		pctcp.aib
  pctcp.ico		ping.ico
  protocol.ftp		samp_net.cfg
  system.ftp		template.ini
  tn.ico

To see which files are removed, see the [remove] section of FILES.INF.

1.10  Installing Multiple Kernels and Adding Interfaces

1.10.1  Installing More than One Type of Kernel

If you use your computer over both a LAN (Local Area Network, such as
Ethernet) and a Serial port using SLIP or PPP, you need to install
two kernels and configure multiple interfaces during that
phase of the configuration, as follows

	1. If it is a new install, choose Custom and install one 
	interface following the directions in the "Getting Started" guide.

	2. In the Interface Summary dialog box, choose Add to install 
	additional interfaces.

If you want to install an additional interface at a later time, you can
do so by running the install program again, and choosing Add at the
Reinstallation dialog box.

1.10.2  Installing Both a TSR Kernel and a VxD Kernel (OnNet Only)

The new default behavior of OnNet 1.2 is to install both the TSR kernel
and the VxD kernel.  If you prefer only the VxD or TSR kernel, use the 
Custom install option.  In the custom installation, make sure to uncheck 
"Copy both kernels" in the Network Connectivity dialog box.

1.11  Multiconfiguration Installation in DOS 6.x

During the OnNet installation, you will be prompted "Update Autoexec.bat?"
Answering "yes," in DOS 6.x and above, does not cause the AUTOEXEC.BAT
to be included in the list of files that are changed.  So, the changes in the 
AUTOEXEC.FTP file located in the destination directory are not copied to
AUTOEXEC.BAT in the root. You must update this manually.

1.12  Installing PC/TCP with Microsoft Windows 95 (Windows 4.0)

During its second Beta, Microsoft changed the Windows 95
protocol-to-driver interface from NDIS version 3.0 to NDIS version
3.1 to support the dynamic loading and unloading of drivers and
protocols.

FTP Software supports NDIS versions 3.0 and 3.1.  To install NDIS 3.1
support, do the following:

(This assumes that NetBEUI is already installed on your machine.)

	1. You must first obtain the files ND31HLP.386 and 
	ND3HLP.386 from the FTP Software anonymous FTP server at:
	ftp.ftp.com\support\ftpsoft\onnet\v1.2\utils
	or the FTP Software BBS at (508) 659-6240 (8,N,1).  

	2. If you work in Windows 95, you should delete 
	ND3HLP.386 and rename ND31HLP.386 to ND3HLP.386. (In 
	the future, the install program will do it for you.)

	3. Copy the PCTCPND3.INF file into the CHICAGO\INF directory.

	4. If you are using a beta version of Windows 95 that was released 
	prior to October 1994, modify the line in the [ND3HLP.AddReg] 
	section in the PCTCPND3.INF file so that there is no * before 
	ndis, and add .386 after it.  The line should read as follows: 

	HKP,,DevLoader,,ndis.386

	5. Edit the SETUP.INF file in the CHICAGO\INF directory. Add the 
	following line into the [load_inf] section of this file:

		pctcpnd3.inf

	6. Reboot the machine.

	7. From the Control Panel, start Network and 

		* Choose the Protocol button.
		* Choose the Add button.
		* Choose FTP Software. Inc in the 'Manufacturers' 
			window.
		* Choose NDIS3 Helper for PC/TCP in the Model window.
		* Choose OK.
		* Choose Close. 
		* Choose OK.

	8. Reboot the machine.

1.13  Installing PC/TCP in a Shared Windows Environment

The OnNet install program attempts to copy CTL3D.DLL to the Windows 
system directory.  If Windows is being run from a shared network drive,
the Windows system directory is usually write protected.  If it is write 
protected, the following message is displayed: 
Could not open the file named <windows sys directory>\CTL3D.DLL.

Choose the Ignore button and the installation proceeds correctly.  
However, PC/TCP OnNet requires CTL3D.DLL to run; your system 
administrator should ensure that CTL3D.DLL is put into the Windows 
system directory.

1.14  TCP and UDP Connections

Please note that while the individual maximum number of connections for
TCP is 128 and UDP is 100, the maximum number of TCP and UDP 
connections together is 140 for the VxD kernel.  If you set an invalid
number of connections in the PCTCP.INI file, the installation program
resets the values.  Check your PCTCP.INI file to see what the values 
were set to.

For the TSR kernel, the maximum number of TCP and UDP connections
together is 80.

1.15	Installing Services OnNet 1.1 over PC/TCP OnNet 1.2 or 
	PC/TCP Network Software 3.1

Installing Services OnNet 1.1 over OnNet 1.2 or PC/TCP 3.1 replaces some 
.EXE and .DLL files with older versions of the same files.  To correct this
problem, after installing Services OnNet 1.1, reinstall either PC/TCP OnNet 
1.2 or PC/TCP Network Software 3.1.

1.16 Additional Configurations for Using COMSCRPT from DOS

If you plan on making serial connections using COMSCRPT, you must
first use the Config program to configure an IP address, subnet mask,
and router.

To configure an IP address using Config:
	1. Start the configuration program by typing config.
	2. Choose PC/TCP kernel.
	3. Choose Interface Update for the current interface.
	4. Enter an IP address.

To configure a router:
	1. Start the configuration program by typing config.
	2. Choose Internet-Addresses.
	3. Enter 1.1.1.1 as a value for the subnet and router.
	    Note: The 1.1.1.1 value is an arbitrary number
	    that serves as a place holder in the router table.  This 
	    number does not mean anything, but allows the
	    kernel to run properly.

2.  Kernel Name Resolution and Third-Party Applications

To make the PC/TCP TSR kernel smaller, Domain Naming Service 
(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 PC/TCP that use the PC/TCP kernel for
name resolution, keep the [pctcp kernel] parameter
"kernel-does-dns=yes" in the PCTCP.INI file.  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 want to free more low DOS memory.

3.  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, in the [pctcp kernel]
section of your PCTCP.INI file, set pktdrv-loopback=yes.

4.  Resizing the PC/TCP Windows TNVT Scrollback Buffer

If you change 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.  This frees memory resources for other
applications.

5.  PC/TCP Windows 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. Conflict with Afterdark and WfW Network Driver (winnet.drv)

In Windows, if you have Afterdark enabled, there may be a conflict 
with pctcpnet that may 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.

7.  Idrive 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; however,
fsck 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. 

8. Listed Router Address over a Serial Line

When you use a SLIP or 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 place holder in the router table.  Values for the router
and subnet mask that are reported by the Statistics tool can be
safely ignored when using a serial connection.

9.  New Functionality for PC/TCP OnNet 1.2/PCTCP 3.1.

9.1 Network Time, the Windows Time Synchronization Client

Network Time is a Windows(TM) application that allows the
user to maintain the PC system clock by routinely synchronizing 
it with a Network Time Server.  

For information about configuring and using the Network Time
application, see the chapter "Updating Your PC Clock from the
Network" in the manual "Using PC/TCP in Windows."

The Network Time application was designed specifically for Windows
users who need a more sophisticated time zone management system than
Windows (or DOS) alone provides.  Windows NT and Windows 95
incorporate a similar time zone handling philosophy to that
incorporated for Network Time.  

Mail OnNet is different from all other FTP Software applications in
that it is an acquired technology, and currently uses only the DOS TZ
environment variable.  This will change in the future to include the
newer time-zone handling technology developed for Network Time,
which is designed to fall back to FTP Software's "old" configuration
method for backwards compatibility, as well as fall back to the 
DOS TZ environment variable for worst-case configuration scenarios.

FTP Software has done its best to provide all applications with
correct time zone information. When you run the install/setup
program:

	1. Asks you to choose the time zone from the new list.
	2. Writes the new format time zone information to PCTCP.INI.
	3. Converts this new information into the old format and
	   writes it to the PCTCP.INI file.
	4. Converts this value into the TZ environment variable 
	   format and writes it to AUTOEXEC.BAT.

If you need to change the time zone after you run the install/setup
program, use the following procedure:

	1. Run Network Time.
	2. Choose Settings.
	3. Choose Time Zones.
	4. Choose your time zone from the list box.
	5. Choose OK.

This procedure updates your time zone for both the new and old
PC/TCP time zone formats for backwards compatibility.  It will NOT,
however, modify your DOS TZ environment variable for the Mail
OnNet application.  You can set the DOS TZ environment variable in 
the AUTOEXEC.BAT file.

9.1.1 TZ Environmental Variable Examples

Use the following TZ environment variable settings if you want to
edit the AUTOEXEC.BAT file:

        Time Zone			Recommended TZ Environment
				Variable Statement 

    UTC/Greenwich Mean Time		set TZ=UTC0   
					    or   
					set TZ=GMT0
    Australia/Tasmania			set TZ=EST-10EDT
    Australia/Queensland			set TZ=EAT-10
    Australia/North			set TZ=CST-9:30WST
    Australia/West				set TZ=WAT-8
    Australia/South			set TZ=CST-9:30CDT
    Britain				set TZ=BST0BDT
    Canada/Newfoundland			set TZ=NST3:30NDT
    Canada/Atlantic Standard		set TZ=AST4ADT
    Canada/Eastern Standard		set TZ=EST5EDT
    Canada/Central Standard		set TZ=CST6CDT
    Canada/Mountain Standard		set TZ=MST7MDT
    Canada/Pacific Standard		set TZ=PST8PDT
    Canada/Yukon Standard			set TZ=YST9YDT
    Europe/Western			set TZ=WST0WDT
    Europe/Middle				set TZ=MST-1MDT
    Europe/Central				set TZ=CST-1CDT
    Europe/Eastern				set TZ=EST-2EDT
    Iceland				set TZ=WIT0
    Japan					set TZ=JAT-9
    New Zealand				set TZ=ZST-12ZDT
    Singapore				set TZ=SIT-8
    Turkey				set TZ=EST-3EDT
    US/Eastern Standard			set TZ=EST5EDT
    US/East-Indiana			set TZ=EIT5
    US/Central Standard			set TZ=CST6CDT
    US/Mountain Standard			set TZ=MST7MDT
    US/Pacific Standard			set TZ=PST8PDT
    US/Yukon Standard			set TZ=YST8YDT
    US/Hawaii Standard			set TZ=HAT10
    US/Arizona				set TZ=MAT7
    Time Zone A				set TZ=A  1
    Time Zone B				set TZ=B  2
    Time Zone C				set TZ=C  3
    Time Zone D				set TZ=D  4
    Time Zone E				set TZ=E  5
    Time Zone F				set TZ=F  6
    Time Zone G				set TZ=G  7
    Time Zone H				set TZ=H  8
    Time Zone I				set TZ=I  9
    Time Zone K				set TZ=A  10
    Time Zone L				set TZ=A  11
    Time Zone M				set TZ=A  12
    Time Zone N				set TZ=A  -1
    Time Zone O				set TZ=A  -2
    Time Zone P				set TZ=A  -3
    Time Zone Q				set TZ=A  -4
    Time Zone R				set TZ=A  -5
    Time Zone S				set TZ=A  -6
    Time Zone T				set TZ=A  -7
    Time Zone U				set TZ=A  -8
    Time Zone V				set TZ=A  -9
    Time Zone W				set TZ=A  -10
    Time Zone X				set TZ=A  -11
    Time Zone Y				set TZ=A  -12
    Time Zone Z				set TZ=A  0

FTP Software, Inc. plans to have this multiple time zone
configuration problem entirely resolved for the next release.

9.2 NFS Autotuning

InterDrive has an automatic tuning device to dynamically adjust three
factors that can affect network performance: streaming, read size,
and write size.

Autotuning is enabled by default. If you prefer not to use autotuning,
you can turn it off for a specific file system by entering autotune=off
in the [pctcp idrive filesys] section that defines the file system in
your PCTCP.INI file. If read-size=, write-size=, and stream=
parameters exist in your PCTCP.INI file from a previous release of
PC/TCP software, and if autotuning is off, InterDrive uses the
values specified in your file. With autotuning on, InterDrive starts 
out using the specified values, but the values are likely to vary up or
down as a result of the autotuning mechanism.

9.3 Idnet

Idnet, the DOS graphical user interface for mounting NFS file systems
and printers, now allows you to configure and mount permanent file 
systems and printers. You can also use Idnet to tune InterDrive 
parameters and view InterDrive statistics. Both of these functions were 
previously available in DOS only by command line.

9.4 New Kernel Features

9.4.1 New Parameter in the [pctcp kernel] Section of the PCTCP.INI file

do-slow-start = [yes/no]	

Turn On/Off slow start.  If a user has 'hang'-like problems with some 
Windows applications (the known ones are HGopher, WinVN, 
TCP3270, Ingres 4GL, and Microsoft SQL Administration Tool), 
the user should try to set this parameter to no. (Default: yes for 
SLIP and PPP; no for other media.)

9.5 Mail OnNet

Mail OnNet is a complete mail system running on PCs connected to
a computer network (including the Internet) through an open standards
mail server. In many installations, the server will be running UNIX, but
the server could also be running DOS, OS2, NT, VMS, or a mainframe 
operating system.

Mail OnNet features MIME and MAPI support.  MIME (Multipurpose
Internet Mail Extensions) support means that users can mail binary file
attachments with regular mail messages.  MAPI (Messaging
Application Program Interface) is a messaging standard developed by
Microsoft that lets users send files from within enabled Windows 
applications.

After the installation is completed, you must configure Mail OnNet
before you can use the application. Refer to Appendix A, "Configuring 
Mail OnNet," in the "Mail OnNet User's Guide" for details.

9.5.1 Mail OnNet Requirements

Mail OnNet runs best with SHARE.EXE loaded.  Mail OnNet does 
not require that SHARE.EXE be loaded; however, many MAPI applications
cause file errors if SHARE.EXE is not running.

Mail OnNet requires a temp directory and that the TMP environment 
variable be set.

9.6 New FTP Features

9.6.1 Windows FTP Client Now Supports Take Files

The Windows FTP client application in PC/TCP OnNet now supports 
the use of command ("take") files. FTP command files allow the user
to automate frequently performed file transfer operations under 
Windows.

9.6.2 FTP Now Defaults to Binary Transfer

The Windows FTP client now uses "Binary" instead of "ASCII" as its 
default file transfer setting.

9.7 Enhanced Windows Dialer

The Windows Dialer provides a powerful scripting language for 
automatically establishing remote SLIP or PPP connections.  Using a 
new "Connection Wizard" feature, novice users are guided step-by-step 
through the configuration process.  The Dialer automatically generates a 
command script and icon, which allow future remote connections to be 
established quickly and easily.

9.8 Windows Remote Copy Application

The Windows Remote Copy application allows the user to copy files or 
directories between the PC and another computer on the network, or 
between two remote computers on the network.  This provides an 
easy-to-use Windows version of the DOS and UNIX "rcp" application.

9.9 Windows Remote Command Application

The Windows Remote Command application allows users to execute 
commands on remote hosts using the "rsh" or "rexec" methods.

9.10 New Reference Desk Features

9.10.1 Reduced Reference Desk Memory Footprint

Using new compression techniques, FTP Software, Inc. has reduced the 
size of the Reference Desk online documentation files by approximatly 
50% to 7 megabytes, while increasing the amount of information.

9.10.2 Installing Reference Desk over a Network

Detailed instructions on how to install Reference Desk over a network 
are now included in the "Getting Started" guide.

10. Known Problems

10.1 Unable to Run Executables on NFS Mounted Drive if longfilenames=yes

Mapped files will lose the UPPERCASE extension if FAT=NO (or the 
lowercase extension if FAT=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.

10.2 Possible Dialer Hangup During Connection Attempt

In some circumstances, the Dialer may hang during a connection attempt.  
Test to see if your modem is working correctly by using the Windows 
Terminal application.  If your modem appears to be working correctly, the 
problem may be that the Dialer application requires specific signals on specific 
pins.  Some modem cables do not strictly adhere to the modem specifications; 
you may need to replace your modem-to-comport cable to correct the problem.

10.3 Dialer Connection Successful During Teach Mode, but Fails on 
        Subsequent Attempts

The Teach Mode of the Windows Dialer is designed to automatically learn 
the sequence of prompts for logging in to your service provider.  However, 
some service providers have multiple servers that have different prompts; 
as a result, the prompt may be different each time you connect.  For 
example, the first time you connect, you may get a prompt that looks like 
this: 
	server-3 login:

The next time you connect, the prompt may look like this:

	server-4 login:

Since the prompt does not match what the Teach Mode learned, the Dialer 
will continue to wait for the expected prompt until it times out.  The Dialer
is designed to recover from this situation (or any situation where the prompt
it receives does not match what it expected).  When it times out, it will
display a dialog box asking you how to respond to the prompt.  If you type
your user ID and choose OK, the remainder of the connection sequence should
function properly.  This will be necessary each time you connect when the 
prompt is different from the first time you connected.

Alternatively, you can manually edit the connect script so that you 
automatically connect successfully each time.  To do this, proceed as 
follows:
	1. In the main Dialer window, choose Go to Advanced Dialer.
	2. Open the Connection box, and select your connection name.
	3. Choose the Edit button.
	4. Scroll down through the file until you find a line that looks 
	    something like this:
		(define,input_data,(receive,(phone,timeout),{er-3 login: }))
	    The sequence of characters between the braces {} are the last 
	    12 characters of the login prompt that the script is looking for 
	    (this will be different, depending on your service provider).
	5. Change this sequence so that the sequence no longer contains the
	     portion of the prompt that continues to change.  In the above 
	     example, you would change {er-3 login: } to {login: }.
	6. Click the OK button.

10.4  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 the Norton Desktop utility and Novell NetWare.  
FTP Software, Inc. is pursuing a solution from Symantec
Corporation, developers of the Norton Desktop utility.

           
10.5  Mounting a File System in Windows

You cannot mount a file system in Windows using an alternate
primary group identifier.  The PC/TCP Network Driver does not 
recognize the gid= keyword in your PCTCP.INI file.  As a
workaround, open a DOS session and use the DOS IDMNT command to 
mount the file system.

10.6  Modified Windows Control Panel 

After installing PC/TCP OnNet, a configuration icon for Mail OnNet, called 
"Mail OnNet Meassaging Subsystem" is added to the Windows Control 
Panel Window.  The long name can cause the window to look messy.

To work around the problem:
	1. In the CONTROL.INI file, delete the line "MON_CFG.DLL."
	2. Create a new icon in the PC/TCP WinApps group with the 
	     command line
	     C:\WINDOWS\CONTROL  C:\PCTCP\MON_CFG.DLL.

10.7  Section 7.4.1 of "Using PC/TCP in Windows"

The Permissions button in the File Managers Properties window
has been removed.  You can change permission of files and
directories with the idchmod command.  See the "Command
Reference" manual for more information.

10.8  Defining a Printer Connection with a Host Name that Does Not
         Exist Causes a General Protection Fault

If there is a defined printer connection with a host name that does not 
exist, the connection will fail if you try to connect that printer.  Any further
attempts to connect to that port will cause a General Protection Fault.
When you close the "Connect a Printer" window, any future 
attempt to reopen that window will result in a General Protection Fault.

11. Files Removed from this Release

As indicated in the OnNet 1.1 release the following files have been 
removed from the OnNet 1.2 and PC/TCP Network Software 3.1
releases:
	SC.EXE
	SUPDUP.EXE
	PD_PCTCP.COM

These files will still be available from the FTP Software BBS.
