FTT Version 1.12 BETA (7/10/95) - Quick Docs File Transfer Test --------------- ! WARNING ! THIS IS A BETA RELEASE OF THIS PROGRAM. USE AT YOUR OWN RISK Changes from v1.11B: 1. Includes USRSTAT2.EXE v4.03B, no changes in FT.PPE Changes from v1.10B: 1. Includes USRSTAT2.EXE v4.02B, no changes in FT.PPE Changes from v1.09B: 1. Modified for use with USRSTAT2.EXE V4.x. Color is disabled. 2. Included USRSTAT2.EXE module V4.01B. Installation of BETA update: 1. Copy the new PPE over the old one. 2. Copy the new USRSTAT2.EXE module over the old one. ---------------------------------- FTT (FT.PPE) is a "Door" program for PCBoard BBS software that is designed to perform file transfer testing in a controlled, repeatable manner, and provide complete statistic reporting in a uniform format. This program can optionally use my USRSTAT2.EXE program to include modem diagnostic info in the report, when used in conjunction with an applicable USRobotics modem and proper setup as described in the documentation for the STPCB program. This program *requires* the use of Chuck Forsberg's DSZ file transfer protocol program, and can be optionally configured to work with Sam Smith's HSLINK bi-directional protocol. This program is fully and automatically multi-node aware. ---------- Installation: Create a directory of your choice to install the FT.PPE file. This will be referred to as the "Home" directory. Example; C:\PCB\FTHOME FTT requires read/write access to this directory. FTT will also look to this directory for all file uploads and downloads, so be sure to install this on a drive with plenty of free space! Now, create another directory off of the "Home" directory, named \DL Example; C:\PCB\FTHOME\DL This \DL directory is the directory which will hold the files you wish to make available for downloading in this door. I recommend using the test files in TSBFILES.ZIP, although you may use any files you like. Note that using the TSBFILES will provide more useful output data, since these are the current industry standard files for throughput and compression testing. This directory and its files will not be modified by FTT. If you wish to change the set of download files, simply move or copy files to/from this directory, and they will automatically appear on the FT user menu. That takes care of the download file set, but what about files that the user uploads? (Gotta test both directions, you know!) FTT will create another directory off of the "Home" directory, called \UL. It will then further create another directory off of the \UL directory, which includes the NODE NUMBER the caller is currently on. Thus, when a user on node 4 opens the door, a directory named C:\PCB\FTHOME\UL\4 would be created, assuming the "Home" directory given in the previous examples. This directory will REMAIN on the disk after the door is exited, but any files the user uploaded during the test will be removed so as not to clutter up the drive any more than necessary. NOTE THAT THE DOOR WILL CREATE THE UPLOAD DIRECTORIES ON THE FLY, YOU ONLY NEED TO CONCERN YOURSELF WITH THE DOWNLOAD DIRECTORY PREVIOUSLY DESCRIBED. ALSO NOTE THAT THIS DOOR DOES NOT REQUIRE THE USE OF ANY OF THE FILE AREAS DEFINED IN YOUR PCBOARD SETUP. ALL TRANSFERS DONE IN THIS DOOR ARE COMPLETELY INDEPENDENT OF ANY OF PCBOARD'S SECURITY AND PATH RESTRICTIONS. THIS DOOR DOES NOT USE THE FILE TRANSFER BATCH FILES FROM PCBOARD, IT CALLS THE TRANSFER PROTOCOL PROGRAMS DIRECTLY, WITH SOME PARAMETERS HARD-CODED AND OTHERS DEFINABLE IN THE FT.CFG CONFIG FILE. When downloading the report files, the door DOES use PCBoard's standard file downloading services, but it remains independent of PCBoard's file path restrictions. ----------- The Configuration File The door will look in the "Home" directory for a configuration file named "FT.CFG". A sample file named "FT.DEF" is included in the distribution archive, and will be created in the home directory at run- time if no config file is found. This file controls certain aspects of the report format, and how the report is delivered to the user. It also controls the use of HSLINK and USRSTAT2. This sample file is self-documenting, so I will refer you to that file for an explanation of the various options and what they control. NOTE YOU MUST EDIT THE FT.DEF FILE TO SUIT YOUR INSTALLATION, AND THEN ** RENAME IT TO FT.CFG ** ------------ The Welcome File The door will search the "Home" directory for a file named FT.WLC, and will display it to the caller upon entry to the door. You may put anything you wish in this "Welcome" file. This display file is entirely optional. ------------ PCBoard Setup To install the program in PCBoard, you need to run PCBSETUP and modify the CMD.LST file for the Main Board and/or any conferences you wish to be able to run the door from. Refer to your PCBoard documentation for more details on installing a PPE program. ----------- The door must also be able to find DSZ.COM (or DSZ.EXE), and HSLINK.EXE (if so configured) somewhere in the DOS path. They do not have to be in the home directory, as long as they are in your path somewhere. ----------- When the user enters the door, a menu similar to the following is displayed: 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � The Majestik Moose � � File Transfer Test - Version 1.12B � � �袴袴袴袴袴袴袴袴袴袴袴袴袴敲 �袴袴袴袴袴袴袴袴袴袴袴袴袴敲 � � � Download Batch � � Upload Drive � � � � 컴컴컴컴컴컴컴컴컴컴컴컴� � � 컴컴컴컴컴컴컴컴컴컴컴컴� � � � � ABCD.TST 184071 � � 48205270 Bytes Free � � � � 1X30.TST 984532 � � � � � � 3X06.TST 131072 � � � � � � ZIPF.TST 243221 � � � � � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴� 훤袴袴袴袴袴袴袴袴袴袴袴袴袴� � � �袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴敲 � � � Current Protocol: Zmodem � � � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴� � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� The file names and sizes will vary depending on what you have placed in the \DL directory, of course. The BBS name will be whatever you have entered in PCBSETUP as your board's name. The following command menu will also be displayed: (D)ownload, (U)pload, (P)rotocol, or (Q)uit The D and U functions will begin the download or upload using the currently selected protocol. The P function will toggle the protocol between Zmodem and Ymodem-G, and optionally, HSLink. When HSLink is selected, the command menu is as follows: (B)egin transfer, (P)rotocol, or (Q)uit The B function will begin HSLink in bi-directional mode, the P function will again toggle the protocol back to Zmodem. When downloading, the user is automatically sent all of the files that appear in the \DL directory, using batch mode. The user is NOT required to "Flag" or "Select" anything. When uploading, the user is NOT asked for file names or descriptions. The door simply goes into batch receive mode, and will keep receiving as many files as the user sends in a batch transfer. Remember that the files are directed into the private node directory (\UL\nnn) so there aren't any problems with uploading files that are already on the system, and multiple users can even be uploading the same files simultaneously. After the transfer is completed, the door will examine the log file created by DSZ or HSLINK, and create a report. This report is automatically sent to the user THROUGH THE PCBOARD MESSAGE BASE, IN WHATEVER CONFERENCE THE USER IS CURRENTLY IN, OR AS DEFINED IN THE FT.CFG CONFIG FILE. The door may also be configured to allow the user to download the report file, using the standard PCBOARD file download mechanism. The report file consists of a header to identify the caller, and a series of entries for each file transferred. Most of the fields are pretty self-explanatory. The FLOW field indicates the number of flow control stoppages the modem enacted. If this number is 0 when SENDING, this is an indication that the CPU is not sending data fast enough for the modem. The ERR field indicates the number of error corrections performed BY THE TRANSFER PROTOCOL. A non-zero number here renders the stats for that file somewhat questionable, since throughput usually suffers during the re-send of the data. Errors appearing here are usually caused by UART buffer over-runs on the receiver side, or incorrect flow control settings on the sending side. If the USRSTATS option is enabled, the report will also contain a standard USRSTATS report. Refer to the USRSTATS docs for further details on the report. ----------------------------------------- This program has been tested at The Majestik Moose BBS running a single node under DesqView and Lantastic, and at the USRobotics Support BBS running multi-node under Desqview and NetWare. It has been tested with DSZ.COM, DSZ.EXE, and HSLINK.EXE protocols, using standard serial port hardware. ----------------------------------------- Helpful Hints: Do *not* use any DSZ environment variables that might affect the target directory of UPLOADED files! FTT must be allowed to direct uploads into its own work directory. You MUST have the DSZLOG environment variable set to indicate the name of the log file that DSZ will use. ----------------------------------------- Send comments/bug reports to: Joseph C. Frankiewicz The Majestik Moose BBS 708-843-2871 ----------------------------------------- [END]