PC World Komputer 1998 April A

home *** CD-ROM | disk | FTP | other *** search

/ PC World Komputer 1998 April A / Pcwk4a98.iso / Wtestowe / OnNet16 / README.TXT < prev next >

Wrap

Text File | 1997-02-10 | 27KB | 667 lines

OnNet(R)16 version 2.5 for Windows Release of February 1997 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 - 1997. All rights reserved. CONTENTS 1 Before You Start to Use Mail OnNet 1.1 Before You View Attachments 1.2 Set the TMP Environment Variable for Mail OnNet 2 New and Removed Applications in OnNet16 version 2.5 2.1 New Licensing 2.2 New TNVTPlus Application 2.3 OnNet16 Installations Supported by Custom Install Manager 2.4 Microsoft Internet Explorer 2.5 Removed Files and Applications 3 New Functionality in OnNet16 version 2.5 3.1 New Mail OnNet Features 3.2 New FTP Client Features 3.3 New Dialer Features 3.4 New Remote Command Features 3.5 New DHCP Features 3.6 New Setup Program Customization Tools 3.7 New Network Control (FTP NFS) Parameter 4 Known Limitations 4.1 Using InterDrive 4.1.1 Setting the Hidden File Attribute on Some UNIX Systems 4.1.2 Unable to Run Executables Whose Extensions Are Incompatible with the Map Lowercase Setting 4.1.3 Conflict with After Dark and Windows for Workgroups Network Driver (WINNET.DRV) 4.2 Using Dialer 4.2.1 Inactivity Warning Setting 4.2.2 Dial-on-Demand Timeout 4.2.3 Dialer Ignores ignore-dsr=on Parameter 4.2.4 Using Dialer with NetWare IP 4.2.5 Using a Cellular Connection 4.2.6 Use of NetBIOS and Dial-on-Demand Incompatible 4.3 Using Mail OnNet 4.4 Using FTP Client 4.4.1 Using FTP Client with MVS File Servers 4.4.2 Using FTP Client with UNISYS 2200 File Servers 4.4.3 Third-Party SOCKS Servers Unsupported 4.5 FTP Server, the DOS SUBST Command, and Windows for Workgroups 4.6 NetWare Server Mapped Disk Access in DOS Session Might Cause Windows Exit to DOS and Sometimes System Reboot 4.7 Using FTP Server and SOCKS Security 4.8 Using OpenScript Editor 4.9 Creating a TNVTPlus Serial Connection 4.10 Installing OnNet Server version 2.0 4.11 Creating Disks from the Disk Layout on the CD-ROM 5 Obtaining Setup.inf Documentation 1 Before You Start to Use Mail OnNet ------------------------------------------------------------------ If you are unable to run Mail OnNet, verify that the MAPI.DLL file in your OnNet16 directory (typically C:\PCTCP) is the only MAPI.DLL file on your computer. If you find another MAPI.DLL file, rename it. 1.1 Before You View Attachments ------------------------------------------------------------------ Mail OnNet uses KEYview (TM) as its default file viewer. If you already have the full version of KEYview, Mail OnNet uses that version as the default file viewer. Otherwise, Mail OnNet uses the version that comes with your OnNet16 installation software. If you want to use a different viewer application, you must edit the MAILON.INI file in your OnNet16 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. 1.2 Set the TMP Environment Variable for Mail OnNet ------------------------------------------------------------------ Mail OnNet saves temporary data to the directory specified by the TMP variable. By default, this is the root directory on the C drive (C:\). If you want Mail OnNet to use another directory, you must specifically define the TMP environment variable, generally in the AUTOEXEC.BAT file. ------------------------------------------------------------------ 2 New and Removed Applications in OnNet16 version 2.5 ------------------------------------------------------------------ 2.1 New Licensing ------------------------------------------------------------------ Review the information in INSTALL.WRI on the CD-ROM or on Disk 1 for information about the new licensing format in OnNet16. 2.2 New TNVTPlus Application ------------------------------------------------------------------ OnNet16 provides a totally new TNVTPlus application that provides the following terminal emulators: VT 420, 320, and 220 VT 100 VT 52 WYSE-60 WYSE-50 SCO ANSI IBM-PC BBS ANSI This product provides the same capabilities for the 16-bit platform as the TNVTPlus shipped in OnNet32 version 2.0 and adds \ the following features: Serial support Echo and line mode Playback for start and stop capture BBS ANSI terminal emulation 180 column support Floating keyboard For TNVTPlus, the telnet= drive:\path parameter in the [pctcp sessions] section of the PCTCP.INI file, specifies the default directory that contains TNVTPlus session definition files, which use the .STE extension. TNVTPlus saves session files to this directory, unless, when you save the session definition, you specify another directory. 2.3 OnNet16 Supported by Custom Install Manager ------------------------------------------------------------------- You can install Custom Install Manager on a Windows 95 or Windows NT system and use it to customize installations of OnNet16. The version of Custom Install Manager available on the OnNet16 CD, or on request on separate disks, supports the OnNet16 Setup program. For more information, see the Custom Install Manager Readme file and online Help. 2.4 Microsoft Internet Explorer ------------------------------------------------------------------ For your convenience, the OnNet16 distribution includes a version of Microsoft Internet Explorer that FTP Software has customized for your use. To install Internet Explorer from the OnNet16 CD-ROM Run the IEW31.EXE program provided in the IEXPLORE directory. To obtain Internet Explorer if you have OnNet16 only on disks 1. Use your FTP Client program to retrieve IEXPLORE.EXE from the following: ftp.ftp.com/support/ftpsoft/onnet/v2.5/patch. 2. At a DOS promt, type the following command: iexplore -saruba where aruba is the password that enables you to extract the Readme and the IEW31.EXE file from IEXPLORE.EXE. 3. In Windows, run the IEW31.EXE program to install Microsoft Internet Explorer. Notes: ╖ Internet Explorer is installed in a directory named IEXPLORE, in the Windows directory. ╖ If you use Internet Explorer with a dialup connection, and if you want Internet Explorer to re-establish the connection whenever you activate the program, you must manually configure dial-on-demand for Internet Explorer. To do so, start Internet Explorer. On the View menu, point to Options and click Connection. In the Connection page, click Connect to Internet. A black dot indicates that dial-on-demand is activated. ╖ The Readme file installed into the IEXPLORE directory is produced by Microsoft. The readme documents information about the TCP/IP stack and dialup adapter typically installed by Internet Explorer. The version of Internet Explorer in the OnNet16 distribution does not install a stack or dialup adapter, since OnNet16 provides both. Therefore, the information in the Readme file about the stack and dialup adapter does not apply to this installation. 2.5 Removed Files and Applications ------------------------------------------------------------------ WTNVT has been removed and replaced by TNVTPlus. Mosaic has been removed and replaced by Microsoft Internet Explorer, which has its own installation program. This product no longer provides the TSR versions of the kernel, InterDrive, and NetBIOS. This product no longer supports the Windows 95 and Windows NT operating systems. Please see your sales representative for information about the product that best suits your environment. ------------------------------------------------------------------ 3 New Functionality in OnNet16 version 2.5 ------------------------------------------------------------------ You can view basic information about your FTP TCP/IP stack (kernel) configuration by selecting Info on the About box of many of the OnNet16 programs. 3.1 New Mail OnNet Features ------------------------------------------------------------------ This release of Mail OnNet provides the following new features: Personal distribution lists. Address book conversion from the format in previous versions of Mail OnNet. Ability to work in offline (remote) mode. 3.2 New FTP Client Features ------------------------------------------------------------------ FTP Client provides the option to always create a new file when copying to the remote system (the sunique command). A new parameter that you can set in the [pctcp ftp] section of the PCTCP.INI file, lets you set the maximum length of time, in seconds, that FTP should wait for a network operation to complete before aborting the connection. This releases the Windows FTP client if the network connection is not working or if the server stops responding. The parameter takes the following form: transfer-timeout=x where x is a length of time in seconds. Range: 1-32767 Default: 60 3.3 New Dialer Features ------------------------------------------------------------------ Dialer now supports MS-CHAP, which extends the CHAP user authentication functionality to support that provided by Microsoft Windows NT dial-up servers. 3.4 New Remote Command Features ------------------------------------------------------------------ Remote Command now supports running commands from a DOS command line. 3.5 New DHCP Features ------------------------------------------------------------------------ If the hostname and domain are both configured in the PCTCP.INI file, the Dynamic Host Configuration Protocol (DHCP) client sends the resulting fully qualified domain name to the DHCP server, which can then use that name to dynamically update a DNS server, provided both the DHCP and DNS servers support this option. Currently, IBM provides a DHCP server that supports this option; other vendors may be providing this support in the future. Also, when the domain is configured in the PCTCP.INI file, the DHCP client will not change the domain setting in the FTP Software kernel. A new parameter, that you can set in the PCTCP.INI file, lets you specify whether the DHCP client caches its lease or releases it when the computer is shut down. The parameter takes the following form: [pctcp dhcp] cache-lease=yes | no If set to yes, the DHCP client caches the lease. The default is no. Another new parameter, that you can set in the PCTCP.INI file, lets you configure the DHCP client to accept only DHCP or only Bootp server responses and reject the other. The parameter takes the following form: [pctcp dhcp] protocol-accepted=dhcp | bootp If set to dhcp, the DHCP client ignores responses from Bootp servers. The default behavior of the DHCP client is to accept either DHCP or Bootp responses. 3.6 New Setup Program Customization Tools ------------------------------------------------------------------ The OnNet16 Setup program and the FTP Software Inc. Custom Install Manager now make it easier for network administrators to customize the OnNet16 Setup program for the clients in your network. Read the Advanced User's Guide to learn about Custom Install Manager, a tool with a graphical user interface that lets you create and manage client installation scripts for OnNet16 users in your network. If you have access to computers that run Windows 95 or Windows NT, you can use Custom Install Manager. Note that this version of the SETUP.INF file has been modified so that you can use Custom Install Manager to prepare installation scripts. Custom Install Manager replaces the need for Setup.inf to support batch installations. 3.7 New Network Control (FTP NFS) Parameter ------------------------------------------------------------------ A new parameter that you can set in the [pctcp pctcpnet] section of the PCTCP.INI file, lets you control whether to suppress the messages that are exchanged between the FTP Network Driver and LPD during the detection and establishment of a connection with the LPD printer. The parameter takes the following form: check-for-lpd=[yes|no] where yes suppresses the display of the messages. You might want to set this value to no for a busy or slow network. Default: yes ------------------------------------------------------------------ 4 Known Limitations ------------------------------------------------------------------ The following items are known limitations with this release of OnNet16. 4.1 Using InterDrive ------------------------------------------------------------------ 4.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. 4.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. 4.2.3 Conflict with After Dark and Windows for Workgroups Network Driver (WINNET.DRV) In Windows, if you have After Dark enabled, there might be a conflict with the FTP Software Network Driver that might cause the Windows for Workgroups network file and printer sharing not to work. The workaround is to comment out afterdark in the SYSTEM.INI file. 4.2 Using Dialer ------------------------------------------------------------------ 4.2.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. 4.2.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 4.2.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. 4.2.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. 4.2.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. 4.2.6 Use of NetBIOS and Dial-on-Demand Incompatible If you use a SLIP or PPP connection with NetBIOS and enable Dial-On-Demand (DOD), the Dialer randomly tries to reconnect to the dial-up server. To work around this problem disable DOD if you are using NetBIOS and SLIP/PPP. The cause of this behavior is that Microsoft Network tries periodically to send NetBIOS packets; the kernel detects that and starts the Dialer. 4.3 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. 4.4 Using FTP Client ------------------------------------------------------------------ 4.4.1 Using FTP Client with MVS File Servers The Windows FTP client has primarily been tested against the IBM MVSV3R1 FTP server. Since the standards do not specify the format for a reply to a directory list request, other server implementations of MVS might transmit lists in another format and the Windows FTP client does not display the list as you might expect. As a workaround, set the host type to None and try to obtain the list. If this does still not work, use the DOS ftp command. In addition, due to the way the FTP client has been designed for Windows and due to the non-hierarchical nature of the MVS filesystem, HLQ and PDS searches may not provide the results you expect. If this is the case, use the DOS ftp command. 4.4.2 Using FTP Client with UNISYS 2200 File Servers You cannot transfer an ABSOLUTE file element (executable or binary program) from a UNISYS 2200 mainframe. 4.4.3 Third-Party SOCKS Servers Unsupported Although we do not support thrid-party SOCKS servers (such as those on a Windows NT computer), you might be able to use the FTP Client program across such a server if you set the client in passive mode. 4.5 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. 4.6 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 NetWare DOS Requester section as follows: NetWare DOS Requester PB BUFFERS 0 4.7 Using FTP Server and SOCKS Security ------------------------------------------------------------------- Your Windows FTP client application will not work with the FTP server if the server has SOCKS enabled. The FTP client will communicate with the FTP server if the server has SOCKS disabled. 4.8 Using OpenScript Editor ------------------------------------------------------------------- When debugging a script that contains embedded dialog boxes, you might receive a message box stating Insufficient memory to perform operation. To avoid the problem, use breakpoints at specific locations rather than stepping through the script one line at a time. 4.9 Creating a TNVTPlus Serial Connection ------------------------------------------------------------------- If you experience difficulty (either regularly or intermittently) in making a serial connection directly from TNVTPlus, this is a known problem. In some computers, when you attempt to make a serial connection from TNVTPlus, the modem does not dial and TNVTPlus displays the error message: Could not connect. To work around this problem, perform the following steps: 1. In the error message box, click Cancel. 2. On the Session menu, click Properties. 3. On the General page of Connection Properties, click Comm Settings. 4. In the Com Properties dialog box, click Use This Port Directly and click OK. 5. On the General page of Connection Properties, click OK. 6. On the Session menu, click Connect. 7. In the edit box that appears, type modem commands directly. If you are using a Hayes-compatible modem, type the following commands: atz atdt phone_number where atz and atdt are literally what you type, and phone_number is the number the modem should dial. If you are using another type of modem, consult the modem documentation to learn which commands to type in for dialing the modem. 4.10 Installing OnNet Server version 2.0 ------------------------------------------------------------------- To install Onnet Server version 2.0 over Onnet16 version 2.5, you need to obtain a patch. Use an FTP client application to connect to ftp.ftp.com and get the file 15731.exe from the support/ftpsoft/service/v2.0/patch directory. To unzip the file, at the DOS prompt, type the following command: 15731.exe -s9590 where 15731.exe is the file you obtained, and 9590 is the password. The 15731.exe file contains the following: syslog.dl_ setup,inf readme.txt For detailed instructions, read the README.TXT file. Although the documentation specifies that this patch is for OnNet32 version 2.0, the patch also applies to OnNet16 version 2.5. 4.11 Creating Disks from the Disk Layout on the CD-ROM ------------------------------------------------------------------- You might experience problems copying files in order to create disk 12. If you are creating the disk on a Windows 95 computer and copying the files from your hard drive or from another computer (using a network connection), you might not be able to copy one or more files to the disk. You can successfully create the disks on a Windows 95 computer if you copy them directly from the CD-ROM to the disks; and you can successfully create the disks if you are using a Windows 3.1 \ 3.11 computer and the DOS command line or File Manager. ------------------------------------------------------------------- 5 Obtaining Setup.inf Documentation ------------------------------------------------------------------- The documentation of Setup.inf has been removed from the OnNet16 printed documentation. If, for some reason, you cannot use Custom Install Manager to produce customized installations, you can obtain documentation of this version of the Setup.inf file from the Technical Support area of the FTP Software, Inc. Web site (currently, http://www.ftp.com/techsup/quick-help/docs).