READ ME PC/TCP(R) Network Software version 4.1 for DOS 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 New Functionality in PC/TCP version 4.1 1.1 New Integrated TN3270/TN5250 Application 1.2 New FTP Features 1.3 New TNVT Features 1.4 New Dialer Features 1.5 New Kernel Features 2 Removed Files and Applications 3 Known Limitations 3.1 Using InterDrive 3.1.1 Setting the Hidden File Attribute on Some UNIX Systems 3.1.2 Unable to Run Exectuables Whose Extensions Are Incompatible with the Map Lowercase Setting 3.1.3 Unable to Run Executables on NFS Mounted Drive If longfilenames=yes 3.1.4 Using the FTP Software Network Driver with the Norton Desktop Utility and Novell NetWare 3.1.5 Using the FTP Software Network Driver with IBM PC-DOS 3.1.6 Confilict with Afterdark and Windows for Workgroups Network Driver (WINNET.DRV) 3.2 Interaction Issues in Context-Sensitive Help 3.2.1 Distorted Group Box Label 3.2.2 Interaction with Snap To Feature for Microsoft Mouse 3.3 Using Dialer 3.3.1 Inactivity Warning Setting 3.3.2 Dialer Ignores ignore-dsr=on Parameter 3.3.3 Using Dialer with NetWare IP 3.3.4 Using a Cellular Connection 3.4 FTP Server, the DOS SUBST Command, and Windows for Workgroups 3.5 Increasing the Number of Network Descriptors for Use by Dialog 3.6 Using FTP Server and SOCKS Security 3.7 Using the TSR Kernel and the COMSCRPT Command 3.8. Using InterDrive NT 4 Ordering Documentation 1 New Functionality in PC/TCP version 4.1 PC/TCP 4.1 applications are supported over the Microsoft TCPIP-32 3.11b TCP/IP (Wolverine) stack. 1.1 New Integrated TN3270/TN5250 Application TN3270/TN5250 is a single Windows program that performs either IBM 3270 or IBM 5250 terminal emulation. The executable filename is TN3270.EXE. 1.2 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. 1.3 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. 1.4 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 PC/TCP 4.1 installation software provides prewritten script files for four popular 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 1.5 New Kernel Features If two users have configured, and are simultaneously using, the same IP address, the FTP Software (R) TCP/IP kernel (protocol stack) does not work for the second user. 2 Removed Files and Applications Many sample Dialer scripts have been removed from the 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, FTP Software plans to remove support in the FTP application for TOPS20 detection. 3 Known Limitations The following items are known limitations with this release of PC/TCP Network Software. 3.1 Using InterDrive (R) 3.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. 3.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. 3.1.3 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. 3.1.4 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. 3.1.5 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. 3.1.6 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. 3.2 Interaction Issues in Context-Sensitive Help 3.2.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). 3.2.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. 3.3 Using Dialer 3.3.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. 3.3.2 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. 3.3.3 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. 3.3.4 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. 3.4 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. 3.5 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 PC/TCP "Advanced User's Guide." 3.6 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. 3.7 Using the TSR Kernel and the COMSCRPT Command If you are using the COMSCRPT command to open and close serial line connections to the network (rather than using the Dialer application), you cannot run FTP Software applications for Windows unless you turn off Van Jacobsen (VJ) compression. (VJ compression is on by default.) To turn off VJ compression , use the DOS configure application, or edit the PCTCP.INI file as follows: [pctcp interface n] vj-compression=off vj-compression-auto=off 3.8. Using InterDrive NT You cannot run InterDrive NT DOS commands from an MS-DOS command window. 4 Ordering Documentation You can purchase supplemental books for PC/TCP by calling 1-800-282-4387. The following printed manuals are available for separate purchase: "Using Networking Commands in DOS" Describes how to use PC/TCP DOS commands to perform networking tasks in DOS. "Command Reference" Describes the PC/TCP DOS commands, and the options for these commands for the full suite of PC/TCP DOS commands. "Configuration Parameters Reference" Describes configuration entries in the PCTCP.INI configuration file.