KSP FTP (tm) A FTP Door for Bulletin Board Systems Version 3.0 Copyright (C) 1995-96 All Rights Reserved by KEY SOFTWARE PRODUCTS 40 Atherton Court Redwood City, California 94061 BBS/FAX: 415-364-9847 KSP FTP is a trademark of Key Software Products. PCL4C is a trademark of MarshallSoft Computing. WATTCP is a trademark of Erick Engelke. Power C is a trademark of Mix Software. Lantastic is a trademark of Artisoft, Inc. Novell is a trademark of Novell Corp. Banyan Vines is a trademark of Banyan Inc. DESQview is a trademark of Quarterdeck Office Systems. TABLE OF CONTENTS CHAPTER 1 - INTRODUCTION ........................... 1 1.1 Compatibility with BBS Software ............... 1 1.2 Hardware Requirements ....................... 2 1.3 Software Requirements ....................... 2 1.4 Other KSP Software ........................... 2 1.4.1 KSP Telnet ............................. 3 1.4.2 KSP SLIP ............................... 3 1.4.3 KSP Mail ............................... 3 1.4.4 KSP HOST ............................... 3 1.4.5 So Many CD's ............................ 3 CHAPTER 2 - INSTALLATION ........................... 4 2.1 Packet Driver Shims for Novell ................. 4 2.2 Packet Driver Shim for Novell w/Token-RingSNAP .. 5 2.3 Packet Driver Shims for Lantastic .............. 5 2.3.1 Changes to CONFIG.SYS ................... 5 2.3.2 Changes to PROTOCOL.INI ................. 6 2.4 Packet Driver Shims for Banyan Vines ............ 7 2.5 Other Things to Configure ..................... 7 CHAPTER 3 - THE WATTCP CONFIGURATION FILE ............. 8 3.1 Multiple Nodes and the "include" Directive ...... 9 3.2 Using a BOOTP Server .......................... 9 3.3 Manual Configuration ........................ 9 3.3.1 The PC's Host Name ....................... 10 3.3.2 The PC's Domain Name ..................... 10 3.3.3 The PC's IP Address ...................... 10 3.3.4 The Name Server's IP Address .............. 11 3.3.5 The Router's IP Address .................. 11 3.3.6 The PC's Network Mask .................... 11 3.4 TCP/IP Parameters (optional) ................. 11 3.4.1 DNS Search Mode ......................... 12 3.4.2 Timeouts .............................. 13 3.4.3 Maximum Segment Size (MSS) ............... 13 3.5 FTP Operating Parameters ..................... 13 3.5.1 Dynamic Parameters ..................... 14 3.5.2 Retrieving Hostname of Remote Server ...... 14 3.5.3 Blocking Access to Certain Sites .......... 15 3.5.4 Allowing Access to a Limited Set of Sites .... 15 3.5.5 Session Time Limit ...................... 15 3.5.6 Session Reserve Time .................... 15 3.5.7 Inactivity Limit ....................... 16 3.5.8 Minimum Baud Rate ....................... 16 3.5.9 Operating Hours ........................ 16 3.5.10 User Session Logging ................... 17 3.5.11 Non-Standard Port/Fossil Break Detect ... 17 3.5.12 Adding External Protocols .............. 17 3.5.13 Controlling Disk Space Usage ............ 19 TABLE OF CONTENTS 3.5.14 Limiting User Download Bytes ............ 19 3.5.15 Updating BBS Download Bytes ............. 20 3.5.16 Silencing the BBS console bell ........... 20 3.5.17 Disabling the Local Screen .............. 20 CHAPTER 4 - INSTALLING THE FTP DOOR COMMAND ............ 22 4.1 Command Line Parameters ...................... 22 4.1.1 The /SCRIPT Parameter ................... 23 4.1.2 The /MAXMINS Parameter .................. 23 4.1.3 The /CONFIG Parameter ................... 23 CHAPTER 5 - INSTALLING YOUR ACCESS KEY ................ 25 CHAPTER 6 - SELECTING A SERIAL COMMUNICATION PROTOCOL .. 26 6.1 Internal Protocols .......................... 26 6.1.1 Internal Xmodem and Ymodem Protocols ...... 26 6.1.2 Internal 1K-Xmodem/G and Ymodem/G Protocols 26 6.1.3 Internal Zmodem Protocol ................ 27 6.2 External Protocols .......................... 27 6.3 Recommendations ............................ 27 APPENDIX 1 - HOW TO REACH US .......................... 29 APPENDIX 2 - GETTING UPDATES VIA THE INTERNET .......... 30 APPENDIX 3 - LEGAL STUFF ............................ 31 Sep 01, 1996 KSP FTP (tm) v3.0 1 CHAPTER 1 - INTRODUCTION KSP FTP is a BBS door that implements the familiar FTP client program that allows users to transfer files to/from remote computers over a TCP/IP network. If your BBS is connected to the Internet, KSP FTP lets your BBS callers transfer files to and from remote host machines anywhere in the world for the cost of a phone call to your BBS! During file transfers, data between the BBS and the remote host is transmitted using the TCP/IP protocol, while data between the BBS and the user is transmitted using a serial communication protocol such as X/Y/Zmodem. Both internal and external serial communications protocols are supported; internal protocols include Xmodem-Cksm, Xmodem-CRC, 1K-Xmodem, 1K-Xmodem/G, Ymodem, Ymodem/G, and Zmodem. KSP FTP meets the following BBS-specific needs: 1. Terminates the BBS session when user's time limit expires. 2. Terminates the BBS session when user hangs up. 3. Terminates when there's no activity for a sysop-specified period of time. 4. Records the FTP session in a log file. 5. Provide colorized or parameterized messages to user. 6. Restrict users by baud rate. 7. Restrict hours of operation. KSP FTP is shareware. The unlicensed version is fully functional except that it imposes a maximum of five minutes per FTP session. Once licensed, the user is limited only by the amount of time remaining in his BBS session. KSP FTP was implemented using Erick Engelke's Waterloo TCP library, MarshallSoft Computing's PCL4C Personal Communications library and PPL4C Personal Protocol Library, and Mix Software's Power C compiler. 1.1 Compatibility with BBS Software KSP FTP is compatible with any BBS software that can generate a DOOR.SYS file. It works with a BBS configured to use the standard COM1 through COM4 ports, or will automatically detect and use a Fossil driver. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 2 1.2 Hardware Requirements KSP FTP inherently requires that the PC running your BBS software have a physical connection to a TCP/IP network - normally the Internet. Ideally, this connection is by means of an adapter card connected to an Ethernet at your company or school (and then through a "gateway" to the Internet). It is also possible to connect to the Internet through a commercial Internet Access Provier via a dial-up FTP (Serial Line Internet Protocol) connection. This approach requires a second serial port, modem, and telephone line dedicated to this purpose. Information on finding such a provider is available on the KSP BBS. 1.3 Software Requirements KSP FTP runs on top of another piece of software called a "packet driver". The packet driver presents a standard software interface to KSP FTP, regardless of the type of hardware interface that connects the PC to the network. Public domain packet drivers exist for SLIP and PPP links and most Ethernet cards. If your BBS uses a multi-tasking operating system to run multiple nodes on a single PC, then you will need a "packet multiplexer". A packet multiplexer designed specifically for use with KSP network products running under DESQview is available as a freeware package distributed as KSPMUX*.ZIP, where the "*" is the version number. KSP FTP is DESQview "aware" to provide better performance in a multitasking environment. If your PC is connected to a non-TCP/IP proprietary network (such as Novell or Lantastic), you will probably need a packet driver "shim". KSP FTP does NOT require that you purchase a separate TCP/IP package, such as that sold by Novell, Artisoft, or IBM. KSP FTP should happily coexist with any of these packages, however. An assortment of public domain packet drivers, multiplexers, and shims are available on the KSP BBS. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 3 1.4 Other KSP Software Key Software Products offers a number of other products for BBS's: 1.4.1 KSP Telnet A door program that allows callers to connect to remote computers anywhere on the Internet via your BBS. Available now on our BBS. 1.4.2 KSP SLIP A door program that allows callers to run any TCP/IP software from home, including using Mosaic to browse the World Wide Web. Available now on our BBS. 1.4.3 KSP Mail A Multi-Threaded Server for SMTP Mail and NNTP Usenet news. Replaces UUCP, its monthly fees, and slow transfer rates! No more unwanted newsgroups! Instant mail without waiting for scheduled events! Works with any BBS software that presently uses UUCP. Requires a 24hr TCP/IP Internet connection. Can now receive NNTP news feeds! 1.4.4 KSP HOST An inbound Telnet server for MS/DOS Bulletin Board Systems. Every node can answer both telnet and modem calls! Requires a fossil driver on each node, a 24 hour TCP/IP connection to the Internet, and a local area network that supports NetBios such as Novell or Lantastic. 1.4.5 So Many CD's A PCBoard PPE to handle off-line CD-Roms. Seamlessly integrated into PCBoard. Users post requests for off-line files and have then returned as attachments to messages. Configurable message pack-out dates automatically keep your hard disk from getting cluttered. Available now on our BBS. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 4 CHAPTER 2 - INSTALLATION Before installing KSP FTP as a BBS door, you must first install: 1. The network interface hardware. 2. A corresponding packet driver. 3. A packet driver shim (if needed). 4. A packet multiplexer (if needed). Detailed directions for these preliminary steps are available in separate documentation that comes with the corresponding hardware or software. It's most common that multi-node BBS's are interconnected with Ethernet and either Lantastic or Novell. Unfortunately, these two network operating systems were designed using their own proprietary protocols rather than the TCP/IP protocol and their own proprietary software rather than packet drivers to talk to their Ethernet interface cards. However, a piece of software called a packet driver "shim" can be used to let both TCP/IP and their proprietary protocol coexist. 2.1 Packet Driver Shims for Novell Novell's network software is installed in layers as TSRs in the order shown below. These commands are usually found either in the AUTOEXEC.BAT file or in another batch file in a directory typically called C:\NWCLIENT. LSL NE2000 }-- specific to your interface card IPXODI VLM The packet driver shim (ODIPKT) logically sits on top of IPXODI, providing a packet driver interface for software such as KSP FTP: LSL NE2000 +--- Frame Type (0-3) IPXODI | ODIPKT 2 97 }--- The packet driver shim VLM | +----- Packet Vector Interrupt (96-127) (See comment below about hex vs. decimal) The ODIPKT command line parameters may vary according to which Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 5 version of the software you have and how your hardware is configured. The "Frame Type" parameter should correspond to the position of ETHERNET_II among the frame types specified in NET.CFG; zero (0) selects the first frame type, one (1) the second, and so on. The "Packet Vector Interrupt" number should correspond to an unused interrupt vector. Note that older versions of ODIPKT insist that this number be given in decimal (96-127) rather than in hex (0x60-0x7F). The necessary packet driver shim can be downloaded from the Key Software Products BBS as file ODI-SHIM.ZIP. 2.2 Packet Driver Shim for Novell w/Token-RingSNAP Another shim called ODITRPKT exists for Novell that should be used if the underlying network is Token-Ring_SNAP. Installation is similar to ODIPKT as described above, except that the first command line parameter must correspond to the Token-Ring_SNAP frame type in NET.CFG, and starts at "1" rather than "0". This shim can be downloaded from the Key Software Products BBS as file TKN-SHIM.ZIP. 2.3 Packet Driver Shims for Lantastic Using a packet driver shim with Lantastic requires that Lantastic be installed using NDIS (Network Driver Interface Specification) Support. The necessary packet driver shim can be downloaded from the Key Software Products BBS as file DIS-SHIM.ZIP. NDIS allows you to stack multiple protocols on a single adapter. This lets you use multiple protocol drivers (such as LANtastic and TCP/IP) on the same adapter. You can also use NDIS to include third-party adapters that have NDIS drivers in your LANtastic network. Supported adapter types include Ethernet, Token-Ring and ARCNET (R) adapters. The software and documentation necessary to add NDIS support to an existing Lantastic network is available free of charge from Artisoft. Once you have NDIS installed and working with Lantastic, adding the shim is a simple matter of editing PROTOCOL.INI (part of the NDIS support) and CONFIG.SYS. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 6 2.3.1 Changes to CONFIG.SYS With NDIS installed, there will be two device driver lines in your CONFIG.SYS file that look something like the following: DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\AEXNDIS.DOS The file listed in the second line may differ if you are not using Artisoft's interface card; in that case, this file would typically be replaced by a NDIS driver supplied by the card manufacturer. The packet driver shim itself is installed as a third device driver after the first two, as in: DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\AEXNDIS.DOS DEVICE=C:\DRIVERS\DIS_PKT.DOS }--- The packet driver shim 2.3.2 Changes to PROTOCOL.INI The PROTOCOL.INI file is a text file created (usually in the C:\LANTASTI directory) as part of the NDIS installation. Before adding the packet driver shim, it typically looks like the following, but with the "iobase" and "interrupt" parameters changed according to your hardware, or with the entire "[AEXNDIS_NIF]" section replaced if you are not using an Artisoft interface card. [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES [AEXNDIS_NIF] DRIVERNAME = AEXNDS$ IOBASE = 0x300 INTERRUPT = 15 Adding the packet driver shim requires adding another section to the PROTOCOL.INI file: [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 7 [AEXNDIS_NIF] <---+ DRIVERNAME = AEXNDS$ | IOBASE = 0x300 | INTERRUPT = 15 | These names must match! | [PKTDRV] | DRIVERNAME = PKTDRV$ | BINDINGS = AEXNDIS_NIF <---+ INTVEC = 0x61 CHAINVEC = 0x66 NOVELL = Y Note that the name "AEXNDIS_NIF" must exactly match the spelling used as the title of the previous section, "[AEXNDIS_NIF]"; if you are not using Artisoft interface cards, then both occurences will use some other identifier. The "INTVEC" parameter may be anything from 0x60 to 0x80; you may have to experiment to find an unused interrupt number. 2.4 Packet Driver Shims for Banyan Vines Although Key Software Products has never used it, and thus cannot offer help on its installation, a packet driver shim does exist for Banyan Vines and can be downloaded from the Key Software Products BBS as file BAN-SHIM.ZIP. 2.5 Other Things to Configure Once your network is up and running with a packet driver or a packet driver shim, there are basically two additional steps: 1. Create a WATTCP.CFG configuration file. 2. Configure KSP FTP as a BBS door. As discussed in the next chapter, you may not need a WATTCP.CFG configuration file if you have a BOOTP server. There is a useful program called TCPINFO available on the KSP BBS. If you have no WATTCP.CFG file, it will tell you (after a maximum of 30 seconds) if it was able to automatically configure itself via a BOOTP server. If you have a WATTCP.CFG file, it will determine whether or not you have configured that file properly. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 8 CHAPTER 3 - THE WATTCP CONFIGURATION FILE In order to run, KSP FTP needs to know some information about your network, and tries to find this in a configuration file called WATTCP.CFG. KSP FTP looks in three directories to locate this file. First, it checks for an environment variable called WATTCP.CFG that specifies the directory. Second, it looks in the current (default) directory. Third, if still not found, it looks in the directory that contains the executable (KSP-FTP.EXE). The following example may be helpful for those using the environment variable approach: If you place WATTCP.CFG in your PCB directory, then your AUTOEXEC.BAT file should contain the following command: set WATTCP.CFG=C:\PCB Note that there is no trailing "\" after the directory name! If KSP FTP still can't find the configuration file, it will attempt to automatically configure itself by looking for a "BOOTP" server on your network. (BOOTP is a standard protocol that obtains your "IP address" and other information about your PC from a BOOTP server.) If there is no BOOTP server, or if your PC is not registered in its database, then you must create a configuration file. The configuration file contains one entry per line. A sample configuration file is included in this distribution, but the values MUST be modified to suit your particular environment or else KSP FTP will not work! The syntax of every entry follows the following format: [ directive = [ "data" | data] ] [ # comment | ; comment ] I.e., if a directive is not followed by data, the directive is ignored. Similary, lines without directives are ignored. The directive is NOT case sensitive; the data IS case sensitive. e.g., netmask=255.255.252.0 domainslist=ksp.com ; Our domain Whitespace is normally removed from data; data containing blanks must be surrounded by quotes. An unquoted '#' or ';' marks the beginning of a comment. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 9 3.1 Multiple Nodes and the "include" Directive There must be one WATTCP.CFG file for each BBS node since each node has to be configured with a unique hostname and IP address. All other configuration parameters are usually set at the same values for all nodes. Rather than duplicating these common entries in each WATTCP.CFG file, you can set-up a master configuration file that gets "included" in each of the node-specific files. For example, the node-specific file (WATTCP.CFG) might look like: include=c:\ksp\master.cfg hostname=ourbbspc myip=125.283.210.17 This makes it much easier to make changes since you only have to modify a single file (MASTER.CFG). 3.2 Using a BOOTP Server It's always a good idea to have a configuration file whether or not you use a BOOTP server. If you choose to use a configuration file and want to tell it to use the BOOTP server, this option allows you to specify your the IP address of your BOOTP server. Example: bootp=129.255.0.128 You should specify the domain name manually as described in the next section since the BOOTP protocol doesn't provide that information. Example: domainslist=ksp.com NOTE: An "IP address" is a logical addressing scheme used on TCP/IP networks such as the Internet. Each computer connected to the Internet is assigned a unique IP address. Your local network "guru" or access provider should be able to provide you with those IP addresses you need. IMPORTANT: The IP addresses given in this document are only examples. Do NOT attempt to use them - they will NOT work and your network administrator will probably get VERY upset! Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 10 3.3 Manual Configuration If you don't have a BOOTP server, or if your PC is not registered with a BOOTP server, then you must use the following directives to configure KSP FTP. The values of these parameters are important, and KSP FTP will NOT function properly without the proper values. If you are not familiar with the terminology, or if you are unsure of the proper values, please consult with your network access provider. 3.3.1 The PC's Host Name This is the network name of the PC that runs your BBS (and thus KSP FTP). If your BBS is implemented by a network of PC's, then each PC should have its own unique host name. Example: hostname=bbs Note that the host name does not include the domain name suffix. For example, the hostname of machine '"bbs.ksp.com" is simply "bbs". 3.3.2 The PC's Domain Name This is the network name of the subnet to which your PC (and possibly others) are connected. Example: domainslist=ksp.com Note that the domain name does not include the host name prefix. For example, the domain name of machine '"bbs.ksp.com" is "ksp.com". 3.3.3 The PC's IP Address This is the unique IP address assigned to your PC. Example: my_ip=100.2.37.4 Your local network "guru" or access provider should be able to provide you with the proper IP address of your PC. Note that you should have a different IP address for each node in your BBS. Note: As an alternative, you may also set the IP address using an environment variable, as in: Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 11 set ksp-ip=100.2.37.4 3.3.4 The Name Server's IP Address This is the unique IP address assigned to a network name nerver. You may specify more than on nameserver by using more than one "nameserver" line. Example: nameserver=111.21.108.110 Your local network "guru" or access provider should be able to provide you with the proper IP addresses of appropriate network name servers. 3.3.5 The Router's IP Address This is the unique IP address assigned to the network router. Syntax: gateway = ipaddr [ , subnet [ , subnet_mask ] ] Examples: gateway=129.97.176.1 gateway=129.97.176.2, 129.97.0.0 gateway=129.97.176.2, 129.97.0.0, 255.255.0.0 Usually the (destination) subnet and subnet mask need not be specified, and is used to create a "default". The other forms are used to specify one or more other gatewaya for particular subnets. Your local network "guru" or access provider should be able to provide you with the proper IP address of the network router. 3.3.6 The PC's Network Mask Network masks are used to distinguish destination IP addresses that are on the local subnet from those that are not. This option may not be required, depending on your network topology. Example: netmask=255.255.254.0 Your local network "guru" or access provider should be able to provide you with the proper netmask if needed. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 12 3.4 TCP/IP Parameters (optional) KSP FTP will work without using the following parameters, but they are provided if you wish to change them. 3.4.1 DNS Search Mode A remote hostname (e.g., ralph.ksp.com) is translated into an numeric IP addresse (e.g., 128.16.202.12) by a nameserver. Sometimes, however, users enter hostnames in an abbreviated form. For example, if the local machine (e.g., ruby.ksp.com) was in the same domain (ksp.com) as the remote host (ralph.ksp.com), then perhaps only the remote hostname (ralph) might be given. Short versions like this must be fully expanded (e.g., ralph.ksp.com) before a nameserver can translate them into an IP address. Waterloo TCP/IP solves this by feeding the nameserver with a sequence of constructions formed from the remote hostname and the local machine's domainslist. For a remote hostname given as "a.b" and a domainslist specified in WATTCP.CFG as "c.d", Waterloo TCP/IP would attempt name server lookups first on "a.b.c.d", then on "a.b.d", and then on "a.b". Although this approach is guaranteed to find the appropriate construction, it can waste time performing nameserver lookups on improbable constructions. Consider the sequence of constructions attempted when the remote hostname is "garbo.uwasa.fi" and the local domainslist is "ksp.com": (1) garbo.uwasa.fi.ksp.com -> fails (2) garbo.uwasa.fi.com -> fails (3) garbo.uwasa.fi -> succeeds We've modified Waterloo TCP/IP's search strategy to accelerate name server lookups by adding three optional mode variations, enabled by specifying one of the following WATTCP.CFG configuration parameters: dns_search_mode=map_local_names Abbreviated (local) hostnames that do not contain a period are processed in the normal (Waterloo TCP/IP) manner. Otherwise, hostnames like "garbo.uwasa.fi" are attempted immediately without modification. This is the recommended search mode. Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 13 dns_search_mode=fully_specified This mode passes the hostname directly to the nameserver without modification. I.e., it assumes that hostnames are always fully specified by the user without abbreviation. Abbreviated names will not be translated and will be returned by the nameserver as unknown. dns_search_mode=recognized_root Remote hostnames ending in the common domain suffixes (com, edu, gov, mil, net, org, nato, arpa) are attempted immediately without modification. All other hostnames are processed in the normal manner. (Note that this mode is no better than the normal Waterloo TCP/IP strategy with names like "garbo.uwasa.fi".) 3.4.2 Timeouts Most network operations (such as establishing a connection to a remote host) have a maximum time before a timeout error occurs. The default value is 30 seconds; a smaller value is unwise, but larger values may be necessary for particularly bad connections. Example: sockdelay=40 3.4.3 Maximum Segment Size (MSS) The default value of MSS is 1400. If you know what maximum segment size means and know what size you want, you can change it: Example: mss=512 Note: Some Internet access providers configure their dial-up slip and ppp accounts with a very small segment size. You may need to set mss as low as 212 if your Internet connection is through such a connection. 3.5 FTP Operating Parameters The remaining parameters in WATTCP.CFG are operating parameters for KSP FTP that define limits and display files needed while KSP FTP is running. Each follows the format: Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 14 ksp-ftp.= where and are replaced by appropriate strings. Some operating parameters have counterparts in other members of the KSP family of network application programs. Rather than have multiple entries in the WATTCP.CFG file for each application, such parameters can be specified globally using the format: ksp.= This global setting can be overridden for a specific application by using the application-specific form at a subsequent line in WATTCP.CFG. 3.5.1 Dynamic Parameters Configuration file parameters can be made "dynamic". Such parameters are ignored unless activated by an associated command line option: /CONFIG= where "" is a non-zero integer. Dynamic configuration parameters are those that specify a number in square backets as in: ksp-ftp[].= The number specified in the configuration parameter must match that in the command line option or else the configuration parameter will be ignored. This also works for dynamic global parameters of the form: ksp[].= Copyright (C) 1995-96, Key Software Products. All Rights Reserved Sep 01, 1996 KSP FTP (tm) v3.0 15 3.5.2 Retrieving Hostname of Remote Server Syntax: ksp-ftp.retrieve_hostnames=