Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / LABTST34.ZIP / LABTEST.DOC < prev next >

Wrap

Text File | 1996-03-09 | 98.0 KB | 2,510 lines

Labtest 3.4 User's Guide Copyright c 1992-1995 Mark Williamson Omega Software Labtest 3.4 User's Guide Note: It is important that you read this documentation in depth. Most common problems are caused by an incorrect setup. 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 What is Labtest and What Does It Do? . . . . . . . . . . 5 1.2 Thanks for Trying Labtest! . . . . . . . . . . . . . . . 7 1.3 Labtest Copyright Information . . . . . . . . . . . . . 7 1.4 License Agreement . . . . . . . . . . . . . . . . . . . 7 1.5 The Beta Team . . . . . . . . . . . . . . . . . . . . . 9 1.6 Acknowledgments . . . . . . . . . . . . . . . . . . . . 9 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . 10 2.1 Hardware Requirements . . . . . . . . . . . . . . . . . 10 2.2 Communications Output . . . . . . . . . . . . . . . . . 10 2.3 Memory Swapping . . . . . . . . . . . . . . . . . . . . 10 2.4 External programs . . . . . . . . . . . . . . . . . . . 11 3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 11 4 Menu Navigation . . . . . . . . . . . . . . . . . . . . . . . . 12 5 Configuration Options . . . . . . . . . . . . . . . . . . . . . 13 5.1 Files/Paths . . . . . . . . . . . . . . . . . . . . . . 13 5.1.1 Log File Path . . . . . . . . . . . . . . . . . . . 13 5.1.2 Swap Path . . . . . . . . . . . . . . . . . . . . . 14 5.1.3 Bad File Path . . . . . . . . . . . . . . . . . . . 14 5.1.4 ANSI Screen File . . . . . . . . . . . . . . . . . 14 5.1.5 ASCII Screen File . . . . . . . . . . . . . . . . . 15 5.1.6 RIP Screen File . . . . . . . . . . . . . . . . . . 15 5.1.7 Screen Control File . . . . . . . . . . . . . . . . 15 5.1.8 Kill File List . . . . . . . . . . . . . . . . . . 15 5.1.9 Add File List . . . . . . . . . . . . . . . . . . . 16 5.1.10 Message Import Text . . . . . . . . . . . . . . . 16 5.1.11 Hack File Name . . . . . . . . . . . . . . . . . . 16 5.1.12 Archive Comment File Name . . . . . . . . . . . . 16 5.1.13 Inbound TIC Directory . . . . . . . . . . . . . . 17 5.1.14 Duplicate File Database . . . . . . . . . . . . . 17 5.1.15 Anti-BBS Ad Text File . . . . . . . . . . . . . . 18 5.1.16 TIC Configuration File . . . . . . . . . . . . . . 18 5.1.17 Editor Command . . . . . . . . . . . . . . . . . . 18 5.1.18 Skip List . . . . . . . . . . . . . . . . . . . . 18 5.2 BBS Setup . . . . . . . . . . . . . . . . . . . . . . . 19 5.2.1 BBS System . . . . . . . . . . . . . . . . . . . . 19 5.2.2 File System Path . . . . . . . . . . . . . . . . . 19 5.2.3 Set Security Level . . . . . . . . . . . . . . . . 19 5.2.4 Remote Status Window . . . . . . . . . . . . . . . 20 5.2.5 Sysop Message Info . . . . . . . . . . . . . . . . 20 ii Labtest 3.4 User's Guide 5.2.5.1 Sysop Message Board . . . . . . . . . . . . . . 20 5.2.5.2 Message Base Path . . . . . . . . . . . . . . . 20 5.2.5.3 Message Base Type . . . . . . . . . . . . . . . 20 5.2.6 User Message Info . . . . . . . . . . . . . . . . . 21 5.2.7 Select User Messages . . . . . . . . . . . . . . . 21 5.2.8 Select Sysop Messages . . . . . . . . . . . . . . . 22 5.3 System Options . . . . . . . . . . . . . . . . . . . . . 22 5.3.1 Sysop Name . . . . . . . . . . . . . . . . . . . . 22 5.3.2 BBS Name . . . . . . . . . . . . . . . . . . . . . 22 5.3.4 Registration Key . . . . . . . . . . . . . . . . . 22 5.3.4 Max File Age . . . . . . . . . . . . . . . . . . . 22 5.3.5 Sound Virus Alarm . . . . . . . . . . . . . . . . . 22 5.3.6 Swapping method . . . . . . . . . . . . . . . . . . 23 5.3.7 DOS Window Height . . . . . . . . . . . . . . . . . 23 5.3.8 Minimum Disk Space . . . . . . . . . . . . . . . . 23 5.4 GIF Options . . . . . . . . . . . . . . . . . . . . . . 24 5.4.1 Check GIF Age . . . . . . . . . . . . . . . . . . . 24 5.4.2 Minimum GIF Width . . . . . . . . . . . . . . . . . 24 5.4.3 Minimum GIF Height . . . . . . . . . . . . . . . . 24 5.4.4 Minimum GIF Colors . . . . . . . . . . . . . . . . 24 5.4.5 GIF Separator Character . . . . . . . . . . . . . . 24 5.4.6 Compress GIF Files . . . . . . . . . . . . . . . . 24 5.4.7 Uncompress JPG Files . . . . . . . . . . . . . . . 25 5.5 Archive File Options . . . . . . . . . . . . . . . . . . 25 5.5.1 Default Archive Type . . . . . . . . . . . . . . . 25 5.5.2 Maximum Old File Percentage . . . . . . . . . . . . 25 5.5.3 File Date Options . . . . . . . . . . . . . . . . . 25 5.5.4 Convert SFX Files . . . . . . . . . . . . . . . . . 26 5.5.5 Pack Unknown Files . . . . . . . . . . . . . . . . 26 5.5.6 Keep Security . . . . . . . . . . . . . . . . . . . 26 5.5.7 Imbedded Archives . . . . . . . . . . . . . . . . . 26 5.5.8 Process Descriptions . . . . . . . . . . . . . . . 27 5.5.9 Maximum File Size . . . . . . . . . . . . . . . . . 27 5.5.10 Maximum Duplicate Files . . . . . . . . . . . . . 27 5.5.11 Maximum Duplicate File Percentage . . . . . . . . 27 5.5.12 Maximum Advertisement File Size . . . . . . . . . 28 5.5.13 Delete BBS Advertisements . . . . . . . . . . . . 28 5.5.14 Adjust User Credit . . . . . . . . . . . . . . . . 28 5.5.15 Failed Scan Action . . . . . . . . . . . . . . . . 28 5.6 Archiver Setup . . . . . . . . . . . . . . . . . . . . . 29 5.6.1 Archive Extension . . . . . . . . . . . . . . . . . 29 5.6.2 Unpack Command Line . . . . . . . . . . . . . . . 29 5.6.3 Pack Command Line . . . . . . . . . . . . . . . . . 30 5.6.4 Comment Command Line . . . . . . . . . . . . . . . 30 5.6.5 Video . . . . . . . . . . . . . . . . . . . . . . . 31 5.7 Virus Scanner Setup . . . . . . . . . . . . . . . . . . 32 5.7.1 Scan Command Line . . . . . . . . . . . . . . . . . 32 5.7.2 Errorlevels . . . . . . . . . . . . . . . . . . . . 33 iii Labtest 3.4 User's Guide 5.7.4 Enable . . . . . . . . . . . . . . . . . . . . . . 33 5.7.5 Scan Log Text . . . . . . . . . . . . . . . . . . . 33 5.8 Description Settings . . . . . . . . . . . . . . . . . . 34 5.8.1 Word Wrap . . . . . . . . . . . . . . . . . . . . . 34 5.8.2 Add Uploader's Name . . . . . . . . . . . . . . . . 34 5.8.3 Remove High Ascii . . . . . . . . . . . . . . . . . 35 5.8.4 Strip ANSI codes . . . . . . . . . . . . . . . . . 35 5.8.5 Strip @ codes . . . . . . . . . . . . . . . . . . . 35 5.8.6 Maximum characters per line . . . . . . . . . . . . 35 5.8.7 Maximum lines per description . . . . . . . . . . . 35 5.8.8 Description Continuation Offset . . . . . . . . . . 35 5.8.9 Description Continuation Character . . . . . . . . 36 5.8.10 Description Comments . . . . . . . . . . . . . . . 36 6 Using LTSetup to Process Your Files . . . . . . . . . . . . . . 36 6.1 Process TIC Files . . . . . . . . . . . . . . . . . . . 36 6.2 Select Files . . . . . . . . . . . . . . . . . . . . . . 36 6.3 CD-ROM Support . . . . . . . . . . . . . . . . . . . . . 36 6.4 Convert . . . . . . . . . . . . . . . . . . . . . . . . 37 6.5 Scan . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.6 Override . . . . . . . . . . . . . . . . . . . . . . . . 37 6.7 Begin . . . . . . . . . . . . . . . . . . . . . . . . . 37 7 Printing/Exporting Your Configuration File . . . . . . . . . . 37 8 Using the Auto Test Feature . . . . . . . . . . . . . . . . . . 38 9 Customizing Labtest's Displays . . . . . . . . . . . . . . . . 38 10 Running Labtest . . . . . . . . . . . . . . . . . . . . . . . 38 11 External Program Errorlevels . . . . . . . . . . . . . . . . . 41 12 Registration, warranty and licensing . . . . . . . . . . . . . 43 13 Customer Support Policy . . . . . . . . . . . . . . . . . . . 44 14 Registration Form . . . . . . . . . . . . . . . . . . . . . . 46 iv Labtest 3.4 User's Guide 1 Introduction 1.1 What is Labtest and What Does It Do? Labtest is a program designed to process files received by a computer Bulletin Board System (BBS). However, Labtest is not just for the operators of BBS's. If you use your modem to download files from BBS's, you can use Labtest to maintain your files and a list containing descriptions about each file. Some of Labtest's many features are: Completely customizable! All display, message and language files can be modified to suite your tastes. Support for the Hack List - searches the HACK.IDX/HACK.COL and fails the file if it exists in the list, logging the reason to the log file. Can be configured to skip files, ensuring that files you want untouched are never processed. Adjust a user's security level if they upload a file which contains a virus. Appends the file description with information about the status (pass/fail) and the reason for failure. Will also add the file count, oldest and newest dates to the description as well as the uploader's name. Advanced file description handling. You can have Labtest remove graphics codes (ANSI/PCBoard), IBM box characters (referred to as HIGH ASCII), word wrap the description using specified line lengths, set a maximum number of lines to import and more! Honors archive security (configurable). Automatically detects archive formats using the archive signature. Convert from any supported archive format to any other. Execute up to 20 virus scanners for the most thorough protection possible. All virus scanners are user definable. Can capture multiple errorlevels from a single pass (very useful for Thunderbyte) Can be configured to record the virus scanner log information and write it to the log file, user message and/or sysop message. 5 Labtest 3.4 User's Guide Duplicate file protection. Checks the files inside archives against your duplicate file database. You may define a maximum duplicate percentage or count, or both. Checks all files in the archive, even in subdirectories to any level. Detect and optionally remove unwanted bulletin board advertisements based on a text string search and/or filename comparison. Process inbound .TIC files, automatically add the files to the file system and process them according to the defined settings. No downlink options (yet!) Writes one or more detailed messages to the user and Sysop pertaining the uploaded file. Each message can be enabled or disabled. The message text is fully customizable, including several macros for system information. Reads .GIF files for resolution information and imports this info into the file data base. Can fail GIFs that are less than a defined resolution. Convert GIF files to JPG format as well. Thorough online help to guide you through the configuration phase. May be configured to fail archived files based on age, including percentage of old files. Again, supporting imbedded archives and subdirectories to any level. Integrates seamlessly with any RemoteAccess 2.xx, Proboard 2.xx, or QuickBBS 2.80 (Classic/GoldBase) bulletin board system or any system using FILES.BBS. Even if you do not use a BBS, you can still use Labtest to process files you may download from other bulletin board systems. Supports several message base formats: JAM, Hudson, GoldBase, *.MSG, Squish and PCBoard. Supports extended FILES.BBS formatting used by Proboard 2.xx. Supports the PCBoard DIR file format. Supports lengthy FILES.BBS descriptions by indenting to a specified column and optionally add a lead character, for example the '|' before each continuation line. 6 Labtest 3.4 User's Guide Complete configuration validation, will test availability of files and directories, locate archive utilities and virus scanners, automatically inputs command paths. 1.2 Thanks for Trying Labtest! Labtest is an easily-configured, very powerful method of automatically testing all files received on a BBS system, whether they are received from callers as an upload, via standard file distribution channels (TIC files), or by downloading from other systems. There are now two versions of the Labtest software. This SHAREWARE version, and a separate package known as Labtest/Pro. The professional package is the complete, full version of Labtest, with additional features not available in the shareware version, plus the extra utilities disk. The professional version of Labtest is not SHAREWARE, and thus cannot be freely distributed. If you have already purchased the shareware version of Labtest, then your registration key will also work with this shareware package, however, it will not work with the professional version. If you would like to upgrade to the professional version, or would like additional information, please contact Omega Software. Upon registering this package, you will receive a registration key that will remove the UNREGISTERED screen. You registration key will work in any shareware version of Labtest. 1.3 Labtest Copyright Information Labtest, including the online information and text documentation, is the copyrighted creation of Mark Williamson, Copyright c 1992 - 1995. It has been thoroughly tested on many different system configurations and has been found to work as described in this manual. It is not guaranteed, however, to function perfectly on your system. If you discover a problem, the author will work with you to determine the cause of the problem and the best solution. 1.4 License Agreement This is a licence agreement between you, the end user, and Mark Williamson, hereafter "the author". The Labtest software and information attached hereto, hereafter "LABTEST", is the property of the author. Read the terms and conditions of this licence agreement carefully before using the software. If you for any reason, whatsoever, cannot accept the conditions in this agreement, you are not permitted to use LABTEST. 7 Labtest 3.4 User's Guide You acknowledge and agree that LABTEST is a proprietary product of the author, protected by applicable copyright laws and international treaty provisions. You further acknowledge and agree that all rights, title, and interest in and to LABTEST are and shall remain with the author. LABTEST may be used for a period of thirty (30) days on a trial basis to allow you to determine its suitability for your particular application. After this period you MUST register each copy of LABTEST that you run simultaneously. Registration entitles you to a non-transferable licence to use LABTEST and any future versions of LABTEST for as long as you wish, subject to any special licensing conditions and/or applicable upgrade fees attached to future versions. Any given version of LABTEST is considered obsolete if the file date of the executable file LABTEST.EXE is more than six months old. Due to continuous development, the author will not provide support on obsolete versions of LABTEST. Users are encouraged to contact the author for information regarding the latest version and any planned future releases. In the event that you are in violation of this licence agreement, you agree and accept that the author may cancel your registration and any rights to use LABTEST that you may have. In the case of a dispute over the licence agreement, you further agree and accept to fully reimburse the author for legal and other expenses resulting from the dispute, should the dispute be decided in favor of the author. LABTEST is provided "as is", without warranty of any kind or fitness for a particular purpose, either expressed or implied, all of which are hereby explicitly disclaimed. The author only guarantees that Labtest will occupy disk space. The author's liability resulting from your use or inability to use LABTEST is limited to the amount that the affected party has paid for it, or in the event that LABTEST was registered with a third party for payment to the author, liability is limited to the amount that was received by the author from that third party. Neither the author nor any of his employees, agents, or other representatives are in any way obligated to provide future versions of, or support for, LABTEST. You may freely distribute and copy LABTEST provided that no fee is charged and the LABTEST distribution archive contains unmodified copies of the original files as produced by the author. Pay 8 Labtest 3.4 User's Guide Bulletin Board Systems may, however, charge their normal fee provided that no additional charge for LABTEST is levied. No part of LABTEST may be modified, altered, reverse engineered, sold, or distributed in any form whatsoever which would involve some sort of trade without prior written permission from the author. 1.5 The Beta Team Labtest and the accompanying files are a collective work of the efforts of many people, without whose involvement this project would not have been possible. I wish to express my sincere gratitude to those who participated in the beta testing of this fine software! 1.6 Acknowledgments Due to its complexity, Labtest uses code and information provided from numerous sources. Here are the required notations: The Graphics Interchange Format c is the Copyright property of CompuServe Incorporated. GIF (sm) is a Service Mark property of CompuServe Incorporated. This product uses the JAM (mbp) API - Copyright c 1993 - 1994, Joaquim Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS RESERVED. This product uses the RIPscrip language, Copyright c 1993 - 1994, Telegrafix Communications, Inc. RemoteAccess, RACONFIG, RAMGR, and RA are Copyright c 1993 - 1994, Andrew Milner. Proboard and PROCFG are Copyright c 1993-1994, Philippe Leybaert. QuickBBS and GoldBase are Copyright c 1994, Steve Gabrilowitz. This product uses the OpenDoors library, Copyright c 1994, Brian Pirie. 2 System Requirements 2.1 Hardware Requirements Labtest requires an IBM(TM) compatible computer system with at least 512k of memory, one megabyte of free drive space and a VGA monitor is recommended. Labtest has been tested on numerous platforms ranging from a basic 80286 computer with a 40 megabyte 9 Labtest 3.4 User's Guide hard drive to a Pentium 90 using OS/2. The author's system is an 80486dx2/80, 12 megabytes of memory, a 1.210 gigabyte hard disk and using Microsoft (tm) Windows For Workgroups 3.11 with QEMM 7.50. 2.2 Communications Output Labtest's serial communications are conducted using OpenDoors 5.0, by Brian Pirie. All communications are managed by the resident Fossil driver. Modem speeds from 2400 - 28.8k baud have been tested. Slow speed modems have the worst performance due to the fact that Labtest is very fast and the output to the remote terminal doesn't appear to 'keep up.' However, under testing, the output was near perfect, with the exception of a few dropped characters. This peculiarity is being worked on constantly. However, with the flow of modem users going away from 2400 baud, this is not anticipated to cause problems. 2.3 Memory Swapping Labtest may use EMS memory for the swap file when running your external programs if it is available. If not, Labtest will swap to disk instead. If you are using DesqView, it is recommended that you make an additional 400k of EMS/XMS memory available to Labtest to enhance performance. When Labtest has swapped out of memory, a small segment (less than 300 bytes) is left in memory to reload Labtest when the external process is completed. 2.4 External programs Labtest uses many external programs which you will define in LTSetup. Following is a list of archive utilities that Labtest currently supports PKZIP 2.04g ARJ 2.41a LHA 2.22 PAK 2.51 PKPAK/PKUNPAK 3.61 PKARC/PKXARC 3.5 LHARC 1.13 RAR 1.50 beta ZOO 2.01 UC2 (Ultra Compressor II) Also, Labtest has been tested with the following virus scanners: 10 Labtest 3.4 User's Guide McAffee's VirusScan (V.119 and 2.0) Frisk Software's F-Prot MicroSoft Anti-Virus ThunderByte Anti-Virus 3 Installation Labtest is distributed in an archive file using the base name of LABTSTxx (where xx is the version number). You should follow these easy steps to ensure a flawless installation: Create a directory where Labtest and its associated files are to reside: MD \LABTEST After you have created this directory, change to it by typing: CD \LABTEST Labtest comes preconfigured using the directory name C:\LABTEST for all of its paths and filenames. You can save yourself some time by using this default installation directory! You may want to add the LABTEST directory to your path statement in your AUTOEXEC.BAT file. Load the AUTOEXEC.BAT file into your favorite editor, and locate the line containing the PATH= statement. Add your LABTEST directory to the end of this line. This is not required by Labtest, but it is recommended so you can execute Labtest from any drive/directory on your system. Using the appropriate archive utility, unpack the distribution archive into your newly created Labtest directory. If you are installing Labtest 3.4 over an older version, it is strongly recommended that you make a backup copy of your previous version and ensure that you REMOVE the previous version. If you attempt to load a configuration file for an older version, Labtest and LTSetup will inform you of this error. Once you have unpacked the archive, execute LTSETUP.EXE to begin configuring your copy of Labtest. Each individual option and command is described in the following pages. You may also use the extensive online help system to guide you through the process. Labtest and LTSetup expect all of the Labtest files they will be using to be in the same directory as LABTEST.EXE and LTSETUP.EXE. You do not need to set any environment variables specifically for 11 Labtest 3.4 User's Guide Labtest. For each system that Labtest supports, there is a .DOC file for information on specific installation. Decompress the file BBS.ZIP and review the appropriate documentation for your BBS software. After you have unpacked your copy of Labtest, configuration is the next step. 4 Menu Navigation LTSetup is written using TCXL 6.12 from Innovative Data Concepts. The TOP menu is a horizontal pulldown menu. You may move the selection bar left and right by using the left/right arrow keys. To select an option, you 'pull' it down using the down arrow key (or hit enter). Lower menus are called vertical menus. The left/up and right/down keys move the menu bar up and down respectively. Two types of items are available throughout the menu structure. Items you 'toggle' and items you 'select'. You may toggle an item by moving the menu bar to the desired item and pressing enter one or more times. Each successive 'enter' will change the item's state. Some items have up to six choices. Press enter until the desired choice appears. The item will maintain this choice, or state. Selectable items are items that will cause an action, open an input field or pop up another window, when selected. You may also use your mouse if you have one connected. The left mouse button is the 'enter' key and the right button is the 'esc' key. You may close a menu window by hitting Esc at any time. If you press ESC while at the TOP menu, LTSetup will exit. Once you have completed the configuration stage of LTSetup, you may select files to process from the Process Files menu. Or you may exit LTSetup and run Labtest from the command line. Complete details on running Labtest, from LTSetup, online and from the command prompt, will be discussed later. For consistency purposes, and to make the author's life a little easier, LTSetup's online help system now loads the portion of this documentation pertaining to the current menu option. 5 Configuration Options Now we get to the heart of configuring Labtest! 5.1 Files/Paths 12 Labtest 3.4 User's Guide This menu contains the bulk of the filenames and paths that control where Labtest will store some items and where it can find special files. Some of these files can be copied to a RAM drive to enhance performance a great deal. These files are annotated with a * next to the file's description. 5.1.1 Log File Path This is the drive and path where Labtest should write the LABTEST.LOG and UPLOAD.LOG files. The actual name of these files depends on whether or not you are running a multi-line system. Enter only the drive and path. If you are running a multi-node system, the log file names will be somewhat different. Instead of using LOG as the file extension, the actual node number will be used instead. This will prevent information from various nodes on your system from being mixed up. For example, the log file on node three would look like this: C:\LABTEST\LABTEST.3 Provided you specified C:\LABTEST as your log file directory. The log file for all local processing will always be LABTEST.LOG. Remember, if you are running Labtest on a multinode system, you must specify /NODExx (where xx is the node number) on the command line for Labtest. The local node will always be 0, thus defaulting to a logfile name of LABTEST.LOG. 5.1.2 Swap Path Specify the complete drive and path where Labtest should store its temporary swap file when executing external programs. To increase efficiency of operation, you may wish to set this path to a RAM drive. 5.1.3 Bad File Path Specify the drive and path where Labtest should place files which fail the checks Labtest runs. If this path is defined in your BBS file area configuration, the database for that area will also be updated. 5.1.4 ANSI Screen File * Specify the path and file name of the .ANS screen Labtest should display to your ANSI callers when processing a file. This screen 13 Labtest 3.4 User's Guide will also be used for the local display regardless of the user's display capabilities. NOTE: If you enable the Remote Status Window option, this file must not display more than 17 lines on screen. The Remote Status Window is never available for ASCII callers or callers using a RIP terminal. 5.1.5 ASCII Screen File * Specify the path and file name of the .ASC screen file to display to callers not supporting RIP or ANSI graphics. 5.1.6 RIP Screen File * Specify the path and filename of the .RIP screen file to display to callers supporting RIP graphics. Labtest will display the .ANS screen on the local terminal while displaying RIP graphics to the remote caller. 5.1.7 Screen Control File * Specify the path and file name of the .CTL file which Labtest will use when displaying information to the screen. This control file contains information such as colors, coordinates and text to be displayed during the processing. This file is required. An example control file is included in the distribution archive and contains detailed information on how to modify the user display. 5.1.8 Kill File List * This file should contain file names (or wildcards) of files you wish to be removed from EACH archive and imbedded archives. For example, specifying RUSTY.* will remove all files that match this file mask. You must not specify a path, only the filename. Here are some examples of valid filenames: RUSTY.* BBSAD.TXT -CALL-US.NOW Filenames containing paths are considered invalid: C:\LABTEST\BBSAD.TXT 5.1.9 Add File List * 14 Labtest 3.4 User's Guide This file contains full paths and file names of files you want to be added to each archive processed. This is just the opposite of the Kill File List, in that you must specify full paths, and wildcards are not allowed. Please note that it is not considered ethical to add files to archives, as this may give the impression that the files were added to the archive by the author of the program and may unfairly reflect negatively on the program and the author. Please do not abuse this option. Labtest will never add files to embedded archives. 5.1.10 Message Import Text File * This field specifies the full path and filename of the Message Import Text file. This file contains the actual text of each of the sysop and user messages. Each message is separated by a special marker. This marker consists of the pound sign "#" followed by a keyword. There is no space between the # and the keyword. Each of these keywords must be on a line by themselves, with no other information on the same line. Please refer to the included IMPORT.TXT file for more information. 5.1.11 Hack File Name * Specify the path and file name of the HACK.COL or HACK.IDX file Labtest should search. This file should contain base file names of files you do not want on your system. Labtest is capable of reading and parsing the Hack Report .IDX and .COL files without modification. 5.1.12 Archive Comment File Name * This is the path and file name of a text file you want added as an archive comment to each file Labtest processes. If you do not want ANY archive comment added, leave this field blank. You may optionally add the contents of the FILE_ID.DIZ as an archive comment. See also 'Archive Comment Command Line.' 5.1.13 Inbound TIC Directory This is the directory where your inbound .TIC files are placed by your mailer software. In implementing .TIC processing in Labtest, our goal was to provide the ability to get the file information into the BBS and have the files processed by Labtest. If you specify /TIC on the command line or select Process .TIC files from LTSetup, Labtest will look for any inbound .TIC files in this directory. If any 15 Labtest 3.4 User's Guide are found, each .TIC file will be read and parsed for the file name, description, and destination file echo area. Labtest then reads your .TIC configuration file and gets the physical destination directory from there. This process is repeated for each .TIC file. If Labtest is interrupted at any time, the most that could happen is you may lose the .TIC file that was being processed at the moment of the interruption. For details on setting up Labtest to handle your .TIC files, please read the TIC.DOC included in your distribution archive. 5.1.14 Duplicate File Database * Enter the path and file name of the file to use as your duplicate file database. This file will be searched for possible duplicates for each archive that is unpacked. Many sysop's like the ability to check for duplicate internal files. This will prevent users from simply renaming an archive and uploading it to you just to steal upload credits. You may leave this field blank if you do not wish to use this duplicate checking feature. Please note that on large systems with numerous files, this feature may impede performance. Note: This file is not a text file. It contains the CRC values for the file names that Labtest has processed. This method was chosen to increase speed as well as reduce overall file size. Each file name will occupy four bytes instead of the full file name of up to 12 characters. This file can be stored on a RAM drive, however, it should be copied back to the hard disk after each user logs off to ensure the master copy is kept up to date. 5.1.15 Anti-BBS Ad Text File * Labtest now can check INSIDE files for text strings that are normally only found in those pesky BBS advertisements. Specify here the path and file name of a text file containing words or phrases to search for in files contained in archives. You can also set the maximum file size to check to enhance speed and operation. You can set Labtest to delete BBS advertisement files if you like. This is not really recommended because not all files which may fail this check are actually advertisements. Other than deleting the files and making a note in the logfile, Labtest does nothing more for advertisement files. The archive will not be failed due to the existence of an advertisement file. 5.1.16 TIC Configuration File * 16 Labtest 3.4 User's Guide Specify here the full path and filename of the TIC.CFG file. This file contains many options for controlling Labtest's TIC processing feature. Please refer to the sample TIC.CFG file provided in your distribution archive. 5.1.17 Editor Command Enter the path and file name of your preferred Default Text Editor. LTSetup will still pop up a list of editors found in your DOS path, but your preferred editor will always appear at the top of the list, so all you need to do is hit enter when the editor list appears if you wish to use the default. 5.1.18 Skip List * Specify the path and filename of the text file which contains names of files you do not want Labtest to process. This file contains only filenames, without paths, so Labtest will skip them regardless of where the file is actually located on disk. Some examples of files you would always want to skip: FILES.BBS DIR.LST COMMAND.COM Storing each of the files marked with an asterisk * on a RAM drive will substantially enhance Labtest's performance. Labtest continually reads information from these files during processing and storing them on a memory drive will save your hard disk some wear and tear. 5.2 BBS Setup This menu controls how Labtest interfaces with your Bulletin Board Software. If you are not running a BBS, or you are running a BBS that is not directly supported by Labtest, then some of the options on this menu will be of little use to you. Please refer to the file BBS.DOC for details on installing Labtest into your BBS system or using Labtest when you do not have a BBS. 5.2.1 BBS System Select from the list your BBS software type. If your BBS is not listed, you may still be able to get most of the functionality provided for the systems listed by selecting FILES.BBS as your system type. 5.2.2 File System Path 17 Labtest 3.4 User's Guide This field is used to tell Labtest where it can find your BBS file database. Usually, this will be left blank, unless your system uses a unique file database instead of the FILES.BBS system. For RemoteAccess, specify the base directory of your file database. Usually, this is C:\RA\FDB (the \IDX, \HDR, and \TXT directories are stored in the \FDB directory). For PCBoard, this is the location, not the filename, of the DIR.LST file. Refer to the list below to decide which file to use for your system: RemoteAccess Usually C:\RA\FDB Proboard Blank QuickBBS Blank PCBoard 15.x Path to DIR.LST FILES.BBS systems Blank (Maximus, Ezycom, etc.) 5.2.3 Set Security Level If you specify a number other than zero '0' in this field, Labtest will lower the user's security level to this number if a virus is detected in the uploaded file. Please note that this is an extremely effective tool to deny user's upload rights should they upload a virus to your system. It is each user's responsibility to ensure that the files they upload are clean. Several states have laws providing punishment for people who 'knowingly or unknowingly' transmit computer viruses. Using this option will ensure that they cannot continue uploading until you grant them access again. 5.2.4 Remote Status Window While processing a file, Labtest writes a great deal of information to the system logfile. This information may also be displayed to the sysop and the user display in a box at the bottom of the screen. If you enable Remote Status Window, be sure that your custom ANSI screen file does not have any pertinent information in the screen region below line 17. 5.2.5 Sysop Message Info In this menu you will specify information Labtest needs to access your Sysop Message Base. 5.2.5.1 Sysop Message Board This is the message board number where messages addressed to the Sysop will be placed. Labtest's message writing routines 18 Labtest 3.4 User's Guide support Squish, Jam, Hudson, GoldBase, *.MSG and PCBoard 15.x message base formats . 5.2.5.2 Message Base Path This is the path to the selected message base files. For Hudson, *.MSG, or Goldbase, specify only the drive and path to the message base files. For Squish, Jam, and PCBoard, specify the path as well as the name of the message base. 5.2.5.3 Message Base Type Select the message base type to use for this conference. Available choices are Jam, Squish, *.MSG, Hudson, Goldbase, and PCBoard 15.x message bases. The text for the Sysop messages is contained in the file LABTEST.LNG. This file contains all of the text used throughout Labtest and LTSetup. You may enter up to 256 characters for each of the Sysop messages. If you wish to force a carriage return a any point in the message text, place a reverse single quote (`) at the position where you would like a carriage return to appear. 5.2.6 User Message Info In this menu you will specify information Labtest needs to access your User Message Base. Refer to the Sysop Message Info above for more information. There are a few macros which will be expanded by Labtest when it writes a message to the user or sysop. These macros must be specified in upper case, with the @ symbol on both sides, excactly as shown. These are explained below: @SYSOP@ Sysop name (as defined in RACONFIG) @SYSTEM@ BBS System name @USERFIRST@ First name of the user @FULLNAME@ Full name of the user @UPLOADS@ Total number of uploads the user has posted @UPLOADK@ Uploads (in K) the user has posted @AGEDAYS@ Maximum age in days for files @AGEYEARS@ Maximum age in years for files @GIF@ Minimum acceptable GIF resolution @FILENAME@ The name of the uploaded file. @VIRUSINFO@ Information about the virus detected. @DUPES@ Total number of duplicate files found. @OLDFILES@ Total number of old files found. @TOTALFILES@ Total number of files in the archive. @DUPEPERCENT@ Percentage of duplicate files. 19 Labtest 3.4 User's Guide @OLDPERCENT@ Percentage of old files. Keep in mind the width of each of these macros when they are expanded. Labtest will not word wrap the text and it may look choppy if your text lines are too long. The message text for each Sysop Message is defined in the LABTEST.LNG file, therefore you could modify your LABTEST.LNG file to add any of the macros you would like to use. 5.2.7 Select User Messages This option will popup a small menu where you will select which messages you want Labtest to write to the user. 5.2.8 Select Sysop Messages This option will popup a small menu where you will select which messages you want Labtest to write to the Sysop. 5.3 System Options This menu contains numerous options which control the overall operation of Labtest. 5.3.1 Sysop Name Enter your name as it appears on your registration form. This field is case sensitive, therefore upper and lowercase letters are not treated the same, so be sure to double check your registration form. 5.3.2 BBS Name This is the name of your BBS system and must match what you have specified on your Labtest registration form. 5.3.4 Registration Key Enter your registration key as it was provided to you. 5.3.4 Max File Age You may specify the maximum age for each file (and files within archives) that you wish to store on your system. If this number is greater than 9, then Labtest assumes the age to be DAYS. If this number is between 1 and 9, Labtest will assume the age to be in YEARS. For example, specifying 2 in this field tells Labtest 20 Labtest 3.4 User's Guide to fail files over 2 years old. Specifying 180 will tell Labtest to fail files over 180 days old. You may enter a zero (0) in this field to disable age checking. 5.3.5 Sound Virus Alarm Specify Yes if you want Labtest to alert you (using the Page File), in the event a virus is detected in the user's upload. This will be ignored if you do not have a Page File defined in Files/Paths or you have your Scroll Lock key on (A RemoteAccess convention adopted by Labtest for consistency.) 5.3.6 Swapping method While executing external programs like PKZIP or SCAN, Labtest needs to free up the memory it uses by performing what is called a swap. Labtest copies its program image to disk or EMS memory and loads the external program. When the second program is finished, Labtest reloads and continues execution. You have three options for swapping Labtest out of memory, NONE, EMS and DISK. None is normally used only in testing. EMS will copy the image to extended memory, and DISK will copy the image to the swapping directory specified in your files/paths section. If you are using a RAMDISK, select DISK here and specify the RAMDISK path in your files/paths setup. 5.3.7 DOS Window Height Many sysop's have asked for a way to adjust the DOS window size. This option will set the number of screen lines that the DOS window should occupy. This does not change the location of the window, which will always END on line 23. If you specify 12 here, the DOS window will begin at line 11 (23-12) and end on line 23, taking up the screen region from the left edge to the right edge. The colors of the DOS window are not yet adjustable, but may be in a future release. 5.3.8 Minimum Disk Space Specify in kilobytes the minimum amount of hard disk space that should be available in order for Labtest to process files. If the space available is less than the amount specified here, Labtest will make a log entry and exit. Additionally, if the amount of available space is not more than two times the size of the file being processed, Labtest will skip the file, and make a log entry. 21 Labtest 3.4 User's Guide 5.4 GIF Options These options only apply to .GIF or .JPG files and control how Labtest will process these files. Note: Labtest cannot determine the graphics resolution of a JPG file. There is no set standard for resolution testing for JPG files and determining the resolution is beyond Labtest's current capabilities. 5.4.1 Check GIF Age Specify whether you would like Labtest to check the age of GIF files according to the Max. File Age setting (described above). 5.4.2 Minimum GIF Width Enter the minimum acceptable width in pixels for .GIF and .JPG files. 5.4.3 Minimum GIF Height Enter the minimum acceptable height in pixels for .GIF and .JPG files. 5.4.4 Minimum GIF Colors Enter the minimum acceptable number of colors for .GIF and .JPG files. 5.4.5 GIF Separator Character Labtest will write the GIF color resolution to the file description in the format width X height X colors. The separator character is the character you want to be put in between each of the resolution factors. For example, if you specify * as the separator, your GIF descriptions will look like this: (640*480*256) 5.4.6 Compress GIF Files Labtest can compress a GIF file using the compression program specified in Archive Definitions if you specify Yes here. Compressing GIF files may save you a large amount of disk space, at the cost of a (generally low) degree of resolution loss. Alternatively, you can choose to Uncompress JPG files as well. 5.4.7 Uncompress JPG Files 22 Labtest 3.4 User's Guide If Labtest detects a JPG file (essentially a compressed GIF), it may be able to uncompress the file, restoring it to GIF. Specify Yes here if you wish to do this. Restoring JPG files will not restore them to their original resolution. JPEG compression is not a loss-less method, and compressed files suffer somewhat in their resolution. 5.5 Archive File Options This menu contains all the necessary info for Labtest to process archived files. 5.5.1 Default Archive Type Specify the three letter extension of the default archive format. This is overridden by your FILES.RA default archive format. If you prefer all your files to be of the same type, you may leave the default archive field blank in all of your file areas, and specify it here instead. You must specify the default archive type if you are not using RemoteAccess. 5.5.2 Maximum Old File Percentage Specify the overall maximum percentage of old files the archive can contain before it will be considered a fail. This extends to imbedded archives and all files contained in all subdirectories, of all archives. . . . .You get the drift. For example, specifying 80 here would fail the archive after 80 percent of its files are found to be too old. 5.5.3 File Date Options Labtest will date the archive according to one of the following: Newest File: The date of the newest file is used as the archive date. Oldest File: The archive is stamped with the date of the oldest file. Keep Date: Labtest will keep the original date of the archive. System Date: Labtest will date the archive with the current system date. 5.5.4 Convert SFX Files 23 Labtest 3.4 User's Guide If the file being processed is determined to be a self extracting file, Labtest can either unpack/scan/convert the file or ignore it altogether. If you set this option to No, Labtest will archive the file in your default archive type. For example, if a user uploaded LABTST29.EXE which is an SFX file, and you had this set to No, Labtest will create an archive called LABTST29.ARJ (assuming ARJ is your default archive type), containing just one file, LABTST29.EXE. 5.5.5 Pack Unknown Files If Labtest is unable to determine the file type, it can compress it using the default archive format. This will save space on your computer if users upload large text files in an effort to steal upload credits. Specify No to leave unknown files in their original state. 5.5.6 Keep Security Labtest can detect and honor the security envelopes of ARJ and ZIP files. If you specify Yes here, Labtest will unpack and scan the files, but will not attempt to repack or add a comment to these files. This applies to imbedded archives as well. 5.5.7 Imbedded Archives Here you may specify how Labtest should handle imbedded archives. An Imbedded Archive is defined as an archived file contained within an archived file. The imbedded archive options are described below: Ignore: Do nothing to imbedded archives. Scan: Scan imbedded archives. Do not rearchive. Rearc: Rearchive imbedded archives. Do not scan. Scan/Rearc: Scan and rearchive imbedded archives. When Labtest processes an archive containing a directory tree, each subdirectory will also be processed, checking for more archives and also performing all other tests performed on the basic archive. There is no 'built-in' limit to this capability. 5.5.8 Process Descriptions Labtest can modify the description found in the FILE_ID.DIZ (or DESC.SDI) file. The purpose of this is to remove high ASCII 24 Labtest 3.4 User's Guide characters such as those used for boxes and other special characters. 5.5.9 Maximum File Size You may define the largest file size in kilobytes that Labtest should attempt to handle. Files exceeding this size are ignored. This applies only to archive files and not .GIF/.JPG files. Set this option to 0 to disable Maximum File Size checking. 5.5.10 Maximum Duplicate Files Specify the maximum number of duplicate files allowed in an archive file. If the uploaded file contains more duplicate files than this number, it will be failed. Keep in mind that files received through a file network often 'replace' other files and may fail this test. Set this option to 0 to disable duplicate file checking. 5.5.11 Maximum Duplicate File Percentage Specify the maximum percentage of duplicate files allowed before Labtest will fail the archive as a duplicate. This can be used instead of or in conjunction with the Maximum Duplicate Files option. 5.5.12 Maximum Advertisement File Size Specify the maximum file size to check for BBS ads. BBS ads are usually small, so setting this to about 500 is normally sufficient. Files larger than this size will be skipped. Each file in each archive is checked against your Anti-Ad file text. Set to 0 to disable Advertisement File checking. 5.5.13 Delete BBS Advertisements Files which failed the advertisement check may optionally be deleted. Select Yes if you wish to delete these files. Use this option with caution. Not all files which will fail your anti- advertisement test may be BBS ads! Labtest will not fail the archive solely based on the existence of an advertisement file. 5.5.14 Adjust User Credit Specify if you would like Labtest to adjust the user's upload credit for the new file size after conversion. 5.5.15 Failed Scan Action 25 Labtest 3.4 User's Guide Here you will specify the action Labtest should take on files that fail the overall processing. Each option is described below: None: Labtest will not do anything in the event of virus detection. Unlisted: Labtest will mark the file as unlisted in your file database. Not Available: Labtest will mark the file as not available. Mark Deleted: Labtest will mark the file as deleted. Move: Labtest will move the file to the path specified in Files/Paths - Bad file path. Move/Unlisted: Labtest will move and mark the file unlisted. Move/Notavail: Labtest will move and mark the file not available. Most of the above options apply only to RemoteAccess 2.xx which uses a database system instead of FILES.BBS. If you are using ProBoard or another FILES.BBS system, the only options that are available are None and Move. Move/NotAvail and Move/Unlisted are not available. 5.6 Archiver Setup This menu contains the information needed by Labtest to run your external archive utilities. Labtest is preconfigured for the more popular archive utilities and associated command lines. However, you may change these as you wish. To skip to the next archiver, press the Page Down key (or use your mouse and click on the PgDn button. To skip to the previous archiver, press the Page Up key, or click on the PgUp button. Press ESCape when you are done. 5.6.1 Archive Extension This is the three letter file extension used by the archive utility. Labtest is designed to detect almost all of the most popular archive formats based on the unique archive signature used by each program. This extension is used to find a match in an internal table of probable extensions based on the archive type. This extension is only used when rebuilding a file name during the conversion phase; it is not used during the unpacking or archive detection phase. 26 Labtest 3.4 User's Guide If you are using an archive utility that Labtest does not recognize, please send the complete distribution archive for the program, and we will install the necessary information into Labtest to automatically detect the archive type. 5.6.2 Unpack Command Line This is the command line that will be executed by Labtest to unpack, or decompress, files of this type. You should specify the path/program name, command line options and the @ character which will be replaced by Labtest with the full file name, including drive and path. The @ character should be in the correct position in the command line, just as you would execute it from DOS. If you specify only the program name without a path, Labtest will attempt to find the program in your DOS path and fill in the entire path/file name for you. Some examples: ARJ: C:\SHEZ\ARJ.EXE x -y @ PKUNZIP: C:\SHEZ\PKUNZIP.EXE @ -d ZOO: C:\SHEZ\ZOO.EXE e @ LHA: C:\SHEZ\LHA.EXE e @ PKUNPAK: C:\SHEZ\PKUNPAK.EXE @ UC II: C:\SHEZ\UC.EXE ES @ 5.6.3 Pack Command Line This is the command line that will be executed by Labtest to pack, or compress, files of this type. You should specify the program name, command line options, and the @ character which will be replaced by Labtest with the file name. The @ character should be in the correct position in the command line, just as you would execute it from DOS. Some example command lines follow: ARJ: C:\SHEZ\ARJ.EXE a @ -r -jm PKZIP: C:\SHEZ\PKZIP.EXE -a @ -rp -ex ZOO: C:\SHEZ\ZOO.EXE a @ LHA: C:\SHEZ\LHA.EXE a @ PKPAK: C:\SHEZ\PKPAK.EXE -a @ UC II: C:\SHEZ\UC.EXE AS @ 5.6.4 Comment Command Line This is the command line that will be executed by Labtest to add an archive comment to archives of this type. You should specify the program name, command line options, and the @ character which will be replaced by Labtest with the file name. The @ character 27 Labtest 3.4 User's Guide should be in the correct position in the command line, just as you would execute it from DOS. You may place the contents of the FILE_ID.DIZ (if found) as the archive comment or you may place the DIZ contents AND the comment file. Labtest uses two macros, $COMMENT$ and $DIZ$ for these purposes. You may place the FILE_ID.DIZ before the comment file or after it by switching the position of these macros. Here are some examples using ARJ: ARJ.EXE c @ -z$DIZ$ $COMMENT$ ARJ.EXE c @ -z$DIZ$ ARJ.EXE c @ -z$$COMMENT$ ARJ.EXE c @ -z$COMMENT$ $DIZ$ NOTE: We have discovered that in order to use PKZIP to add an archive comment, it must be called using COMMAND.COM in the beginning of the command line. The reason for the change is Labtest's internal method of calling programs does not work for programs that use the dos REDIRECTION '<' symbol. To add a comment to a PKZIP archive, the following command line is required: C:\COMMAND.COM /C C:\SHEZ\PKZIP.EXE @ -z<$COMMENT$ $DIZ$ Of course, the path for PKZIP may be different for your system, and the COMMENT DIZ specifier is up to you. This is just an example but the important piece of information is the C:\COMMAND.COM /C must appear before PKZIP.EXE in the command line. PKZIP is the ONLY program that requires this change. (This only applies for the Comment Command Line. Pack/Unpack command lines do not require this.) 5.6.5 Video Full Screen: Labtest will save the screen, clear it, run the external program, and restore the screen upon return. DOS Window: Labtest will run the program in an adjustable window. All of the program's output will be restricted to this window. Some programs perform direct screen writes and are not compatible with the DOS window. Labtest must find the program DOSWIN.EXE in the same directory as LABTEST.EXE in order for the DOS window to be used. The size of the DOS window is adjustable. See the Control Menu, DOS Window Size. Disable Video: Labtest will disable all video while running the external program. This is the most stable view. It may, however, 28 Labtest 3.4 User's Guide only work on VGA or better systems. The only way to determine out what's best for you and your system is to try until you find the one you prefer most. NOTE: While being the most stable view, Disable Video temporarily disables the entire video system of your computer, regardless of the operating system you are using. This has resulted in the impression that the system was locked up under a multi-tasking system (OS/2 or DESQview), when indeed it was not, but the video had been disabled by Labtest. The video is enabled upon return from the external program. The recommended video method is DOS Window, as it is compatible with almost all archiving and virus utilities and provides a window where you can watch what is happening. 5.7 Virus Scanner Setup Labtest can be configured to run up to 20 virus scanners, in succession, on each uploaded file. Each virus scanner will be executed in the order they have been defined. The errorlevel returned will be written to the log file. To skip to the next virus scanner, press the Page Down key (or use your mouse and click on the PgDn button. To skip to the previous virus scanner, press Page Up key, or click on the PgUp button. Press ESCape when you are done. 5.7.1 Scan Command Line Specify the command line to run your desired virus scanner. The full path is required for all external programs. If you are using a virus scanner which has the ability to log the information regarding the files it has scanned, Labtest may read this information and write it to the log file. To enable this option for McAfee's SCAN, specify /REPORT $REPORT$ option on your command line. The /REPORT tells Scan to create a report file and the $REPORT$ is a macro used by Labtest to specify the file name to the virus scanner. Labtest creates this file name at run time to prevent interference from other nodes. If you use /REPORT, you must use $REPORT$ or Labtest will not read the results from the report file that Scan creates. F-PROT uses a similar format for specifying the report file. Use /REPORT=$REPORT$ for F-PROT. 5.7.2 Errorlevels Specify one or more errorlevels that may be returned by this scanner in the event a virus is detected. Some virus scanners may return a different errorlevel for different types of viruses. 29 Labtest 3.4 User's Guide By specifying each errorlevel separated by a space, you can test for any virus level the scanner may return. Errorlevels other than those specified will simply be logged and will be considered a pass. Check your virus scanner's documentation for the appropriate errorlevels to use. Examples of errorlevels that you would not specify here are those that indicate low memory, bad command line, or no files found to scan. These should be considered as warnings and should not cause Labtest to fail the file. For more information on program errorlevels, please review the information appearing at the end of this documentation, External Program Errorlevels. 5.7.3 Video See section 5.6.5 Video options 5.7.4 Enable You may enable or disable each of your virus scanners by setting this option to Yes or No. Setting it to No means that this virus scanner will not be used. Using this option, you may configure many virus scanners, but only actually use selected ones each time Labtest runs. 5.7.5 Scan Log Text Many virus scanners have the capability to create a logfile containing information about the scan session. Labtest can read this file and write the information pertaining to an infection to the log file and the sysop/user messages. Using the Log Text feature, you will specify one or more words or phrases that are contained in the virus scanner's report file which indicate a virus has been detected. Separate each word or phrase with a space. If you wish to search for a multiple word phrase, i.e. "Virus Found", use an underscore '_' character as a substitute for the space between the words. Labtest will translate the underscore to a space before performing the search. For example, F-PROT writes something like: VIRUS.EXE Infection: Jerusalem.1808.Standard to the REPORT file. The keyword here would be 'Infection'. Case is relevant, so be sure to specify the word exactly as it appears in the report file. McAffee's VirusScan reports something like: 30 Labtest 3.4 User's Guide Found the Jerusalem [Jeru] Virus Labtest will write the entire line which contains the selected words or phrases. So you would specify 'Found' as the log text for SCAN.EXE. You can experiment with this and see what suites your needs best. Labtest will write a file called SCANRPT.nnn (nnn is the node number, 0 = Local Node) in the Labtest directory during each run. Check this file for the appropriate words or phrases. 5.8 Description Settings This menu contains options for handling file descriptions imported from a FILE_ID.DIZ or DESC.SDI file. 5.8.1 Word Wrap When Labtest imports a description from a FILE_ID.DIZ or DESC.SDI file, it can perform a word wrap using the Max. characters per line and max. lines per description values. This will help make the descriptions line up better for display to the user and for file listings, such as an all files list. 5.8.2 Add Uploader's Name Setting this option to Yes will cause Labtest to add the name of the user who uploaded the file to the file's description. 5.8.3 Remove High Ascii You may set this option to Yes to have Labtest remove all characters from the desription above ASCII 127. These characters are usually IBM box drawing characters or foreign language characters. Box characters frequently mess up file listing displays. Removing them will save you disk space and make a more uniform appearance for your users. 5.8.4 Strip ANSI codes A new trend seems to be developing in adding ANSI color codes to FILE_ID.DIZ files. These are very annoying when viewing file listings either online or from an all files list. Set this option to Yes to remove ANSI escape codes from descriptions before importing into the file database. 5.8.5 Strip @ codes 31 Labtest 3.4 User's Guide Perhaps equally annoying as ANSI color codes are @ codes used by PCBoard. The only @ code currently supported is the @X color code. Labtest does not currently support removal of @ macros, or other codes preceded by an @ symbol. 5.8.6 Maximum characters per line This value is used to determine the maximum line width for descriptions when performing a word wrap. 5.8.7 Maximum lines per description This value sets the maximum number of lines Labtest should import from a FILE_ID.DIZ. The remaining lines are truncated. This is performed after the word wrap. 5.8.8 Description Continuation Offset Some systems (PCBoard for example) indent the 2nd and following file description lines to line up with the first line. For PCBoard systems, the correct value for this field is 34. For FILES.BBS systems, this value depends on wether you have download counters or not. Usually, 34 is a good value for most systems. Proboard users should specify 0 here. 5.8.9 Description Continuation Character This is a single character field. Enter the character you wish to precede the 2nd and following file description lines. PCBoard users should specify the vertical bar | in this field. Proboard users should specify the plus + symbol in this field. All others should leave this field blank. 5.8.10 Description Comments This option will popup a menu which you will use to select which comments you want Labtest to write to the file description concerning the status of the file. These comments are appended to the file description. 6 Using LTSetup to Process Your Files You may utilize LTSetup to select and process your files or file areas from the Select Files or Select File Areas menu. 6.1 Process TIC Files 32 Labtest 3.4 User's Guide This option will tell LTSetup to check your inbound directory for new .TIC files. The files will be processed according to current settings. 6.2 Select Files Selecting this option will open a window of file names from the current directory. You may tag as many of the file names as you like. Press ENTER when you are done selecting files. 6.3 CD-ROM Support If you are selecting CD-ROM areas to process, be sure that you have selected any non CD-ROM areas you want processed before you select the first CD-ROM area. Labtest will default to No Rearc, No Comment, and No Move when processing CD ROM areas. Additionally, the Add Uploader Name is disabled when processing CD ROM areas. These defaults remain in effect until Labtest exits. To allow you to alter Labtest's default behavior for the current session, you may select one of the options below and toggle it to Yes or No. This will only affect Labtest's behavior while run from within LTSetup. These options are the equivelant to the command line options discussed later in this manual. 6.4 Convert This option defaults to Yes. If you toggle this to No, it is the same as specifying /NC (No Convert) on the command line and will inform Labtest that it is not to convert files to the default archive format during this session. 6.5 Scan This option defaults to Yes. If you toggle this to No, it is the same as specifying /NS (No Scan) on the command line and will inform Labtest that it is not to run any of the defined virus scanners during this session. 6.6 Override This option defaults to No. This informs Labtest that it should not process files which have already been processed. Labtest keeps track of which files have already been processed by any other version of Labtest. If the file is modified in any way, Labtest will consider it to be a new file, subject to processing. If you run Labtest by selecting file areas, it is highly recommended that you leave this set to No. If it is toggled to Yes, Labtest will 33 Labtest 3.4 User's Guide process ALL files in the selected areas which could result in a rather lengthy task if you have many files. 6.7 Begin If you have selected files or file areas to be processed, selecting this option will fire up Labtest to go to work. 7 Printing/Exporting Your Configuration File You may wish to print a copy of your configuration file once you have installed Labtest. Select the Quit Menu. The Export Config File option will open a window asking you how you want the information exported. If you wish to print the configuration file to the printer and write it to a text file, press B for Both at the prompt. If you wish to only print the configuration, press P for Printer. To simply export the configuration information to a text file, press F for File. LTSetup will prompt you for the file name to save the information to. If this file exists, it will be overwritten. NOTE: Never specify the same file name as your LABTEST.CFG file when exporting the information. Labtest's configuration file is not a text file, and overwriting it will cause you to re-enter all of the information. 8 Using the Auto Test Feature LTSetup now has the capability to check your configuration options and report possible conflicts or missing directories/files. Additionally, LTSetup can automatically configure each of your command lines for all external utilities. 9 Customizing Labtest's Displays Labtest can display information in one of three display modes, RIP, ANSI, and ASCII. Labtest detects the remote user's terminal capabilities by checking the BBS door information file (usually EXITINFO.BBS or DOOR.SYS). Note that RIP display is available only on the remote terminal. Labtest will attempt to display ANSI to the sysop's terminal if the user has a RIP terminal. You may wish to modify the display screens to suite your tastes. In addition to drawing your screens, you need to tell Labtest where to put the information on the screen to reflect each stage of the process. This is accomplished by using the Screen Control File. This file is named LABTEST.CTL in the distribution archive and 34 Labtest 3.4 User's Guide contains all the information you need to customize your display. Refer to that file for more information. 10 Running Labtest There are several command line options you will need to be familiar with in order to run Labtest from the command line. /L Local Mode. Informs Labtest that it is not to read the door information file (EXITINFO.BBS/DORINFO1.DEF) and that no communication with the modem is to take place. /G Configuration file name. Specifies an alternate configuration file to load. Instead of using this command line, you may wish to use the alternate naming method for your configuration files. You may name your configuration file by using the current node number. For example, creating one configuration file for each node (not normally required), you would place all of these files in your Labtest directory. The default is always LABTEST.CFG. It will be read last. If Labtest finds a file named LABTEST.Cxx, where the xx is the node number, that file will be loaded. If this file does not exist, LABTEST.CFG will be loaded instead. /O Override Mode. Informs Labtest that it is not to check for previously processed files. Files already processed by Labtest will be re-checked. This is recommended when running under the BBS. If you are running in Local Mode, you may want to leave the /O switch off, unless you are sure you want to re-process files. /E EXITINFO Path. Informs Labtest of the location for your EXITINFO.BBS file. Normally not needed if the file is in the current directory. /NODE Node Number. Labtest normally reads the node information from the BBS drop file. If it cannot correctly determine what node you are operating on, you may force Labtest to use a specific node number by specifying the /Nnnn command line option. nnn indicates the node number. Do not precede the node number with any spaces or zeros. Usually, the BBS will have some provision for specifying the node number on the command line. RemoteAccess uses *N to indicate the node number, so specifying /N*N on the command line will pass the node number to Labtest. /NS No Scan. Prevents Labtest from scanning for viruses. Useful if you want a quick import of the file information/description. 35 Labtest 3.4 User's Guide /NR No Conversion. Prevents Labtest from converting files to the default archive format. Useful if you want a quick import of the file information/description. /NC No Comments. Prevents Labtest from adding the archive comment. /ND No Delete. Prevents Labtest from removing the .TIC files and their accompanying after it has processed them. Labtest will mark the .TIC as having been processed, so if you run Labtest again with the /ND command, it will not reprocess the .TIC file. However, if you do not specify /ND on the command line, Labtest will process and remove all .TIC files found in your inbound directory. /TO Tic Override. This is very similar to the /O command, forcing Labtest to process all .TIC files. This is particularly useful if you want to reprocess your .TIC files, but do not want them removed by using the /ND command. This command is only relevant when used with /ND. /NTR No Tic Replace. This will prevent Labtest from replacing any file named in the .TIC 'Replaces' field. This is a global command and its scope is the duration of the current session. Therefore, no replacement will be done for any .TIC files. If you only have certain areas you wish to keep older versions of the file, you may specify that area as a No Replace Area in your TIC configuration file. /- No uploader name. Disables the writing of the Uploader's name to the file description. Useful when you are bulk processing files offline. Here are some examples of running Labtest from DOS: LABTEST C:\UPLOADS\LABTST31.ARJ /O /L Processes the file C:\UPLOADS\LABTST31.ARJ with Override on. You may specify more than one file name on the command line. LABTEST 89 /L Processes your file area number 89. Only new files will be processed since we did not specify /O. You may specify more than one file area on the command line. LABTEST C:\UPLOADS\*.* /L 36 Labtest 3.4 User's Guide Processes the C:\UPLOADS directory. Only new files (files that have not been tested before) will be processed. You may specify more than one wildcard path on the command line. You must specify a wildcard if you specify a path without file names. Labtest wouldn't know if C:\UPLOADS was a file or directory. LABTEST /TIC /O Labtest will process your incoming .TIC files in your inbound directory as specified in LTSetup. Informs Labtest it is to re- check previously processed files (/O). You need not specify the /L local switch when using /TIC. Please note: If your inbound .TIC directory is, for example, C:\RA\FD\FILE, and you start Labtest with: LABTEST C:\RA\FD\FILE\*.* /L /O This is not the same as LABTEST /TIC /O. Labtest will only start in .TIC mode if you specify the /TIC on the command line. Never run Labtest on your inbound .TIC directory without using the /TIC switch. You may, however, specify other file areas or file names in addition to /TIC: LABTEST 89 C:\UPLOADS\LABTST31.ARJ /TIC /L /O This would cause Labtest to process file area 89, LABTST31.ARJ, and your incoming .TIC files all in one session! For information on running Labtest from your BBS, please read the SYSOP.DOC file. 11 External Program Errorlevels Labtest will always record the errorlevel reported by an external program upon return from a shell. These errorlevels were captured from various documentation files from the respective program archives. PkZip 2.04g 1 :Bad file name of file specification 2-3 :Error in ZIP file 4-11 :Insufficient memory 12 :No files were found 13 :File not found. The specified ZIP file or list file was not found. 14 :Disk full 37 Labtest 3.4 User's Guide 15 :Zip file is read-only and can not be modified. 16 :Bad or illegal parameters specified. 17 :Too many files. PkUnzip 2.04g 1 :Warning error (such as failed CRC check) 2-3 :Error in ZIP file 4-8 :Insufficient memory 9 :File not found. No zip files found. 10 :Bad or illegal parameters specified. 11 :No files found to extract/view etc. 50 :Disk full 51 :Unexpected end of file in ZIP file. ARJ 2.41a 1 :Warning Specified file not found 2 :Fatal error 3 :CRC error 4 :ARJ-SECURITY error 5 :Disk full or write error 6 :Can't open archive or file 7 :Simple user error (bad parameters) 8 :Not enough memory LHARC 1.13c 1 :CRC error 2 :Fatal error. 3 :Failed to write temporary files in the archive. PKPAK 3.61 PKUNPAK 3.61 1 :Bad CRC warning 2 :Out of memory 3 :No archives found to extract 4 :Can't open archive file 5 :Read error on archive 6 :Internal table overflow 7 :Disk Full PAK 2.51 1 :CRC error 2 :Out of memory 7 :Disk Full 38 Labtest 3.4 User's Guide McAffee's VIRUSCAN Version 9.20V109 EXIT CODES 0 :No viruses found 1 :One or more viruses found 2 :Abnormal termination (program error) 3 :One or more uncertified files found 4 :Ctrl-C or Ctrl-Break aborted scan 12 Registration, warranty and licensing Upon registering Labtest 3.4, you will be provided a personal registration key. You will enter this registration key into LTSetup, which will then be recorded in LABTEST.CFG. Upon verification, Labtest will then run in registered mode, removing all 'nag screens'. Current registration prices are subject to change at any time without notice. At this time, we are not requiring upgrade fees. However, free upgrades are not guaranteed and this policy is subject to change according to customer demands and needs. This is a change from the previously published 'no upgrade fee' policy. In order to receive a registration key for version 3.4, you MUST use the enclosed registration form. Using older forms will result in processing delays. This program reflects the combined efforts of many people, none of which are being paid a salary for their work. This is the reason the price is being kept low enough for most sysops to easily afford. Although Labtest has no "Unregistered" features, you are nonetheless required to register if you continue usage beyond the 30 day trial period you are granted. By not registering, you are not only breaking a code of honor that the shareware community enjoys, you are in fact attributing to slower development and enhancements. When you register Labtest, you become part of a large team. This team communicates among eachother and with the author, providing a feedback network which stimulates not only the further development of Labtest, but fosters new ideas for other programs (Upload Partner and File Sorter to name just two). There are no guarantees in life. And Labtest is no exception. Although version 3.4 has undergone the most extensive testing of all versions since its inception, it is not guaranteed that Labtest will perform a function suitable to your needs, or that Labtest will even run on your system. The author is not responsible for any damage or loss of system resources due to the use or misuse of this product. Additionally, the author is not liable or responsible to any other party for damages or claims made by the third party for any residual damages or losses, whether real or 39 Labtest 3.4 User's Guide imagined. Basically, if you are an author, and you distribute Shareware in archived files, the author of Labtest is not responsible for a sysop's use of Labtest which may alter or add files to your distribution archives. 13 Customer Support Policy We may be contacted via Fido network Net-Mail, calling one of the support Bulletin Board Systems listed below, or by posting a message in on of the following Fido Network Conferences: RA_UTIL RemoteAccess Utilities Conference PROBOARD ProBoard Support Conference QUICKBBS QuickBBS Support Conference QUICKPRO QuickBBS Sysop Conference You may wish to use this method as the most economical means of obtaining answers to your questions, as there are many experienced Labtest users who frequent these conferences. North American Support Sites System Operator Fidonet addr/Phone # Scott Livingston 1:142/212 Phone Henge BBS BBS: (203) 673-6247 New Britain, CT Eddy Salvador 1:107/957 Integrated Circuits BBS BBS: (908) 354-4395 Elizabeth, NJ Glen Appleton 1:260/371 Psycho Ward BBS BBS: (315) 478-2042 Syracuse, NY Gary L. Murphy 1:130/85@ The Recovery Corner II BBS: (817) 447-3580 Burleson, TX Hector Cintron 1:142/1778 U.S.S. Nautilus BBS: (203) 827-0280 New Britain, CT William Brooks 1:264/415 Gameworld BBS BBS: (804) 261-0687 Glen Allen, VA Gary Petersen 1:280/389 40 Labtest 3.4 User's Guide Midwest Xpress BBS: (913) 894-8835 Lenexa, KS Marlin England 1:309/45 All Around the World BBS BBS: (602) 458-6371 Fort Huachuca, AZ Mark McNew 1:19/14 Sirius BBS: (501) 424-2510 Mountain Home, AR Scott Drake 1:189/922 The T.E.R.N. BBS BBS: (201)399-4772 Irvington, NJ 14 Registration Form Users may register Labtest by printing and filling out the registration form appearing at the end of this document or by entering LTSETUP and answering Yes to the prompt "Fill out registration now? Y/n" All registrations must be in US funds, either by check or money order drawn on a US bank. Make all checks or money orders payable to Mark Williamson. Expect 5 to 10 days to process your registration. You will receive a key either by Fidonet direct netmail, or by a personal letter via the U.S. Post Office. 41 Labtest 3.4 User's Guide Labtest Registration Form Date: _________ Yes! I want to register my copy of Labtest 3.4! Enclosed is a check or money order for the US $15.00 registration fee. YOU MUST USE THIS FORM TO ORDER VERSION 3.4. Fill out this form and mail to: Mark Williamson PO Box 131 Imperial Beach, CA 91932-0131 Please process my order according to the following: Your Name: ____________________________________________ BBS Name: ____________________________________________ BBS Software: ____________________________________________ Voice Phone: _____________________ BBS Phone: ______________________ Fidonet Address: __________________________________________ Mailing Address: ___________________________________________ ___________________________________________ ___________________________________________ Type Of Computer: __________________________________________ Operating System: __________________________________________ Comment/Suggestions : ______________________________________ ________________________________________________________ You should consider your copy of Labtest outdated if the LABTEST.EXE file is more than six months old. Due to constant changes, outdated versions cannot be supported. You are encouraged to keep your copy current by downloading the most recent version from one of the support sites. 42 Labtest 3.4 User's Guide 15 Contacting the author Mark Williamson lives in Imperial Beach, California. The most effective way to contact me is by calling one of the support BBS's listed in the beginning of this documentation or you may call the author's BBS at 619-575-4245. Leave a message with your comments/problems and your phone number. I will return your call as soon as possible. The Fidonet Node number for netmail and file requests is 1:202/750. File requests are available 23 hours a day. Zone Mail Hour is 1:00am to 2:00am PST. You may write to him via US mail by using the address in the REGISTER.DOC file. The latest version of Labtest can always be found on the author's system or any of the support sites listed in the beginning of this documenation. The magic name for file requests is LABTEST. 43