Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1993-09-13 | 36.6 KB | 692 lines

┌─┐ ┌──────┌──────┌─────┌─────┌─────┌─────┐ ┌─────┐ ┌─┐ ┌─┐ │ │ │ ┌──┐ └┐ ┌─┐ ├─┐ ┌─│ ┌───│ ┌───└─┐ ┌─┘ └───┐ │ │ │ │ │ │ │ │ └──┘ │ └─┘ │ │ │ │ └─┐ │ └───┐ │ │ ┌───┘ │ │ └──┘ │ │ │ │ ┌──┐ │ ┌─┐ │ │ │ │ ┌─┘ └───┐ │ │ │ │ ┌───┘ └────┐ │ │ └──│ │ │ ┌┘ └─┘ │ │ │ │ └───┌───┘ │ │ │ │ └───┬──┐ │ │ └────└─┘ └─└──────┘ └─┘ └─────└─────┘ └─┘ └─────└──┘ └─┘ Copyright (c) 1993 by Mark Williamson I would like to begin by thanking the following people for their contributions to the development of Labtest. Without their help, this program wouldn't be possible! Brian Pirie for writing an awesome door writing library Steve Joselson for his patience while beta testing (and for seeing it through!) Mike Ehlert for his insight with RemoteAccess and his patience for testing the program without actually being asked to do so. Bob Henderson for giving me a really easy dos shell routine (Spawn.c) Bob Lopinski for some great ideas! Bill Hull (author of CZip) for some tech-help! ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ LICENSING INFORMATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ This program is not Freeware. This is SHAREWARE which means it is user-supported software. If you use this program for more than 30 days, you are required to register or remove it from your system. The concept works only with your support. If you find that you can use this program, then a registration fee of $10.00 U.S. funds will help defray the development cost and encourage the authorship of other programs that might be useful to you. A Registration Form for this purpose is included with the distribution archive and is called REGISTER.DOC. Labtest is Copyrighted (c) 1993 by Mark Williamson and all rights are reserved. You may copy this program and documentation for backup purposes. You also may copy and share UNMODIFIED copies of the program package, providing that the copyright notice is reproduced and included on all copies. You may not sell the product for a fee and/or distribute the product along with other products without expressed written permission from Software Solutions, nor may you modify or remove the Copyright Notice from the program or the documentation. Those who register this program within one year of its release by the author, will receive a registration key. The key will be delivered either by personal upload, netmail or postal service. Allow up to 6 weeks for delivery. This program is not guaranteed to do anything except take up hard disk space. This program was written with the intent to support as many BBS systems as possible. Comments, suggestions and bug reports are welcome. If you have any, you should contact Mark Williamson at Fidonet 1:214/54. If you're reporting a bug, please give as much detail as possible about the problem you are experiencing so that it can be duplicated and fixed. ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ With the popularity of computer Bulletin Board Systems (BBS) comes the risk of intrusion by computer viruses which lay dormant and normally undected within a compressed archive file. These archive files are usually created using some sort of compression program, like PKZIP or ARJ. With the advent of file compression programs comes the increased likelihood that a computer virus may be lurking within the files of the archive, undectable by any virus scanning program unless actually uncompressed. Labtest was designed as a RemoteAccess 2.00 utility to aid in the fight against viral intrusion. Labtest will uncompress the archived file, run a Sysop definable virus scanner, and report the results to the user online and the Sysop. However, Labtest will do much more than this simple little chore. Labtest will also check .GIF files for minimum desirable resolution factors; update RemoteAccess 2.0 file database system with the correct filename, size and description (as read from a FILE_ID.DIZ/DESC.SDI file if one exists), remove unwanted 'junk' files from the archive file, add any Sysop defined 'junk' files to the archive, and add the Sysop's own archive comment text (.ZIP/ARJ files). The author feels that the Sysop should have complete control over the files that are placed on his system, therefore Labtest now has the ability to reject files based on age, in years. For example, if a file is more than 3 years old, Labtest will fail the file. Hint: If a user starts a file description with a forward slash '/', this tells RemoteAccess that the file is for the Sysop only. Labtest will honor this even if a FILE_ID.DIZ was imported. ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ Installation of Labtest is relatively simple. You may create a directory especially for Labtest or you may wish to place the program and support files in your RemoteAccess system directory. The location of Labtest is unimportant. Since Labtest may also be used as a maintenance utility, you may wish to place Labtest and it's support files in your system Path so you may execute the program from any directory on your system. To install Labtest, unpack the distribution archive into your desired directory. At a minimum, you should have the files LABTEST.EXE and LABTEST.CFG in your DOS path. You may use the LABTEST environment variable to tell Labtest where to find the configuration file. Insert the following command in your AUTOEXEC.BAT file to set the LABTEST environment variable: SET LABTEST=C:\LABTEST (specify your own directory). The Labtest environment variable is NOT optional! If you don't set this variable, Labtest will NOT RUN. Using your favorit text editor, load the file LABTEST.CFG and set up your system settings. The configuration file is well documented, so specific parameters will not be discussed in detail here. However, there are some settings which are read from the RemoteAccess CONFIG.RA file. They are discussed below: CONFIG.RA Path: Labtest will get this path from your RA environment variable. You must ensure that you have SET RA=C:\RA (or whatever) in your AUTOEXEC.BAT file. Message Base Directory: Obtained from RACONFIG.PATHS.MSG_BASE_DIRECTORY, this path name is where your Hudson message base files are placed. Labtest will use the information contained in LABTEST.CFG to determine where to post messages to the user and the sysop concerning the uploaded file. Labtest will check to see if it is a JAM message base and post the message in the JAM message base vice the Hudson message base. File Base Directory: Obtained from RACONFIG.PATHS.FILE_BASE_DIRECTORY, this path is the base directory of your file databases. Usually this is something like C:\RA\FDB System Name: Obtained from RACONFIG.SITE_INFO, this is the name of your BBS system. Sysop Name: Obtained from RACONFIG.SITE_INFO, this is the name of the System Operator. Compression utilities: Labtest will utilize the information obtained from RACONFIG.FILES.ARCHIVERS for the compress/uncompress utilities. See below for details on setting up archivers in RACONFIG. You must ensure that each of your file areas are configured properly for scanning. Each file area must have the UL Scan set to YES, and an archive type. If you want all of your files in the same format, then leave all the Archive Type fields blank, and Labtest will use the format indicated in LABTEST.CFG. In RACONFIG, under Files.Upload Scanner, enter the following: C:\RA\LABTEST.EXE @ /O *M ^^ Labtest directory. For clarity, here is some screen captures from RACONFIG on the author's system to aid you in setting up RA and Labtest: To setup the archivers, ensure that each Pack/Unpack line has a @ in the line to represent the filename. The full path names have been omitted here so you could see the entired command line. On your system, you must specify the entire path to each archive utility. File System Options Modem ═╒════════ File options ╕═════════╒══════════════╕══════════════ ▒│ │▒▒▒▒▒▒▒▒▒│ Messages │▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Upload credit 120 │▒▒▒▒▒▒▒▒▒│ Files │▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Payback credit 60 │▒▒▒▒▒▒▒▒▒│ Restrictions │▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Touch dates Yes │▒▒▒▒▒▒▒▒▒│ Errorlevels │▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Show missing No │▒▒▒▒▒▒▒▒▒│ Display │▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Upload spa╒══════════════════════════════════════════ Archivers ╕ ▒│ Logon.Newf│ │ ▒│ Newfiles.T│ Arc 1 ZIP C:\PKUNZIP.EXE -E @ C:\PKZIP.EXE -A @ │ ▒│ Download s│ Arc 2 ARJ C:\ARJ.EXE x -y @ C:\ARJ.EXE a -r -jm @│ ▒│ Download e│ Arc 3 LZH C:\LHA.EXE e @ C:\LHA.EXE a @ │ ▒│ Download s│ Arc 4 PAK C:\PAK.EXE e @ C:\PAK.EXE a @ │ ▒│ No dupe ex│ Arc 5 SDN C:\PAK.EXE e @ C:\PAK.EXE a @ │ ▒│ DL descrip│ Arc 6 ZOO C:\ZOO.EXE e @ C:\ZOO.EXE a @ │ ▒│ List forma│ Arc 7 SQZ C:\SQZ.EXE X @ C:\SQZ.EXE A /SP1 @ │ ▒│ Missing fo│ Arc 8 │ Archive format definition Below is a screen snapshot of the Upload Scanner menu to show you how to setup Labtest in your Upload Scan utility command line. Labtest will not move or delete files that fail any of the tests, thus it is important to set up RA to handle it. File System Options Modem Manager ═╒════════ File options ╕═════════╒══════════════╕═════════════ ▒│ │▒▒▒▒▒▒▒▒▒│ Messages │▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Upload credit 120 │▒▒▒▒▒▒▒▒▒│ Files │▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Payback credit 60 │▒▒▒▒▒▒▒▒▒│ Restrictions │▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Touch dates Yes │▒▒▒▒▒▒▒▒▒│ Errorlevels │▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒│ Show missing No │▒▒▒▒▒▒▒▒▒│ Display │▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒╒══════════════════════════════════════════════ Upload Scanner ┐ ▒│ │ ▒│ Scan online Yes │ ▒│ Failed scan /unavailable │ ▒│ Scan utility C:\RA\LABTEST.EXE @ /O *M │ ▒│ │ ▒╘═════════════════════════════════════════════════════════════─┘ ▒│ DL description Ask │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒╒═══ Fail action ╕▒▒ ▒│ List format │▒▒▒▒ All Rights Rese▒│ │▒▒ ▒│ Missing format │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Delete No │▒▒ ▒│ Upload scan │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Unlisted No │▒▒ ▒│ RAMGR FnKeys │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Notavail Yes │▒▒ ▒│ Ext arcview │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ Move to 0 │▒▒ ▒│ Archivers │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒▒ ▒│ │▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒╘════════════════╛▒▒ ▒╘══════════════════════╛▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ────────────────────────────────────────────────────────────────── You must make sure the file areas are setup correctly. Labtest will look in FILES.RA for your preferred archive type. If nothing is defined there, Labtest will default to the type set in LABTEST.CFG. The two important pieces of information here are the UL Scan and ArcType fields. The rest is arbitrary. Labtest has the ability to change a user's security level and/or flags if the uploaded file fails the virus scan portion of Labtest. Note that other test failures have no effect on the security level or flags, only the virus scan portion does. This is an extremely powerful option as you can prevent the user from uploading another file until you contact him about the problem. Described below are sample menu settings which you can impliment an upload security system. Fire up RACONFIG and go into the menu manager section. Here we will add another upload option to your menu. Below is two lines from the author's system which handle an upload attempt by a user. The first is the actual upload command line which almost everybody has one in their menu. Your actual display may be much different than this, that's ok. Notice directly below the actual upload, is another menu item with the same hot key. You should have these menu items next to each other because only one of them will be displayed depending on the flag setting. If you don't have them next to each other, it may throw off your menu display. (If you use textfiles to display your menus, then the actual order of doesn't matter). Move the highlight bar to the actual upload menu item. Hit return to edit the your upload command. Text display Key Action Optional data Actual: (U)pload │'U'│ Upload │ /FG=205 /L Fake: (U)pload │'U'│ Disp CR │ VIRUS Make sure the flag setting which you defined in LABTEST.CFG is set to a 'O' in your menu. For example, on Software Solutions BBS, we use the C1 flag for this feature. In our menu: │ A flags -------- Age 0 │ B flags -------- MinSpeed 0 │ C flags O------- MaxSpeed 0 │ D flags -------- Credit 0 │ Notice the C1 flag is 'O'. This tells RA that this flag MUST be set to OFF in order for the user to select this menu item. Now, go back to the menu item list and move the highlight bar directly below the actual upload command. Hit insert to add a new item. Here, we will define a whole new upload command. View the next screen snapshot for an idea of what we're doing here: ╒════════════════════════════════════════════ Edit Menu Item ╕ │ │ │ 1 2 3 4 5 │ │ 1234567890123456789012345678901234567890123456789012345678 │ │ (U)pload << make it look the same as the real thing! │ │ │ │ VIRUS << enter filename to display to 'virus-users' │ │ │ │ Action Display .ANS/.ASC with CR pause at end (Type 45) │ │ Display │ │ OptData │ │ HotKey U << same as your 'real' upload command! │ │ AutoExec No │ │ Colour Colour example │ │ │ │ MinSec 0 TimeUsed 0 │ │ MaxSec 0 TimeLeft 0 │ │ A flags -------- Age 0 │ │ B flags -------- MinSpeed 0 │ │ C flags X------- MaxSpeed 0 │ │ D flags -------- Credit 0 │ │ │ │ │ ╘════════════════════════════════════════════════════════════╛ Notice the optional data line has a file name VIRUS in it. This is an .ANS/ASC file which you will create in your text file directory to display to a user who has uploaded a file infected by a virus. This file should explain why they can't upload, what they should do (leave a message to you) and can even remind them of your upload/download ratios. Hence, if you have ratios in effect, the user may not be able to download since they can't upload anything! Real attention getter! Now, in the above screen, set the Action command to display an .ANS/ASC file. In the above example, VIRUS is actually VIRUS.ASC, a simple text file in the text file directory, and RA will display the file and wait for the user to hit ENTER after it is displayed. Notice that the C1 flag is set to X. This means that if the C1 flag is SET (Labtest will set it), then this menu item is 'selectable'. Remember, our real upload command requires the C1 flag to be OFF or NOT SET in order to be selectable. Get the picture? If the user has uploaded a virus infected file, when they attempt to upload again, they will be denied and our nasty-gram will tell them why. You may do the same thing with security levels instead of flags, but we'll leave the rest up to you. Labtest now uses an external ansi screen to give the user something nice to watch while Labtest goes to work. The full path and filename of the display screen must be identified in LABTEST.CFG. Additionally, a special control file is used to control how Labtest displays responses on the screen. If the user does not have ANSI capabilities, then Labtest will display regular ASCII text. The control file is used regardless of ANSI or ASCII settings. Please read the SCREEN.CTL file for additional information on controlling Labtest's output. Note that if a feature is disabled via either the configuration file or the command line, nothing will be displayed at all. Please do not remove the copyright information from the display screen as it is my only advertisement! ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ SUPPORT FILES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ The following is a list of files related to the operation of this program. It is noted whether or not the file is absolutely required in order for the program to run. Filename Required Description ------------ -------- -------------------------------------- LABTEST.EXE Yes The main executable. DOSWIN.EXE Yes Required for use of Dos Window LABTEST.CFG Yes Configuration file - ascii text file LABTEST.ANS Yes Screen displayed to users SCREEN.CTL Yes Control file for output screen COMMENT.CTL Yes Used when inserting archive comments ORDER.FRM No The program registration form. LABTEST.DOC No The User's Manual *.MSG No Message text files to be written to the user You will also need to have the various archive programs and virus scanning program in your DOS path. Customization ──────────────────────────────────────────────────────────────── Included with the distribution archive is a sample LABTEST.ANS, LABTEST.ASC and accompanying SCREEN.CTL files. You may use these stock screens without modification. But most sysops like to give their BBS a personal touch. In depth information on how to tell Labtest where to display text on the screen is contained in the control file SCREEN.CTL. You can use a drawing program like THEDRAW to change the .ANS screen. You can also have a different screen for each node that you run, by using the /G command line switch and specifying a different configuration file for each node. During the processing, provided you have enabled the Dos Window feature, Labtest will use the screen region beginning at line 15 and ending at line 23. This will not effect the user's screen, only the sysop screen. If you customize your LABTEST.ANS screen, please send us a copy so we can include it in the archive as a sample for others to use. You may name the screens and control file anything you wish, just be sure to put the correct name and path in the LABTEST.CFG file. ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ USING LABTEST ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ To run Labtest, you must have a fossil driver installed. If you want to run Labtest in local mode, you will still need a fossil driver, but you should use the /L switch to override the reading of the door information file. Labtest will read the commandline to fetch the file names to be processed. Valid filenames include: Wildcards (*.*, *.ZIP, etc..) One or more filenames (ie C:\BBS\UPLOADS\NEWFILE.ZIP) You can mix and match any of the above. You can even have multiple wildcards, like C:\BBS\*.* C:\BBS\UPLOADS\*.* C:\MODEM\DOWNLOAD\*.ARJ, etc.. Note: When using wildcards Labtest will only process those files that were not previously processed by Labtest. Labtest keeps track of which files have been already processed. You may force Labtest to process all files by using the /O (Override) command line switch. Using the /O switch is not recommended in conjunction with a wildcard. Override is useful when rearchiving is not enabled or on single files. Override should always be enabled when running Labtest on the BBS to gaurantee that the file will be properly handled. Please note that Labtest will search the FILES.RA file for a path matching the path specified on the command line. Labtest will expand wildcards to a path and wildcard. If there was no matching path found in the FILES.RA file, no updates will be made to the file database. Additionally, if the file being processed is not found in the database, Labtest will not add it to the database. To run Labtest as a nightly event in your BBS, install Labtest in your system's event handler: \/==Local Mode! C:\LABTEST\LABTEST.EXE C:\BBS\UPLOADS\*.* /L The above line would cause Labtest to process any 'new' files in the upload directory. The above method is useful if your system recieves files through a "front door" program. Running Labtest in a Multi-Node Environment ──────────────────────────────────────────────────────────────── In RACONFIG, use the following commandline: C:\RA\LABTEST.EXE @ /N*N *M For Multi-node systems, specify the node number which Labtest is running under by utilizing the /N switch. The proper format for this switch is /N*N. This will prevent Labtest from unpacking the archive file in a directory already in use by another node. Command Line Options ───────────────────────────────────────────────────────────────── The follow is a description of valid command line options which you can better control Labtest's performance: /L Causes Labtest to run in 'local' mode. In Local Mode, Labtest will not attempt to read a door information file. /O This is the Override command. Labtest will normally process only those files not previously proceseed. Using this command, you will force Labtest to ignore it's own time stamp feature. This is highly recommended while running under the BBS system. An industrious person may determine the special file stamping and attempt to trick Labtest. This will ensure that this will never happen. /C This switch forces Labtest to look in the specified directory for the EXITINFO.BBS file. Example: /CC:\RA\NODE1. Note that this is only a path, not a full filename! Proper format for this switch is /CC:\RA\NODE*N (specify whatever path you like, use of the *N is optional) /N Specifies the node number which Labtest is operating on. This is extremely important to keep one user's files from getting mixed up with another user's files. The proper format for this switch is /N*N on the Labtest command line in RACONFIG. /G This switch tells Labtest to use an alternate cfg file. Specify the full path and file name of the configuration file with this switch. Example: /GC:\RA\LABTEST\LABTEST.CFG. This is particularly useful if you have a multi node system and have the nodes configured significantly different that you would like to post a different style of message to the user's or perhaps disable certain features of Labtest but want them to be enabled on the other nodes. /D Starts Labtest in Debug mode, where additional helpful information is written to the log file in case you are having problems. This information should be forwarded to Software Solutions in case you are having problems. /NOSCAN When this command is given, Labtest will not run /NS the virus scanner on any file during the current session. Note this is only useful when you just want to convert your files to one format. Otherwise, this is not recommended. /NOREARC Prevents Labtest from rearchiving files. /NR /NOCOMMENT Prevents Labtest from adding an archive comment. /NC Running Labtest from RAMGR ─────────────────────────────────────────────────────────────── You may wish to setup one of the RAMGR function keys in RACONFIG to run Labtest from the File Manager. Specify the same command line in RACONFIG.RAMGR.Fkeys as you did in RACONFIG.SCANNER. Then, when you are browsing through RAMGR, hit the ALT+(Fkey) to run Labtest. When Labtest returns to RAMGR, the results should be obvious! ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ THE CONFIGURATION FILE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ Beginning with version 2.2, Labtest no longer uses a separate program to write the configuration file. A simpler, easier to use text file based configuration system will be utilized by Labtest to establish its environment. You may have more than one configuration file. You may optionally specify the path to the configuration file by using the /G command line switch. The proper format of this command line is: /GC:\RA\LABTEST\LABTEST.CFG LABTEST.CFG may reside in any directory. It is recommended that you place Labtest and all of its accompanying files in your DOS path so Labtest will be able to find the required files without trouble. There is three ways to tell Labtest where the configuration file is located, by your dos path, by the LABTEST environment variable (SET LABTEST=C:\RA\LABTEST) or via the /G switch. ╒══════════════════════════════════════════════════════════════╕ │░░░░░░ NOTES FROM THE AUTHOR ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ╘══════════════════════════════════════════════════════════════╛ Labtest is distributed "AS IS" and no warranty or gaurantee is supplied. The end user accepts all responsibility for the proper use and operation of Labtest. Under no circumstances will Software Solutions be held liable for any damages or loss of resources either directly or indirectly resulting from the use or misuse of this software. Technical notes ──────────────────────────────────────────────────────────────── Labtest was written entirely in Turbo C++ version 3.0. Door interface routines provided by OpenDoors 4.2 by Brian Pirie (all rights reserved). Labtest detects the following archivers (SFX where self extracting files are supported) and their associated de-archivers: (Note: ??? means not thoroughly tested) Archiver Version PKZIP/SFX 1.11 through 2.04g ARJ/SFX 2.20 through 2.41 LHA/SFX 2.13 PKPAK/SFX 3.61 PKARC 3.5 LHARC ??? ARC ??? Labtest operates by shelling to the user defined archive and scanning programs. If the archive programs return an errorlevel of 0, Labtest assumes the operation was successful. If any other errorlevel is returned by the software, then the archive is tagged as 'bad'. Note however that utilities like PKZIP will return an errorlevel of non-zero if you did not have enough memory or disk space to unpack the archive. Labtest will always log the errorlevel reported by an archive utility and the scan utility. Consult the documentation on the utilities you decide to use with Labtest for specifics on errorlevels. Labtest will run the virus scanning utility once for each executable file extracted from the archive. This method was chosen over shelling once and scanning a whole directory so we could inform the user and the sysop of which file failed the scan. Also, Labtest will log the specific filename which failed the scan. After a file is successfully unpacked, scanned and repacked, Labtest will throw in your ZIP/ARJ comment (if defined in LABTEST.CFG). Last but not at all least, Labtest will update RemoteAccess 2.00 file database system to reflect the new changes. Labtest initially renames the archive file. If an error occurs during processing, the file will be renamed again to its original name for further inspection by the Sysop. Notes on Secured Archives ──────────────────────────────────────────────────────────────── PKZip and ARJ archive utilities have the ability to stamp an archive file with a special code protecting it from future changes. Labtest detects these 'archive stamps' and will either ignore them or honor them, depending on how you have the option set in LABTEST.CFG. ──────────────────────────────────────────────────────────────── Software Solutions BBS is the official support site for Labtest. All future versions of Labtest will be available on Software Solutions BBS. Labtest may be requested by using the magic name LABTEST or you may log onto the BBS and download the latest version. Additionally, if you are running Fido Net mail, you may set up your system for the Labtest echo, originating from 1:214/54. Tag name is LABTEST. Send a netmail message to 1:214/54, indicate your password and archive preference. Your system will then be placed on the export list. From there, just poll us and you'll get the latest tips, user comments and suggestions. It's also an excellent way to keep in touch with us and Labtest users. Software Solutions 1:214/54 BBS: (209)997-0224 PO Box 1233 Lemoore, CA 93245-1233