home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
LBTST30A.ZIP
/
LABTEST.DOC
< prev
next >
Wrap
Text File
|
1994-06-01
|
65KB
|
1,583 lines
┌─┐ ┌──────┌──────┌─────┌─────┌─────┌─────┐
│ │ │ ┌──┐ └┐ ┌─┐ ├─┐ ┌─│ ┌───│ ┌───└─┐ ┌─┘
│ │ │ └──┘ │ └─┘ │ │ │ │ └─┐ │ └───┐ │ │
│ │ │ ┌──┐ │ ┌─┐ │ │ │ │ ┌─┘ └───┐ │ │ │
│ └──│ │ │ ┌┘ └─┘ │ │ │ │ └───┌───┘ │ │ │
└────└─┘ └─└──────┘ └─┘ └─────└─────┘ └─┘
Version 3.0
Copyright (c) 1993-94 by Mark Williamson
> This documentation file has been re-written and the information
> contained herein only applies to version 3.0 and above.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ LEGAL STUFF ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
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 Joaquim
Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS
RESERVED.
This product uses the RIPscrip language, Copyright (c) 1993
Telegrafix Communications, Inc.
RemoteAccess, RACONFIG, RAMGR and RA are copyrighted (c) 1993
Andrew Milner
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ TABLE OF CONTENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Licensing information......................................... 1
Introduction.................................................. 2
Installation.................................................. 3
Environment variables...................................... 3
RA environment variable................................. 3
Labtest environment variable............................ 3
Configuration................................................. 4
Files/Paths................................................ 4
Log file path........................................... 4
Swap directory.......................................... 4
Bad files directory..................................... 4
ANSI screen............................................. 4
ASCII screen............................................ 4
RIP screen.............................................. 5
Screen control file..................................... 5
Add files list.......................................... 5
Kill files list......................................... 5
Page file............................................... 5
Hack Report file........................................ 5
Archive comment file.................................... 5
Messages................................................... 6
Sysop message board..................................... 6
User message board...................................... 6
Thank you message....................................... 6
Virus message........................................... 6
Bad file message........................................ 6
Old file message........................................ 7
Bad GIF message......................................... 7
Hack report message..................................... 7
Sysop messages.......................................... 7
File description notes.................................. 7
Options.................................................... 7
Registration Key........................................ 7
Maximum file age........................................ 7
Set security level...................................... 7
Set user flags.......................................... 7
Add uploader name....................................... 7
Sound virus alarm....................................... 8
> Remote Status Window.................................... 8
Gif file options........................................ 8
Minimum width........................................ 8
Minimum height....................................... 8
Minimum colors....................................... 8
Separator character.................................. 8
Compress GIF files................................... 8
Uncompress JPG files................................. 9
i
Archive file options.................................... 8
Default archive type................................. 8
Number of old files.................................. 9
File date options.................................... 9
Convert SFX files.................................... 9
Pack unknown files................................... 9
Keep archive security................................ 9
Imbedded archives.................................... 9
Process descriptions................................. 9
Maximum file size.................................... 9
Adjust user credit...................................10
Failed scan action...................................10
Archiver setup.......................................10
Extension.........................................10
Unpack command....................................10
Pack command......................................10
Comment command...................................10
Memory required...................................11
Use dos window....................................11
Virus scanner setup..................................11
Scan command line.................................11
Memory required...................................11
Use dos window....................................11
> Errorlevel........................................12
FILES.RA...................................................12
File area path..........................................12
Default archive type....................................12
Long descriptions.......................................12
MESSAGES.RA................................................12
Sysop message board type/JAMbase path...................12
User message board type/JAMbase path....................12
CONFIG.RA..................................................12
Multi-line..............................................12
Hudson message base path................................13
Sysop name..............................................13
System name.............................................13
Upload scan.............................................13
Running Labtest...............................................13
Command line options.......................................13
/L Local................................................13
/O Override.............................................13
/C Exitinfo.bbs path....................................13
/N Node number..........................................13
/NS No scanning.........................................13
/NR No converting.......................................13
/NC No commenting.......................................14
Processing file areas...................................14
Processing wildcards....................................14
Online.....................................................14
RAMGR......................................................14
With OS/2 and Desqview.....................................15
ii
Customization.................................................15
ANSI screen................................................15
RIP screen.................................................15
Support files.................................................16
External program errorlevels..................................17
How to contact the author.....................................19
iii
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ 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 $20.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 ORDER.FRM.
Labtest is Copyrighted (c) 1993 - 1994 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, the documentation or the
display screens.
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.
Comments, suggestions and bug reports are welcome. If you have
any, you should contact Mark Williamson at Fidonet 1:214/53.
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. Please also include information about
the platform Labtest is running on.
1
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Labtest was initially developed as a non-BBS tool I used to
process my files which I downloaded from BBS's. When I became a
Sysop, I decided that I needed an upload scanner. Thus, I
commenced work on Labtest. Originally, as an upload scanner,
Labtest was not specific to any one BBS program. That created
severe problems for me, so I chose to limit my efforts to the
RemoteAccess community.
Labtest started life as version 2.00v1. Then quickly progressed
through numerous stages, albeit some were very painful. In its
current state, as version 3.0, Labtest represents a great deal
of research, bug-hunting, and an appreciable amount of patience
on the part of the Sysops out there using the program.
Labtest is written with Borland C++ 3.1, using the OpenDoors
library by Bryan Pirie.
Although there are no guarantees that you will have success at
setting up and using Labtest, I have gone through great lengths
to make the configuration easy. If you have any recommendations
or possible bugs to report, please see the last page of this
documentation for ways you can get a hold of the author.
2
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ INSTALLATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Installation of Labtest is relatively simple. You should create
a directory especially for Labtest or place the program and
support files in your RemoteAccess system directory. The
location of Labtest is unimportant. To install Labtest, unpack
> the distribution archive into your desired directory. Changed
> from previous versions, you no longer need to have a LABTEST
> environment variable. Instead, put Labtest in your DOS Path so
> that you may run it from any directory on your system, and
> Labtest will find its files by searching the path.
If you are running a multi-node system, you have the option of
having a different configuration file for each node your system
runs. To create a config file for each of your nodes, simply
copy the LABTEST.CFG file to LABTEST.Cnn, where nn is the node
number, 1 being node 1 and so one. Do not place any leading
zeros in the node number. For example, LABTEST.C1 is the
configuration file for node 1. Using this multi-file
configuration, you can further customize Labtest for your
system. Labtest will look for the file LABTEST.Cnn first,
then, LABTEST.CFG.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ ENVIRONMENT VARIABLES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
> It is no longer required to have a LABTEST environment variable
> set, since Labtest now searches your DOS PATH for LABTEST.EXE,
> and expects to find its associated files in this directory.
Ensure you have your RA environment variable set. Include the
following commands in your AUTOEXEC.BAT file:
SET RA=<path>
where <path> is the drive and path for your RA. Do not include
an ending backslash '\'.
It is also recommended that you add the Labtest directory to
your DOS PATH statement, so you can run Labtest from anywhere on
your computer.
3
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ CONFIGURATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
> With the release of version 3.0 comes a new setup program which
> will read your CONFIG.RA file and adopt much of the information
> needed by Labtest and store it in your configuration file.
> Labtest 3.0 no longer uses a text configuration file so you will
> not be able to modify it with a text editor. Labtest uses other
> information from your FILES.RA and MESSAGES.RA files as well. To
> ensure that changes made in your *.RA files is reflected in your
> configuration file, it is recommended to run LTSetup after you
> make changes to any of your *.RA files.
When you load the Setup program, you will be presented with a
pull down menu that has four possible choices: Files/Paths,
Messages, Options, and Quit. Each menu selection and the
submenus it contains will be described below:
All prompts and log file text used by Labtest and LtSetup are
contained in an ASCII text file called LABTEST.LNG. It has been
provided in ASCII format so that international users can easily
modify the prompts for their native language. Note that the
order of the prompts is extremely important and should not be
changed. Additionally, no prompt can be more than 80 characters
wide. The LABTEST.LNG file must be located in the same directory
as LABTEST.EXE and LTSETUP.EXE. Several <reserved> prompts
appear between the LTSETUP prompts and the LABTEST text. You
MUST not remove any of these as it will throw off the order of
the remaining prompts.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ FILES AND PATHS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
This menu contains the bulk of the filenames and paths that
control where Labtest will store some items and where it can
find special control files and screen display files.
Log File Path: This is a drive and path where Labtest should
write the LABTEST.LOG and UPLOAD.LOG files. The actual name of
these files depends on your whether you are running a multi-line
system or not.
Swap path: Specify a complete drive and path where Labtest
should store its temporary swap file when executing external
programs.
Bad files path: Specify the full drive and path of where Labtest
should place files which are failed by Labtest. If this path is
defined in your FILES.RA, the database will also be updated.
Ansi screen: Specify a full path and filename of the .ANS screen
Labtest should display to your ANSI callers when processing a
file. This screen will also be used for the local display.
Ascii screen: Specify a full path and filename of the .ASC
screen file to display to callers not supporting RIP or ANSI
graphics.
4
Rip screen: Specify a full 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.
Screen control file: Specify the full path and filename 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!
Add file list: While not a popular thing to do, Labtest can add
files to an archive. Specify here the full path and filename of
your add file list. This file should contain full paths and
filenames, one per line, of files you want added to EACH archive
processed. Labtest only adds these files to the BASE archive and
never adds them to the imbedded archives.
Kill file list: This is the opposite of the above. This file
should contain filenames (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.
Page file: Specify the full path and filename of the
RemoteAccess compatible page file Labtest should use as a virus
alarm. This is ignored if you set Sound Alarm to No (described
later) or if you have the Scroll Lock key on. See the file
PAGE.LAB in the distribution archive.
Hack report file: Specify the full path and filename of the HACK
.COL or .IDX file Labtest should search. This file should
contain base file names of files you do not want on your system.
Do not include the file extension. Labtest is fully capable of
reading and parsing the Hack Report .IDX and .COL files without
modification.
Archive comment file: This is the full path and filename of a
text file you want added as an archive comment to each file
Labtest processes. If you do not want ANY archive comments
added, leave this field blank. See also the Archive Definitions
menu under the Comment field. You may optionally add the
contents of the FILE_ID.DIZ as an archive comment.
5
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ MESSAGES TO USER/SYSOP ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
In the distribution archive you should find several *.MSG files.
These files contain text which will be imported by Labtest into
the message base. These messages may be totally customized by
you to give your system a personal touch. There are a few macros
which will be expanded by Labtest during reading of the message
file. These are explained below:
@SYSOP@ Sysop name (as defined in RACONFIG)
@BBS@ BBS system name (RACONFIG)
@USERFIRST@ First name of the user
@UPLOADS@ Total number of uploads the user has posted
@UPLOADK@ Uploads (in K) the user has posted
@AGE@ Maximum age in years for files
@GIFRESOLUTION@ Minimum acceptable GIF resolution
@UPLOADFILE@ The name of the uploaded file.
@VIRUSINFO@ Labtest will insert specific information
about the virus detected (if any). Used
*ONLY* in the VIRUS.MSG file.
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.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ MESSAGES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
This menu controls how Labtest should write messages to the
Sysop and to the User as well as writing notes to the file
description.
Sysop message board: Specify the message board number where
Labtest should write messages to the Sysop concerning various
stages of the process. Specify 0 if you do not want ANY messages
written to the Sysop.
User message board: Specify the message board number where
Labtest should write messages to the user concerning the
uploaded file. Specify 0 if you do not want ANY messages written
to the User.
Thank you message: Specify the full path and filename of the
file to be imported thanking the user for the upload.
Virus message: Specify the full path and filename of the file to
be imported informing the User that the file failed the virus
scan.
Bad file message: Specify the full path and filename of the file
to be imported informing the User that the file could not be
processed by Labtest.
Old file message: Specify the full path and filename of the file
to be imported informing the User that the file failed the age
test.
6
Bad gif message: Specify the full path and filename of the file
to be imported informing the User that the .GIF file failed the
resolution test.
Hack report message: Specify the full path and filename of the
file to be imported informing the User that the file was found
among those listed in the Hack report.
Note: If you do not want a specific message to be written to the
user, do not specify a path or filename for that message file.
It is important to adhere to this rule due to the way messages
are written by Labtest.
Sysop messages: Labtest will write a short note to the Sysop
concerning the status of the file. You may turn on or off any of
these messages by selecting Yes or No at the appropriate Sysop
Message menu prompt.
File comments: Labtest will append a short note to the file
description concerning the status of the file. You may turn on
or off any of these notes by selecting Yes or No at the
appropriate File Comments menu prompt.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ OPTIONS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
This menu controls the overall performance of Labtest.
Registration key: Enter your personal registration number. Enter
0 if you have not registered.
Max file age (years): Specify in years the maximum desirable
file age. Labtest will fail files older than this.
Set security level: Labtest can lower the user's security level
if they upload a file containing a virus. Note that the security
level is ONLY affected if the file fails the actual virus
scanning stage. Security level is not affected by any other
process. Specify 0 if you do not want Labtest to modify the
user's security level.
Set user flag: Specify the flag and status to set if the file
fails the virus scan. The same applies as for set security
level. For example, A1 ON would cause Labtest to set flag A1 to
ON if a file fails the virus scan stage. Leave blank if you do
not want Labtest to modify the user's flags.
Using the flags or set security level settings, you can
effectively prevent a user from uploading a file. For example,
if you have the MinSec for your Upload command set to 3, and you
set Labtest to drop the security level to 2, then the user
cannot access the upload command.
Add uploader name: Specify whether Labtest should add the
uploader's name to the file description. Labtest will write
'Uploaded by: <name>' at the end of the file description if this
is set to Yes.
7
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.
> Remote Status Window: Labtest displays a small status window at
> the bottom of the sysop's screen. You may also display this
> window to your users by setting this option to Yes. The status
> window displays a great more information about the file being
> tested.
Gif file options
The following only apply to .GIF or .JPG files:
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).
Min. Gif Width: Enter the minimum acceptable width in pixels for
.GIF and .JPG files.
Min. Gif Height: Enter the minimum acceptable height in pixels
for .GIF and .JPG files.
Min. Gif Colors: Enter the minimum acceptable number of colors
for .GIF and .JPG files.
Note: There is no set standard for JPEG files and resolution
checking is sort of hit and miss with these files.
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.
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.
Uncompress JPG files: 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.
Archive file options:
This menu contains all the necessary info for Labtest to process
archived files.
Default archive type: Specify the three letter extension of the
default archive format. This is overriden 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.
8
No. of old files: Specify the minimum number of files that fail
the Max file age before the whole archive is failed. For
example, you may want the archive to be failed after 10 old
files are found.
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.
Convert SFX files: If the uploaded file 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.
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.
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.
Imbedded archives: Here you may specify how Labtest should
handle imbedded archives. The options are described below:
Ignore: Do nothing to imbedded archives.
Scan: Scan imbedded archives. Do not rearchive them.
Rearc: Rearchive imbedded archives. Do not scan them.
Scan/Rearc: Scan and rearchive imbedded archives.
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 characters such as those used for boxes and
special characters.
Max. file size: You may define the largest file size in kilo
bytes that Labtest should attempt to handle. Files exceeding
this size are ignored. This applies only to archive files and
not .GIF/.JPG files.
9
Adjust user credit: Specify if you would like Labtest to adjust
the user's upload credit for the new file size after conversion.
This prevents crafty individuals from being overcredited for
junk files.
Failed scan action: 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.
Archiver setup
This menu contains the information needed by Labtest to run your
external archive utilities. Setup is preconfigured for the more
popular archive utilities and associated command lines. However,
you may change these as you wish. The following information
pertains to the Archiver Setup menu:
Extension: This is the three letter file extension used by
the archive utility.
Unpack command line: This is the command line (path is optional)
that will be executed by Labtest to unpack, or decompress,
files of this type. You should specify the program name, command
line options, and the @ character which will be replaced by
Labtest with the filename. The @ character should be in the
correct position in the command line, just as you would execute
it from DOS.
Pack command line: This is the command line (path is optional)
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 filename. The @ character should be in the correct
position in the command line, just as you would execute it from
DOS.
Comment command line: This is the command line (path is
optional) 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 filename. The @ character should be
in the correct position in the command line, just as you would
execute it from DOS.
10
MemReq (memory required): This is the number of kilobytes of
memory Labtest should set aside for archivers of this type. The
default is 400k.
Labtest may be configured to convert GIF(sm) files to JPG files
or vice versa. Two programs, CJPEG.EXE (Compress JPEG) and
DJPEG.EXE (Decompress JPEG), are supplied with the Labtest
distribution archive.
Use dos window: Specify yes if this archiver can be used within
the dos window. You also have the option of using an 'invisible'
dos window, which doesn't allow the archive utility to display
any text at all, preserving the sysop's screen entirely.
If you plan on converting GIF/JPG files, you should see the
settings under Gif File Options for setting the appropriate
switches.
DJPEG will uncompress a JPEG file, resulting in like-original
image quality. It is important to note here that DJPEG will NOT
decompress a file compressed with GIF2JPG.EXE. However,
JPG2GIF.EXE will properly handle a JPG file compressed by
CJPEG.EXE.
You must make sure the file areas are set up 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 important pieces of information here are the
LongDesc, File path and ArcType fields. The rest is arbitrary.
If you want only one archive type for all of your files, leave
the ArcType field empty, and Labtest will use the setting
specified by LABTEST.CFG.
Virus Scanner Setup
Labtest can be configured to run up to 20 virus scanners, each
one right after another, on each uploaded file. Since version
3.0 no longer uses the SCAN.CTL file, you must configure your
upload scanners in LTSETUP.
Scan command line: Specify the virus scanner and command line.
You do not need to specify a complete path. If you are using
McAfee's SCAN.EXE or NETSCAN.EXE, Labtest can determine the
actual name of the virus as reported by Scan. To enable this
option, 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. If you use /REPORT, you must use
$REPORT$ or Labtest will not read the results from the report
file that Scan creates.
Memory required: This is the number of kilobytes Labtest should
set aside for this virus scanner. If this amount of memory is
available when Labtest executes the program, Labtest will not
swap out of memory.
Use Dos Window: Specify Yes if this virus scanner can be run
within the dos window. Some virus scanners, like Microsoft
Antivirus, do not work well in the dos window. As mentioned in
the Archiver Setup section, you may specify 'invisible' if you
11
want your sysop screen preserved entirely, preventing the
scanner from displaying any output at all.
Errorlevel: Specify the errorlevel returned by this scanner if
and only if a virus is detected. This avoids a problem with
scanners that return different errorlevels for different
situations i.e. no memory, no files to scan, etc.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ FILES.RA ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Labtest obtains much of the needed information concerning your
file system directly from your FILES.RA. Each item is identified
and described below:
File area path: Labtest uses this information when moving files
and updating your database. You should have a complete path,
including drive, defined in each of your file areas.
Default archive type: This field is optional, and if not
specified, is overridden by the Default Arc type specified in
your Labtest configuration file. Archives destined for this file
area will be converted to this archive type.
Long desc: You must enable long descriptions for all of your
file areas. This does not actually affect Labtest, however, the
descriptions imported from FILE_ID.DIZ files will not be
displayed by RemoteAccess unless this is set to Yes.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ MESSAGES.RA ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Like FILES.RA, Labtest obtains information concerning your
message areas from MESSAGES.RA.
Labtest determines the message board type (JAM or HUDSON) based
on that found in the message area pointed to by the Sysop and
User message boards defined in your Labtest configuration file.
Additionally, Labtest will determine the JAM message base path
if the message area is a JAM base.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ CONFIG.RA ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
As with FILES.RA and MESSAGES.RA, other important information
about your BBS is read from CONFIG.RA:
Multiline: The Setup program determines if your system is a
multiline system based on the setting found under System -
Multiline. This controls the log file writing and some safety
checks provided by Labtest to keep each node from clashing with
another.
Message base path: The base directory for your Hudson message
base. Jam message base paths are determined from your
MESSAGES.RA file.
File base path: The base directory for your file databases.
12
Sysop name: Your Sysop name of course!
System name: The name of your BBS.
Be sure to setup your Upload Scan portion of CONFIG.RA:
Below is a screen snapshot of the Upload Scanner menu of
RACONFIG to show you how to setup Labtest in your Upload Scan
utility command line. Labtest will mark the files as indicated
in the Failed Scan Action section of Setup. Additionally, you
may specify a file area in Setup to move failed files to, and
Labtest will move the files to that area.
╒══════════════════════════════════════════════ Upload Scanner ┐
│ │
│ Scan online Yes │
│ Failed scan /unavailable │
│ Scan utility C:\RA\LABTEST.EXE @ /O *! *M │
│ │
╘═════════════════════════════════════════════════════════════─┘
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ RUNNING LABTEST ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Labtest may be run from RemoteAccess while a user is online,
from the RAMGR program as a function key or from the Dos command
line. There are several command line options which temporarily
modify Labtest's operation, overriding the configuration file.
These command line options, or switches, are described below:
/L Causes Labtest to run in 'local' mode. In Local Mode, Labtest
will not attempt to read a door information file nor will it
post messages to the sysop or the user.
/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.
> /E This switch forces Labtest to look in the specified directory
> for the EXITINFO.BBS file. Example: /EC:\RA\NODE1. Note that
this is only a path, not a full filename! Proper format for
this switch is /EC:\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.
/NOSCAN or /NS: When this command is given, Labtest will not run
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 or /NR: Prevents Labtest from rearchiving files.
13
/NOCOMMENT or /NC: Prevents Labtest from adding an archive
comment.
In addition, you must tell Labtest what file, directory or file
area you want processed. You may specify more than one file name
or directory, or any combination of the above. Wildcards are
valid. A few examples are listed below:
If you run Labtest with no command line parameters, Labtest will
load and run LTSETUP.EXE.
To run Labtest on your file area # 15 in local mode, processing
only new files:
LABTEST 15 /L
This will cause Labtest to process ALL files in the C:\UPLOADS
directory:
LABTEST C:\UPLOADS\*.* /L /O
This will run Labtest on the specified archive, in local mode
with debugging on:
LABTEST C:\UPLOAD\LABTST30.ARJ /L /O
To run Labtest from RemoteAccess, you must specify the following
commandline in RACONFIG - FILES - UPLOAD SCAN:
C:\RA\LABTEST\LABTEST.EXE @ /O *M
(The actual drive/path names will vary depending on your
installation)
The @ symbol is a RemoteAccess macro which is replaced by the
full path and filename of the uploaded file. The /O switch ensures
nothing is skipped by Labtest.
The *M causes RemoteAccess to swap out of memory, making room
for Labtest.
To run Labtest from the RAMGR program, you must define a
function key in RACONFIG - FILES - RAMGR FN KEYS. Use the
following command line:
C:\RA\LABTEST\LABTEST.EXE @ /O /L *M
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. Labtest will add the file information
to the database if it does not already exist. Additionally, if
the file being processed fails any portion of Labtest, the file
will be marked and/or moved according to the setting in the
LABTEST.CFG. This is particularly useful when handling files
offline or when using an upload door program.
14
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ RUNNING UNDER OS/2 AND DESQVIEW ░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Labtest has been tested on systems using OS/2 2.1x and Desqview
2.6. Important things to note when running under these
environments is to set aside enough memory for Labtest and the
external programs it uses. Normally, this would be about 450k or
more. All of Labtest's screen output is compatible with Desqview
and OS/2. You should ensure you have an ANSI driver such as
ANSI.COM (supplied with your distribution archive) in each of
the Desqview windows you are using Labtest in.
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ CUSTOMIZATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
Labtest's output (remote and local) is fully customizable by
using the LABTEST.CTL and various screen drawing programs.
Please refer to the file LABTEST.CTL in the distribution archive
for detailed information on how to modify and customize your
copy of Labtest. In general, all that is required is to modify
the supplied .ASC/.ANS/.RIP screens with an appropriate screen
editor. While editing, special note should be made as to the
location of various text prompts on the screen. Then, editing
the LABTEST.CTL file, change the corresponding prompts/
locations. For .ANS screens, this process is relatively simple.
However, for .RIP screens, this process becomes very complex and
is not recommended.
Included with the distribution archive is a sample LABTEST.RIP,
LABTEST.ANS, LABTEST.ASC and the accompanying LABTEST.CTL file.
You may use these stock screens without modification. But most
sysops like to give their BBS a personal touch. Indepth
information on how to tell Labtest where to display text on the
screen is contained in the control file LABTEST.CTL. You can use
a drawing program like THEDRAW to change the .ANS screen. During
the processing Labtest will use the screen region beginning at
line 17 and ending at line 23. This will not effect the user's
screen, only the sysop screen. If you have the Remote Status
Window set to Yes in LTSETUP, Labtest will use this region on
the user's screen as well. Please do us the courtesy of leaving
our copyright information in your custom screens as this is the
only advertisement we have.
> If the user's terminal is set for ASCII output only, the file
> named in LTSETUP -> Ascii Screen will be sent to the remote
> terminal, while the Ansi Screen is sent to the local terminal.
> The user will see the progress of the file as plain text prompts
> exactly as you will see them in the Status Window. These are the
> same text prompts used in writing to your log file.
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. On multi-line systems, it is possible to have a different
screen setup for each node, just create each screen and control
file, and specify them in the appropriate LABTEST.Cxx files.
15
About using RIP with Labtest
Labtest will determine the user's RIP graphics capabilities from
the EXITINFO.BBS file. If the user has a RIP-capable terminal
program, then the RIP screen specified in your .CFG file will be
displayed. Simultaneously, Labtest will display the .ANS file
specified in your .CFG file. The Sysop will hardly notice that
the user is using RIP graphics. To make it somewhat discernable
from an .ANS caller, the local screen will not have blinking
colors. This lets you know that the user is in RIP mode.
Due to the complexity of modifying the .RIP file and matching up
the locations of the text prompts, it is not recommended that
you attempt to change the .RIP screen. Instead just use the
supplied .RIP screen and you'll do just fine!
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ 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.
LTSETUP.EXE Yes Configuration program.
LABTEST.LNG Yes Help prompts for LTSETUP.EXE
DOSWIN.EXE Yes Required for Dos Window display box.
NODOSWIN.EXE Yes Required for the Invisible Dos Window.
PAGE.EXE No Plays the page tune file from dos.
DEC2RIP.EXE No Converts Decimal - Rip numbers
LABTEST.CFG Yes Configuration file - ascii text file
LABTEST.RIP Yes Screen displayed to RIP callers
LABTEST.ANS Yes Screen displayed to ANSI callers
LABTEST.ASC Yes Screen displayed to Ascii callers
LABTEST.CTL Yes Control file for output screen
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
DJPEG.EXE No Required for decompressing .JPG files
CJPEG.EXE No Required for compressing .GIF files
ANSI.COM No Needed for Desqview users (other
Desqview Ansi device drivers will
work, this is provided if you don't
have one.)
PAGE.LAB No Example page files that you can use
as a virus alarm.
16
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ EXTERNAL PROGRAM ERRORLEVELS ░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
> LABTEST ERROR CODES
>
> Labtest will exit with an error code indicating the success or
> failure of the file processed. The error codes are listed below:
>
> 0 :Success, no problems detected.
> 1 :A virus was detected.
> 2 :Archive file could not be processed. Possibly a bad
> archive.
> 4 :Gif file did not satisfy resolution requirements.
> 8 :The archive file date was beyond the maximum age limit.
> or maximum old file limit was exceeded.
> 16 :One or more imbedded files could not be processed.
> 32 :One or more files were listed in your Hack report.
> 64 :One or more files were found in your unwanted list.
>
> If more than one error occurred, Labtest will add the errorcodes
> and report the sum. Thus, if a file was old and failed the
> virus scan, Labtest will report an errorlevel of 9.
Errorlevels for external programs will be recorded in your
LABTEST.LOG file. If a problem arises, review the log file to
determine the errorcode and possible source of the problem.
The following information has been extracted from various
utility program documentation files to provide you with a single
source for error level definitions:
PKZIP ERROR CODES
1 :Bad file name of file specification
2-3 :Error in ZIP file
4-11 :Insufficient memory
12 :No files were found to add to the ZIP file or
no files were specified for deletion.
13 :File not found. The specified ZIP file or list file
was not found.
14 :Disk full
15 :Zip file is read-only and can not be modified.
16 :Bad or illegal parameters specified.
17 :Too many files.
PKUNZIP ERROR CODES
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 ERROR CODES
1 :Warning Specified file to add not found
17
Specified file to list, extract, etc., not found
or answering negatively to "OK TO PROCEED TO NEXT
VOLUME" prompt
2 :Fatal error
3 :CRC error
4 :ARJ-SECURITY error or attempt to update an ARJ-SECURED
archive.
5 :Disk full or write error
6 :Can't open archive or file
7 :Simple user error (bad parameters)
8 :Not enough memory
LHARC ERROR CODES
1 :CRC error
2 :Fatal error.
3 :Failed to write tempory files in the archive.
PKUNPAK ERROR CODES
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 ERROR CODES
1 :CRC error
2 :Out of memory
7 :Disk Full
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
18
╒══════════════════════════════════════════════════════════════╕
│░░░░░░ CONTACTING THE AUTHOR ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
╘══════════════════════════════════════════════════════════════╛
The author may be contacted by writing to:
> Mark Williamson
> PO Box 1233
> Lemoore, CA 93245
Or by sending Netmail to 1:214/53.
(The above is subject to change in July 1994, as I am moving to
San Diego, California.)
Alternatively, you may log onto the support BBS at (209)998-7249
and leave a comment to the sysop.
19