THD ProScan Version 13.0
for DOS and OS/2
THDCFG.EXE
-----------
- Outline -
-----------
This document outlines the operation of THDCFG.EXE which incorporates a
number of programs which were distributed separately with earlier versions.
The sections covered by this document are...
Install/Configure
Archive Editor
Language Editor
Ansi Demo/test
THDTERM (configure)
Author / Register
----------------------
- The opening screen -
----------------------
Upon running THDCFG.EXE you will be faced with an opening screen which
consists essentially of a lightbar style menu. You can select your appropriate
option by moving the highlighted bar to the option and pressing enter or by
typing the highlighted letter of the option you wish to choose. The <ESC> key
is the same as selecting the "Quit" option. The program uses approximately
400k of memory under DOS (OS/2 memory usage is unknown).
---------------------
- Install/Configure -
---------------------
This selection runs what used to be called THDINSTL.EXE. This is the
program needed to configure the various options available in THDPRO.EXE. From
most screens pressing the F1 key will bring up online help and pressing F2
will provide a shell to the operating system.
After selecting this option you will be taken to another menu with the
options...
Normal
Previous
Full
Quit / Back
Normal - Starts the configuration in it's default mode. In this mode the
program will check THDPRO.EXE for an existing configuration and if one
exists, it will move immediately to the final three option screens if the
configuration process. If no pre-existing configuration is found then you
will be stepped through the available options.
Previous - Prompts you for the location of the 'old' THDPRO.EXE from which to
extract an existing configuration. It then imports this configuration and
proceeds through the configuration process using the imported
configuration.
Full - Starts the configuration process as if the copy of THDPRO.EXE had never
been previously configured. This process is the same as configuring a
brand new copy of THDPRO.EXE using the "normal" option for the first
time.
Quit / Back - Returns you to the main menu.
This text will attempt to explain the various options and the necessary
input for each. Some options are grouped together here because of their
similarity.
First READ THE INSTRUCTION SCREENS then follow the instructions to begin
the configuration.
Maximum allowable log size - Input a number. The limits are enforced by the
program. Entering a negative number indicates no logging at all.
Reboot after viral detection - A simple Yes/No option. If you run in any kind
of multi-tasking environment it is strongly recommended that you select
"No". This option is available only for the DOS version and the actual
rebooting is performed using the FOSSIL driver.
Pass without testing - If you wish THDPRO.EXE to pass large files without
actually testing them, then select one of the four options provided.
Pressing any key other than those options shown will cause THDPRO.EXE to
test all files regardless of their size.
Drop carrier on Virus uploaders - A simple Yes/No option. If you wish to drop
carrier (hang up) on people who upload files which failed the virus scan
select "Yes" otherwise select "No". This option is available only for the
DOS version and the carrier dropping is performed using the FOSSIL
driver.
Com Port - If you choose, you can set a default comport to be used by
THDPRO.EXE on every run. Normally, I recommend that the comport be
supplied on the command line, but if you'll always use the same comport,
and it is a port between 1 and 8, you can enter it here. Entering "0"
selects no comport by default.
Local Com Port - In almost all cases this should be set to "0". If you think
you might need to set it to something else, hit the "F1" hey for help.
Bulletin Board Name - This entry is required. When you register THD ProScan,
this is the name which the program will present itself as being
"Registered to:".
Log Directory - Enter the full path to a directory in which to keep
THDPRO.EXE's log files. This directory MUST already exist.
BBS Type - If you are running a BBS AND you wish THD to update your BBS file
bases, you must select the appropriate BBS type here. Selecting "None"
will cause THDPRO.EXE to make no attempt to store information for the
purpose of modifying your file databases. If your BBS type is not
'explicitly' supported and shown on this screen, then select none. The
"other" option is for use with third party programmers. Select this
option ONLY is instructed to do so by the manufacturer of that third
party software.
- Once you have selected a BBS type, you may be sent to another selection
screen to select a version.
- You may also be required to enter the path to your BBS directory.
Age / Date Limitation - If you wish THDPRO.EXE to fail files because they are
too old, you can select to limit acceptance by either the date of files
INSIDE the archive or by the age of the file INSIDE the archive. The date
the archive was last modified is not import in this consideration.
- If you select to limit by AGE you are then asked to choose if you wish
to limit files by their age in Days, months or years. After you select
the appropriate limiter, you will be asked how many days/months/years
to limit it to. Each entry has it's own maximum limit which can be
entered.
- If you select to limit file by DATE, you will then be prompted to enter
the year, month and day at which to limit the acceptance.
Limit testing time - This time limit affects ONLY the time required to expand
files. Normally a reasonable limit like 2 minutes would be more than
sufficient to expand legitimate files. This limit is not absolute.
Testing for exceeding the limit is done after each file has been
expanded. An entry of 0 means no limit.
Space usage limit - This specifies the free space which must be left on the
hard drive to continue performing the testing. It is checked after
expansion of each archive. If less space than is entered here is available
then the file will fail. An entry of 0 disables this limit.
Free Space Limit - This specifies that THD must always leave a specific number
of bytes free on the testing drive. As with the above limits it is tested
after each file is expanded. If space drops below the accepted limit the
file is failed. an entry of 0 means no limit.
Ansi Detection time - This option allows you to determine the amount of time
THD spends attempting to detect ANSI support on the remote system. The
default is 5 seconds. Normally you would never alter this. however if you
have some users who cannot be detected in the default amount of time, you
may wish to increase the time allowed for this detection.
Date format - Select from the available options the date format which suits
you best.
Do you wish to use/test.... - This question is asked numerous times in
relation to various things. If you wish to use the product specified or
test the file type specified. Answer "Yes", otherwise answer "No".
Heuristic failures - If you have opted to use one of the Heuristic scanners
you will be asked if you wish files which fail heuristic analysis to be
considered virus infected or if the details should simply be logged.
Enter the full path... - Again you will be asked numerous time to supply path
information (usually whenever you select "Yes" to one of the use/test/
options). Enter the path (and filename if necessary) as outlined in the
screen instructions and hit the enter key to complete the input.
VENDINFO description size - Select the size of the description to be used for
BBS updates and optionally in comment headers. Normally I recommend the
450 size unless your BBS accepts long descriptions.
File comment - This screen asks you if you wish to supply a file to be used as
a comment of all files or if you wish to supply a filename to be used as
a random selection list. Hitting "ENTER" Causes THD to not insert a
comment at all. Either of the other two options will prompt you to enter
a full path and filename to the file to be used.
Drive selection - THD detects the drives which are available to it and lists
the first three here. THD will use these drives to test files by
searching for enough available free space on one of them (in order). You
can remove a drive from this list by entering its letter. You can
re-order the drives shown by pressing 1 or 2. If you're unsure, you can
hit enter to accept the default and change it later if it causes
problems.
File removal - You can select to remove files by supplying a few filenames,
supplying a list of filenames, removal by CRC or by a combination of
names and CRCs. It might be a good idea to read FEATURES.DOC before
selecting.
Loaders - You can add files to each tested archive. If you wish to do so, then
enter here, the filename(s) to add to every tested archive (wildcards are
accepted).
Reject Directory - Enter the full path to a directory to which to move files
which fail the tests. Note that failed file moving can be turned off, but
this entry is required regardless. The directory entered must exist.
Dupe Checking file - THDPRO.EXE can skip testing files it has tested before.
In order to do this, it must keep a record of files it has already
tested. If you think you may want THD to skip files it has tested
previously, then select "Yes". The dupe checking is not automatic, it
must be specifically invoked.
Reject list (Hacklist) - If you wish to reject files from a list of files,
enter the full path to that file here. See FEATURES.DOC for a list of
acceptable file types.
Default options - you can set some options for THDPRO.EXE to use as defaults.
select "Yes" to modify the defaults. See FEATURES.DOC on how to override
these selection. Select "No" to skip setting default options.
Archive conversion levels - You can select to view and/or modify existing user
conversion levels. If you wish to do so select "Yes".
THREE FINAL SCREENS
-------------------
In the three final screens of the installation you are shown your
selected options and some options which have not yet been covered.
Screen one - Shows only the state of options which have been configured to
this point. to modify an existing option, select its corresponding letter.
Hit ENTER to move to the next screen.
Screen two - Shows path to files which you have entered. If you wish to modify
any of the options enter their corresponding letter. Hitting ENTER goes to
the next screen. Hitting "1" goes back to the first final screen.
Screen three - Contains a number of options which have already been configured
and a few that haven't. Select the corresponding letter to modify an
entry. Press "1" to return to screen one or "2" to return to screen two.
Hitting "ENTER" accepts the entries and ends the configuration.
-On this screen the following options have not been seen prior to this.
G-- File's Timestamp - this option determines if the time stamp of files
after they have been tested should be modified. By selecting "G" from
this screen you can toggle between the following values.
- Update to current date and time.
- Use File's upload date and time.
- "Best Guess" at original date and time.
- Use date of newest internal file.
H-- Failed File moving - This option determines if THDPRO.EXE should move
files to the directory specified for failed files if they fail the
tests.
Selecting "H" toggles between "ACTIVE" and "INACTIVE".
O-- Secure Mode - Turn secure mode on or off.
Hit "O" to toggle between "TRUE" and "FALSE".
(See FEATURES.DOC for details).
------------------
- Archive Editor -
------------------
The archive editor (formerly THDEXARC.EXE) is used to add or modify
external archive definitions and external scanner definitions. This function
of the program creates or manipulates a data file called THDEXARC.DAT. If
this file is present in the same directory as THDPRO.EXE then THDPRO.EXE will
extract the information and use it to control the possible additional archive
or scanner usage.
As soon as you select the Archive editor you will be taken to the list
screen. If THDEXARC.DAT exists in the current directory then this screen will
contain a list of the additional scanners and/or archivers, otherwise it will
have a title bar and lower instruction bar.
Pressing F1 from this screen will invoke the following help screen...
╔══════════════════════════════════════════════════════════════════════════╗
║ <Up Arrow> - Go up one entry ║
║ <Down Arrow> - Go down one entry ║
║ <Home> - Go to the first entry on the screen ║
║ <End> - Go to the last entry on the screen ║
║ <Page Up> - Page up 23 entries ║
║ <Page Down> - Page down 23 entries ║
║ <CTRL><Page Up> - Go to the very first entry ║
║ <CTRL><Page Down> - Go to the very last entry ║
║ <ENTER> - Edit/View the currently highlighted entry ║
║ <ESC> - Exit the editor (and save) ║
║ <INS> - Insert (add another entry) ║
║ <DEL> - Delete highlighted entry ║
║ I - Import definition(s) from a text file ║
║ E - Export definitions(s) to a text file ║
║ S - "S"earch for text (starts at first entry) ║
║ N - Find the "N"ext occurrence of the text last searched ║
║ F1 - Show this help screen. ║
║ F10 - Sort and Save the current changes to file. ║
╚══════════════════════════════════════════════════════════════════════════╝
The movement keys (up, down etc.) will not be explained here. A
description of the rest of the commands follows.
<ENTER> - Edit/View the currently highlighted entry
- Hitting the ENTER key will move you to edit mode with the current
scanner or archive definition. If the definition is blank you will be
moved to the SCANNER definition screen (see a later section for
changing to the ARCHIVER definition screen).
<ESC> - Exit the editor (and save)
- Exits the Archive Editor and saves any unsaved changes.
<INS> - Insert (add another entry)
- Hitting the INSert key takes you into the SCANNER definition screen
with a blank definition. Note that due to required sorting for some
definitions it is possible that the newly defined definition will not
be placed in the location where the highlight bar was when you pressed
the INSert key.
<DEL> - Delete highlighted entry
- Permanently removes the highlighted definition.
I - Import definition(s) from a text file
- This option will prompt you to enter the full path and filename of an
existing "EXPORT" file as created by the archive editor (or prior
versions of THDEXARC). Once done the program will open the file and
move you to a selection screen strongly resembling the opening screen.
See the later section on importing definitions.
E - Export definitions(s) to a text file
- This option can create or append to a file the "EXPORT" definition for
the currently highlighted entry. Useful for sharing definitions with
others or saving them for possible later importation.
S - "S"earch for text (starts at first entry)
- Search for text. All fields of all records are searched. You will be
prompted to enter the text to search for (searches are not case
sensitive). Stops at the first occurrence of the test searched. Note
that the text searched may not necessarily be visible from the list
screen, but the text was found in the record.
N - Find the "N"ext occurrence of the text last searched
- Searches for the "next" occurrence of the last text searched. Reacts
the same as the search command except that it starts at the current
highlight position and does not prompt you to enter text.
F1 - Show this help screen.
F10 - Sort and Save the current changes to file.
- Sorts the existing records to be saved in the THDEXARC.DAT file
(required for proper operation) and saves the changes to disk.
It's purpose is to allow the user to add external archive and virus
scanner support to THD ProScan, by creating a data file with necessary
information for THDPRO.EXE to use these external archives and/or virus
scanners in it's normal running.
Definitions found in THDEXARC.DAT (created by this utility) will only be
used IF THDEXARC.DAT exists in the same directory as THDPRO.EXE and IF the
archive type is not supported internally to THDPRO.EXE. An archive type
"normally" supported by THDPRO.EXE which is not configured in the
installation/configuration portion of THDCFG.EXE will be considered unsupported
for this definition and will be checked against the types supported in
THDEXARC.DAT. If however they are configured in THDCFG, the internal routines
will be used.
Conversion "to" external archive types is supported by THDPRO.EXE ONLY in
the registered version. Conversion from these type to types supported
internally by THDPRO.EXE is supported in registered and unregistered mode.
In the case of virus scanners, no comparison to internally configured
scanners is made, so you can opt to run the internally supported scanners via
this option with different parameters than set internally without a conflict
arising with those internal to THDPRO.EXE.
KEYWORDS (replaceable strings if you prefer) are as simple as the following...
~~A - use "A"rchiver instead of unarchiver
~~U - use "U"narchiver instead of archiver
~~F - "F"ilename for the current process
~~I - "I"nclude filenames or other relevant information.
~~D - "D"irectory
~~L - "L"og file (for scanners only)
If any of the above is entered in lower case they will be translated to upper
case prior to saving the record.
The ~~A and ~~U are special keywords in that they are not actually
"replaced" on the command line. Instead they are simply stripped from the
command line and the archiver (~~A) or unarchiver (~~U) is used instead of the
default. In order to understand this, you must realize that each of the
archive processes has a default executable.
In the case of the "test archive" command for instance, THDPRO.EXE will
use the "path to unarchiver" by default. If for some reason THDPRO.EXE should
be required to use the archiver (instead of the unarchiver) you could put ~~A
on the parameter line to tell THDPRO.EXE to use the "path to archiver" instead
of the "path to unarchiver". Putting ~~A in a parameter which normally uses
the Archiver will have no adverse effects (except to take up a few spaces in
your configurable space)
The other codes are replaced at run-time by THDPRO.EXE based on the
following. Codes not explained in any given entry are not supported for that
entry and have no translation value.
IN THE SCANNER CONFIGURATION
----------------------------
Path to Scanner - None
Scan a directory - ~~D=name of the Directory to scan (no ending "\")
~~L=full path and filename of "heurist.Log"
(or more accurately the temporary heuristic Log)
Scan a file - ~~F=full path and filename of the File to be
scanned.
~~L=full path and filename of "heurist.Log"
(or more accurately the temporary heuristic Log)
Success Errorlevel - None
IN THE ARCHIVE CONFIGURATION
----------------------------
Archive Type - None
Archive extension - None
Internal/External - None
Archive ID (hex) - None
Archive ID (chr) - None
Archive ID Offset - None
Path to Archiver - None
Path to Unarchiver - None
Expansion - ~~F=full path and filename of the archive to be expanded
~~D=Current temporary directory used by THDPRO.EXE
~~A=Path to Archiver (use only if you wish the
archiver to be used for this process instead of
the unarchiver. If absent the unarchiver is used).
** Note that an entry of "N/A" (without the quotes) in
this field will cause THDPRO.EXE to skip all aspects
of processing except the "test" for this file type
(new as of THD ProScan Version 12.2)
Compression - ~~F=full path and filename of the archive to be created
~~D=Current temporary directory used by THDPRO.EXE
~~U=Path to Unarchiver (use only if you wish the
Unarchiver to be used for this process instead of
the archiver. If absent the archiver is used).
Add a file - ~~F=full path and filename of the archive being tested
~~I=full path and filename of the file(s) to be added
~~U=Path to Unarchiver (use only if you wish the
Unarchiver to be used for this process instead of
the archiver. If absent the archiver is used).
Add a comment - ~~F=full path and filename of the archive being tested
~~I=full path and filename of the comment to be added
~~U=Path to Unarchiver (use only if you wish the
Unarchiver to be used for this process instead of
the archiver. If absent the archiver is used).
Test archive - ~~F=full path and filename of the archive being tested
~~I=No replacement values (will be left untouched)
~~A=Path to Archiver (use only if you wish the
archiver to be used for this process instead of
the unarchiver. If absent the unarchiver is used).
Delete by list - ~~F=full path and filename of the archive being tested
~~I=full path and filename of the list to be removed
~~U=Path to Unarchiver (use only if you wish the
Unarchiver to be used for this process instead of
the archiver. If absent the archiver is used).
Delete by filename - ~~F=full path and filename of the archive being tested
~~I=full path and filename of the file(s) to be removed
~~U=Path to Unarchiver (use only if you wish the
Unarchiver to be used for this process instead of
the archiver. If absent the archiver is used).
Success Errorlevel - none
The Menu Interface
------------------
The menu interface is "basic" meaning that it supports the up/down arrow
keys as well as the use of the highlighted "Hot Keys". <enter> selects the
highlighted option. <esc> is equivalent to the "Quit" option on each menu.
To select an option move the highlight by pressing the up and down arrow
keys and press the <enter> key when the correct option is highlighted. Or
press the highlighted letter of your selection.
Except as noted below the home key will move the highlight to the first
selection on the menu and the end key will move the highlight to the last
selection.
The menu commands will not be broken down in this text. Anyone incapable
of understanding the meanings of the various menu options should seriously
reconsider before trying to add or manipulate external archives or scanners.
IMPORT - EXPORT
---------------
The "Import" option available from list mode allows the user to "import"
definitions from a text file. This text file must contain a definition in the
precise format created by the "export" function (discussed in the next
paragraph) except that it will ignore any leading and/or trailing spaces. This
will allow easy importation of other's settings. The text imported "from" can
contain as many definitions as you like and may also contain information other
than the definitions (THDEXARC will search for the definition portions and
offer you the option to import each definition as it is found).
The "Export" option available from list mode will prompt you to export the
currently displayed archiver or scanner or to export "all" records. If you
select the "all" option then all scanner AND archive definitions will be
exported regardless of which you are viewing. The export file is a simple text
file and can be edited without destroying the effectiveness as long as no
lines which are "used" are removed completely.
Both of these options will prompt you to enter a filename with the
"default" being THDEXARC.EXP. You may supply another filename and/or a full
path and filename at your option. If the file exists on an export attempt you
will be asked if you wish to "overwrite" (replace the existing file), "append"
(add the new info to the end of the existing file) or "abort" (stop
exportation).
THDEXARC.EXP
------------
Included in the distribution archive is THDEXARC.EXP. This is a text file
which contains the "Export" of some archivers and scanners. You can Import the
various definitions via the Import function from the main menu. It is
distributed in this format to avoid having THDPRO.EXE use THDEXARC.DAT unless
it has been specifically configured.
Note that the various Paths supplied in this file are not likely to exist
on your system and will almost certainly need to be corrected. This can be
done with a text editor or inside THDCFG.EXE at the time of importation.
Import only those definitions that you wish to use and/or add your own.
However please take great care when using this utility. I cannot stress how
little control you may have if you're not fully aware of the capabilities of
the archivers or scanners that can be configured through it's use. Archiver
definitions which are marked "INTERNAL" represent no greater risk factor since
they use the utilities and command lines configured within THDPRO.EXE. These
definitions simply alter the place where THDPRO.EXE searches for the
signature.
*********************************
* UNDER "ARCHIVE" CONFIGURATION *
*********************************
--------------
Archive Type -
--------------
The Name and version of the Archiver/Unarchiver who's action this entry is
designed to account for (ie. PKZIP/PKUNZIP version 2.04g).
--------------------
Archive extension -
--------------------
The "normal" extension of the archive type (ZIP for Zip, LZH for Lha etc)
[ capital letters are forced ]
-------------------
Internal/External -
-------------------
This entry is a toggle. Selecting it toggles support from External (use the
info in the THDEXARC file) to Internal (use THDPRO.EXE's internal
identification and handling routines).
IN ALMOST ALL CASES THIS SHOULD BE SET TO EXTERNAL!!!
This will signify that you are defining an archive type not supported by
THDPRO.EXE.
The setting of INTERNAL is a special case which tells THDPRO.EXE, that the
archive type is already support internally but the search for the
Identification needs to be adjusted by the number in ID_OFFSET in order for
THDPRO.EXE to properly identify the archive type.
In order to understand how this might be used, see the "Internal Support"
notes at the end of this document.
------------------
Archive ID (hex) -
Archive ID (chr) -
------------------
Either of these will allow you to "input" archive identification characters
in HEXADECIMAL format (00-FF). These can usually be seen in a hex editor or
other hexadecimal viewer. The "?" is a reserved character and may NOT be used
in the archive id (hex 3F). The ? is used to indicate that a character in
"this" position may be any character. PKZIP for instance might be entered as
50,4B,03,04,??,??,??,??,??,??,??,??,??,??,??. Which is translated into.. Only
the first four characters are significant and they must be 50,4B,03,04 IN THAT
ORDER. The "hex" entry is where input is made, the "chr" entry is for display
purposes only and will show the actual character represented by the hex code
entered.
LHA archives could be identified here as...
2D,6C,68,??,2D,??,??,??,??,??,??,??,??,??,??
which would require a match for the first three and fifth character while
allowing the fourth character to be anything. (The Id offset for this pattern
in LHA archives is at position "2")
In cases where it would be easier to enter the actual character than it's
"hex" equivalent, you may do this by entering it with a preceding "=". So for
PKZIP for instance one could alternately enter it as...
=P,=K,03,04,??,??,??,??,??,??,??,??,??,??,??.
The "=" tells the interpreter that the second character is the actual
character to be entered and it in turn "translates" that character into it's
appropriate hex code. So entering "=P" would result in "50" showing in the
space where that was entered (as "50" is the hex equivalent of a capital "P").
The "P" itself would be displayed on the (chr) line below. This works for all
"typable" characters.
-------------------
Archive ID Offset -
-------------------
Number of bytes from the beginning of the archive at which the Archive ID
is located. The "first" byte of the archive is "0" (not 1). Thus "ZIP"
archives with the above signature would have an offset of "0".
------------------
Path to Archiver -
------------------
The full path and filename of the archiver (ie C:\TOOLS\PKZIP.EXE). This
entry MUST represent a full path and filename (drive preferred but not
required) [ capital letters are forced ]
--------------------
Path to Unarchiver -
--------------------
The full path and filename of the UNarchiver (ie C:\TOOLS\PKUNZIP.EXE).
This entry MUST represent a full path and filename (drive preferred but not
required). An entry of "=" will cause it to match the "Path to Archiver" entry
above. [ capital letters are forced ]
-----------
Expansion -
-----------
The parameters required by the UNARCHIVER to expand an archive of this
type for PKZIP for instance, one might enter "-d -o- ~~F" (meaning to recreate
directories and never overwrite existing files)
To avoid running expansion and compression commands in THDPRO.EXE (v12.2
or later) set this field to "N/A" (without the quotes). This will tell
THDPRO.EXE that this entry is for "testing only" (like GIFTEST) and there is
no appropriate command to expand or compress files using this utility.
-------------
Compression -
-------------
Supported only in the registered version of THDPRO.EXE, this field should
be defined as the parameters necessary for the ARCHIVER to create an archive
including all subdirectories which may be under it. . For PKZIP, one might use
"-arp ~~F"
If this action is not applicable set to "N/A" (see above under Expansion)
------------
Add a file -
------------
Parameters used to "add a file" to this particular archive. The "archiver"
is normally used for this purpose. For PKZIP you might use "-a ~~F ~~I".
---------------
Add a comment -
---------------
The parameters required by the Archiver to add an archive comment. For
PKZIP one might use "-a ~~F -z > ~~I"
--------------
Test archive -
--------------
The parameters used by the Unarchiver to "test" the CRC of an archive. For
PKZIP "-t ~~F".
----------------
Delete by list -
----------------
The parameters required by the Archiver to delete files via a list where
~~F will be replaced by the full path and name of the archive and ~~I will be
replaced by the full path and filename of the "list". For PKZIP "-d ~~F @~~I"
--------------------
Delete by filename -
--------------------
The parameters required by the Archiver to delete files BY NAME where ~~F
will be replaced by the full path and name of the archive and ~~I will be
replaced by the filename(s) of the file(s) to be removed.
For PKZIP "-d ~~F ~~I"
--------------------
Success Errorlevel -
--------------------
The errorlevel returned when the various command lines have encountered
no errors in their execution (usually "0"). Note that THDPRO.EXE evaluates
this errorlevel in the same way as "DOS". An errorlevel less than or equal
to the value entered here is considered a "pass".
*********************************
* UNDER "SCANNER" CONFIGURATION *
*********************************
---------
Scanner -
---------
The Name and Version of the scanner represented by this entry. For example
"McAfee's VirusScan Version 2.2.5."
-----------------
Path to Scanner -
-----------------
The full path and filename of the Virus Scanner (ie C:\SCAN\SCAN.EXE). This
entry MUST represent a full path and filename (drive preferred but not
required) [ capital letters are forced ]
------------------
Scan a directory -
------------------
The parameters required to scan all files in a directory and all of it's
subdirectories. for Mcafee's SCAN you might use "/all /sub /nomem ~~D\*.*".
-------------
Scan a file -
-------------
The parameters required to scan a single file. for Mcafee's SCAN you might
use "/all /nomem ~~F".
--------------------
Success Errorlevel -
--------------------
The errorlevel returned when no viruses are found. (usually "0") Note that
THDPRO.EXE evaluates this errorlevel in the same way as "DOS". An errorlevel
less than or equal to the value entered here is considered a "pass".
Notes -
Prior to saving any records, This program records the CRC of the
executable file(s) of the record for use by the SECURE mode of THDPRO.EXE. The
time required to do this will vary depending on the size of the executables.
If running THDPRO.EXE in secure mode, the CRC's above can be "corrected"
by "edit"ing the path to any one of the executable files of the record in
question. This will cause the CRC's to be recalculated for the executables
in that record. Running THDPRO.EXE /SEC has no effect on the THDEXARC CRC
records and will not correct the CRC's stored therein. Note however that none
of these CRC's should change unless you have changed the file that they point
to. You should be EXTREMELY suspicious if you find yourself needing to
correct a CRC contained in the THDEXARC.DAT file if you have not changed
the file(s) affected.
All archive records are sorted upon exit from the program in reverse order
based on the archive identification strings. The sorting is required to ensure
that THDPRO.EXE attempts archive identification in the correct order. No
"sorting" of scanner entries is necessary.
------------------
Internal Support -
------------------
In order to understand when one might set the Internal/External toggle on
an archive type to "INTERNAL" one needs to understand how THD looks for it's
archive identification internally as well as what THD looks for. Under all
"normal" circumstances, THD looks for the archive identification at offset "0"
in any given archive type ("2" for LHA).
When looking at SFX files THD reads the executable header for the "size" of
the executable header and changes its starting point by that amount. This
works fine for DOS SFX files since the actual archive is simply appended to an
executable file. However OS/2 and Windows have a different executable
structure and the "size" THD finds can simply be the size the the "dos stub".
This stub is then followed by a portion of code specific to OS/2 or Windows.
(Some OS/2 SFX types do return the proper size and do not need to be accounted
for by this method.)
THDPRO.EXE would thus not be able to identify that file as an archive as it
would be searching for the ID in the OS/2 or Win executable portion instead of
the archive. What is needed is a way to tell THDPRO.EXE to "skip" a specific
number of bytes to locate the id header.
When setting an archive type to INTERNAL, most fields are ignored. The
only "significant" field in the record is the ID_OFFSET. THD will (if it fails
to recognize the archive internally) check again beginning with the id_offset
as specified in any internal THDEXARC entries. It will restart a new internal
search using the offset provided by THDEXARC and defining the archive as
whichever internal identification it matches. If it matches none of the
internal archive types, it is defined as an unrecognized type.
A sample of this type of use is included in THDEXARC.EXP, and I may be
happy to help those who may need it for other purposes (although I may require
you to send me the archiver or possibly a few sample archives of the type
which needs to be defined). I have accounted for the RAR occurrences of this
type. The [OS/2] LH and ZIP SFX formats I tested do not need to be accounted
for as they both returned the correct size and are recognized by THDPRO.EXE
without this consideration.
It is important to remember that "internal" means internal to THDPRO.EXE.
Those types defined as "internal" will NOT be compared to any other records
stored in the THDEXARC.DAT file and therefore will ONLY work if THDINSTL.EXE
has been configured to use the particular archiver you intend to support using
this method. If the archiver is NOT configured internally, then make the
definition an external one and fill in all necessary fields.
If in doubt, ask. This option is not for the average user.
-------------------
- Language Editor -
-------------------
Finally, THD ProScan comes with a language file. And as with any good
language file, you need a way to edit the strings it uses. Since there are
some restrictions on the strings used by THDPRO.EXE, it seemed only logical to
make an editor rather than putting the strings in a plain text file (it's also
faster to access than a plain text file). The editor itself is designed to
help you avoid entering invalid strings, although it makes no judgement of the
actual text in the strings.
It is important to note that this editor will ONLY work with the
registered version of THD ProScan's language files. Attempting to edit the
freeware version's language file with this utility will either not work or
corrupt the language file.
Upon selecting the language editor from the main menu, you will be
prompted to enter a filename (default is LANGUAGE.THD). After entering the
filename and hitting the ENTER key the following will occur...
If the specified language file does not exist in the current directory,
you will be asked if you wish to create it. If you select to create it a new
file of that name will be created containing all of the default strings from
the default language (the default language is stored internally to THDCFG.EXE
and is not taken from any existing language file).
If you wish to base your changes on a file you've already edited, you
should "copy" that already modified file to the filename of your choice before
running THDCFG.EXE.
It is important to note that in order for the language editor to run, the
file LANGUAGE.IDX must exist in the same directory as THDCFG.EXE.
THDPRO.EXE basically has 6 usages for strings.
1) They can be used in the log file created by THDPRO.EXE. Strings used for
this purpose can be up to 255 characters but a carriage return must be
inserted every 72 characters or less.
2) They can be used on the sysop's view in the upper left corner to explain
THDPRO.EXE's current action. These strings can be up to 255 characters but
must contain a carriage return every 36 characters or less.
3) They may be used in the ANSI output for the remote and/or in the upper
right sysop window. Strings used here are limited to their space in the
ansi ("usually" 14 characters maximum with NO carriage returns). In most
cases these strings "must" be a specific length to properly display. In
these cases, the program will add spaces when necessary to pad the string
to it's required length)
4) They can be used in THDPRO.EXE's Warning Descriptions. Warning Descriptions
are short messages inserted instead of (or in addition to) the proper
description when files fail testing for a number of reasons. These strings
must be one line not exceeding 45 characters.
5) They can be used in the lower half of sysop output screen. These strings
are limited to 255 characters and must contain a carriage return every 78
characters or less.
6) They can be used for NON-ANSI output to the remote. These strings usually
are limited in the same fashion as a log entry.
In the case where a given string is used in more than one of these places,
the limitations for that string will be based upon the most restricted of the
types for which it is used. Note also that some strings are used in
conjunction with others and you may need to account for that when deciding on
the text to modify. In addition to this, certain strings have conditions other
than determined by the above conditions. These "other" conditions will be
enforced when applicable by the editor.
String number 91 ("Unknown") is not used in any of the places defined for
string usage, but is included with in the language file. It is used in THD's
COMMENT when file date or time are not known. Otherwise all strings are used
in one of the six instances explained above.
Once started, THDCFG will load either the selected language file or the
default file (depending on the conditions above). You will be presented with a
rather boring screen filled with various strings (one per line). If any string
should exceed 80 characters, only the first 80 characters will be shown on the
line.
The following keys function from this screen...
<Up Arrow> - Go up one string
<Down Arrow> - Go down one string
<Home> - Go to the first string on the screen
<End> - Go to the last string on the screen
<Page Up> - Page up 23 strings
<Page Down> - Page down 23 strings
<CTRL><Page Up> - Go to the very first string
<CTRL><Page Down> - Go to the very last string
<ENTER> - Edit the currently highlighted string
<ESC> - Exit the editor (prompts for saving)
S - "S"earch for text (starts at first string)
N - Find the "N"ext occurrence of the text last search
R - "R"estore the default string.
V - "V"iew the usage of the highlighted string.
F1 - Show this help screen.
F10 - Save the current changes to file.
Each of the keys actions is defined below.
<Up Arrow>
Pressing the UP arrow will cause the highlighted entry to go "up" (physically)
by one string (scrolling the screen if necessary). In effect it decreases the
"number" of the highlighted string. Pressing it from the first string will
have no effect.
<Down Arrow>
Pressing the DOWN arrow will cause the highlighted entry to go "down"
(physically) by one string (scrolling the screen if necessary). In effect it
increases the "number" of the highlighted string. Pressing it from the last
string will have no effect.
<Home>
Pressing the HOME key will cause the highlight to move to the first entry
visible on the screen.
<End>
Pressing the END key will cause the highlight to move to the last entry
visible on the screen.
<Page Up>
Pressing the PAGE UP key will cause the screen to scroll "up" 23 entries (one
screen worth of entries). If the currently highlighted string is one of the
first 23 strings, then this will cause it to highlight the first string in the
language file.
<Page Down>
Pressing the PAGE DOWN key will cause the screen to scroll "down" 23 entries
(one screen worth of entries). If the currently highlighted string is one of
the last 23 strings, then this will cause it to highlight the final string in
the language file.
<CTRL><Page Up>
Holding the CTRL key while pressing the PAGE UP key will cause the highlight
to move to the first string in the language file (changing the screen if
necessary).
<CTRL><Page Down>
Holding the CTRL key while pressing the PAGE DOWN key will cause the highlight
to move to the last string in the language file (changing the screen if
necessary).
<ENTER>
Pressing the ENTER key will enter View Mode followed immediately by Edit mode
(described in detail later in this text).
<ESC>
Pressing the ESC key causes the program to exit to the main menu. Prior to
exiting you will be prompted to save the language file in it's current state
(regardless of whether or not any editing has actually taken place).
S
Pressing the S key will display a small dialogue box which prompts you to
enter a text string to search for. If a search has previously been done, the
edit box will contain the last string searched. Edit the current string or
enter a new string. Press enter after entering the string to begin the search.
Note that any search is NOT case sensitive (ThD matches thd). A search started
this way "always" starts with string number 1 (the first string in the
language file). If a match is found the highlight will be moved to the string
which contains the match. Otherwise you will be informed that the string was
not found.
N
Pressing the N key will repeat the search of the last string searched
beginning at the current position in the language file. If an occurrence of
the last string searched is found between your current position and the end of
the language file, then the highlight is moved to the match. Otherwise you
will be informed that there was no match.
R
Pressing the R key will replace the currently highlighted string with the
default entry. This is the value it would be given if the program had created
the language file and is NOT necessarily any previous definition the string
may have had. This process is irreversible except by manual editing (although
changes made this way are not saved until you opt to save the changes).
V
Pressing the V key will enter "VIEW" mode, which is described in detail later
in this text. This is the same as the output shown just prior to entering Edit
mode, except that on completion you are returned to LIST mode rather than
entering EDIT mode.
F1
Pressing the F1 function key displays the help screen shown above (with the
key list and a brief explanation of their actions).
F10
Pressing the F10 function key causes a dialogue box to appear prompting you to
save the current changes to disk. If you select yes all current changes are
saved to the active language file. There is no reversing this step except by
manually editing to reverse the saved changes.
Immediately following the introduction screen, LIST mode is started, which
is basically the screen on which a list of strings is presented with one
string highlighted and the above keys active. There are two other "modes".
They are VIEW mode and EDIT mode. VIEW mode is entered by pressing the V key
as described above or by pressing ENTER as described above.
If you enter VIEW mode by pressing V then upon completion you will be
returned to LIST mode. If however you enter VIEW mode by pressing ENTER then
EDIT mode will be entered upon completion of VIEW mode.
VIEW MODE
---------
View Mode is entered as described above by pressing the V or ENTER key
from LIST mode. View mode starts by giving a brief description of where and
how the last highlighted string is used in THDPRO.EXE. Once you have read the
explanation press a key to advance to a sample usage screen.
The sample screen attempts to show you where the string will be used in a
practical manner. If the string is displayed in the sysop view then a screen
similar to the THDPRO.EXE sysop view is displayed with the string highlighted
according to the following rules. If the string is used in the ANSI GRAPHIC
portion then it is displayed as bright white text on a black background with a
yellow ">" preceding it and a yellow "<" following it. This is done because
these strings are length sensitive and any string entered will fill all spaces
between those two symbols. If the string is displayed anywhere else, it is
shown in yellow to distinguish it from other filler/sample text. Often other
text is included to show the context of the current string (referred to above
as filler/sample text). The filler/sample text is almost always displayed in
blue.
Generally speaking the text can show up in two places aside from the ANSI
GRAPHIC portion. These places are in the upper left (under the big grey THD)
or in the lower half of the screen.
Text which is shown under the big THD is actually displayed there during
the running of THDPRO.EXE either in the sysop view or on the remote view
("almost" always in the sysop view).
Text shown below the separation line can be destined for one of four
places. If no purpose is stated in red, then the line(s) displayed is/are
shown by THDPRO.EXE in the lower portion as displayed.
Text which is displayed in the LOG file is shown with a red "Log - " on
the line preceding the sample log entry, and text destined for remote output
is shown with a red "Remote -" prior to the text. In some cases a language
string is used for both purposes and is shown as "Log and Remote -" (since the
restrictions on LOG and Remote output are the same the string is only
displayed once for both contexts).
The fourth type of entry shown in the lower portion is the THDPRO.EXE
Warning Description. This is the description THDPRO.EXE will use to update the
file bases of some supported BBSes when a failure occurs. These string are
"almost" always shown in conjunction with other strings to retain some context
as to their complete message. these descriptions will always be shown with a
red "Warning Description -" on the line preceding the description text.
Note that the THD ANSI GRAPHIC is only displayed in the upper portion if
it is actually needed for display purposes and VIEWing "some" language strings
will not require this to be displayed. For the sake of consistency the strings
described above as being shown in the lower portion of the screen are shown
there even if the GRAPHIC portion is not displayed.
EDIT MODE
---------
Once you have pressed ENTER from LIST mode, you will be sent to VIEW mode
as explained above and thereafter EDIT mode will begin. The last highlighted
string will be made available to edit in a box. The dimensions of that box are
predefined according to the restrictions placed on the use for that string. In
most cases you will be presented with a multi-line edit box (although some
strings will be a single line). Regardless of whether there is one line
available to edit or 10, the procedure of editing is basically the same.
In the editor box, the following keys are active. All ASCII keys, ENTER,
<UP ARROW>, <DOWN ARROW>, <LEFT ARROW>, <RIGHT ARROW>, <HOME>, <END>,
<CTRL><LEFT ARROW>, <CTRL><RIGHT ARROW>, <ESC>, <INS>, <DEL> and <BACKSPACE>
(other keys not mentioned here "may" also be active).
To edit the current line, you must move the cursor off of the first
character. Failure to do this will cause the line to be completely removed and
the text you enter to begin without any of the previously visible text
available for editing. If you wish to replace the string currently shown
simply start typing.
The Keys in the editor have the following functions
All ASCII keys - Cause their corresponding character to be inserted or
entered at the current cursor position.
<UP ARROW> - Completes input for the current line and moves up one line in the
edit window (if possible).
<DOWN ARROW> - Completes input for the current line and moves down one line in
the edit window (if possible). If it is not possible to move down one
line, then input is treated as if enter had been pressed and it is
assumed you have completed editing the current string.
<LEFT ARROW> - Moves the cursor to the left one character (if possible).
<RIGHT ARROW> - Moves the cursor to the right one character (if possible).
<HOME> - Moves the cursor to the first character on the line.
<END> - Moves the cursor to the space after the last character entered on the
current line.
<CTRL><LEFT ARROW> - Moves the cursor to the left to the beginning of the
current word or the beginning of the line (whichever applies).
<CTRL><RIGHT ARROW> - Moves the cursor to the right to the beginning of the
next word or the end of the line (whichever applies).
<ESC> - erases all characters on the current line. If all characters have
already been erased, then it completes the input for that line (and in
effect for the entire string).
<INS> - Toggles insert mode. INSERT is "off" at the start of editing each
line.
<DEL> - Deletes the character at the current cursor position.
<BACKSPACE> - Moves the cursor to the left (removing any existing character in
the newly occupied space).
<ENTER> - Completes input for the current line. If the current line is blank
or is the last editable line then it completes input for the entire
string.
other keys - no other keys are "specifically" assigned values. Some may cause
characters to be inserted or not, but this is not an intentional
effect.
Because THDPRO.EXE uses some of the strings in restricted spaces or in
more than one place, there may some restrictions on the string's length or
what it can contain.
VIEW mode will attempt to show you (or tell you) in what instances
the string will be used and EDIT mode will enforce the restrictions via the
available edit space in the box.
Where ever possible I have tried to account for all usages. Limits
regarding the number of lines or number of characters per line will be imposed
automatically by the edit window and will not show an "explanation".
The string may be edited using ASCII characters (there are no "replaceable"
strings or special codes). To complete the entering of a string, press the
<ENTER> key on any blank line or on the 10th line (or the last line available
to your particular editing window). The available space is updated at each
pressing of the <ENTER> key to show how many more characters may be added.
Pressing enter on a non-blank line completes the input for that line. The
editor automatically inserts a carriage return at the end of each edited line
(except for the last line of the string).
Strings may not contain any blank lines. If you press enter on a blank
line, you will complete the input for that string and the string portion saved
will be only up to (but not including) that blank line. Any text following a
blank line will be lost if you save the string.
The editor does NOT support word wrapping, so if your typing forces
characters off of the current edit line, they will be lost.
Also string number 99 (THD ProScan) is not editable. It is used in a
number of instances where no other string is logical (or allowed).
After editing any string you will be asked if you wish to save the string.
If you select "Y" to save the string it will be saved to a buffer in memory
and NOT directly into the language file. If you wish to save changes
permanently you will have that opportunity from the main screen where the F-10
function key will rewrite the language file with all current changes. If you
attempt to exit the editor with unsaved changes, you will be prompted to save
those changes prior to exiting.
Any time you're presented a Y/n option, pressing <ENTER> is the same as
pressing "Y" and pressing <ESC> is the same as pressing "N".
As changes are made to the language, it is "possible" that the memory
buffer may become full. If this occurs you will be asked if you wish to save
"all" current changes. If you select to save and continue, then the current
changes will be saved to the active language file, the internal buffer will be
cleared, and you may continue editing. If however you opt NOT to save the
changes, the edit session will be aborted with no saving of changes taking
place. Needless to say if you get this prompt you've made significant changes
and really "should" save them so as not to lose all of your efforts.
As of this version there are 292 modifiable and 2 unmodifiable strings
(the appropriate string number is displayed in the upper left corner while in
list mode), each of which has been accounted for in the sample usage chart
(VIEW mode). This should enable you to completely convert THDPRO.EXE's
language to any language you like although you may be limited by space in some
instances. And of course you are not allowed to modify the product
identification string. But otherwise, I would be interested if you are able to
send me any language files which are completely converted to a language other
than English.
Please keep in mind that while I have made an attempt to verify the usage
of every string in the language file, it's entirely possible that I missed an
instance where a strings restrictions "should" be more strict. If you find a
string not displaying properly, please inform me of the problem, so that I may
correct its restrictions in the next version of the language editor. In the
meantime, you should be able to insert carriage returns etc. until the output
looks acceptable. In the case of LOG entries, it might be advisable to note
where the log entries are preceded by a filename or file path, as when
combined with the filename (or path) the string may exceed the number of
characters available on your viewer. In such instances, it might be a good
idea to leave the first line of such strings a little shorter to allow a
reasonable length for the inclusion of the filename (or path).
And of course, most important of all, if you find a problem with the
editor or have suggestions, please let me know.
------------------
- ANSI Demo/Test -
------------------
Once selected from the main menu, you will be presented with another menu
with the following options...
Demo Only
View ANSI
Colour Test
Quit / Back
- Demo will show you a sample output as might be seen by your remote users
when they upload a file. This demo will use one of the three internal
ansi screens selected at random.
- The View ANSI option is used to preview your ansi with the THD test
screen. Use this to see if your ansi will be displayed correctly to the
remote users. You will be prompted to input a filename. THDCFG will load
the filename and display it locally in much the same manner as the remote
would see it. If the filename is PAINSOFT.AN? (where the ? is any
character), the file will be displayed as a PAINSOFT formatted file. Any
other filename will be displayed as a THDPRO file. The differences
between the two formats are discussed in THDPRO.DOC.
The program is purposely crippled to not properly display ansi which
exceeds 70 characters per line. This is to ensure that your ansi will
remain compatible with the majority of user's systems. If your ansi looks
fine through the demo, it will almost definitely be fine on the remote
end.
If the filename is not PAINSOFT.AN? then the demo will simply display the
ansi file and then go on with the demo using the internal screen (without
replacing the upper left corner).
If however the file is a PAINSOFT.AN? file then the demo will run through
the test in two runs. The first run goes through a simulated test where
everything passes (use this to ensure all of your pass indicators work),
and the second run goes through as if every test failed (use this to
ensure that all of your failed indicators work).
- Colour Test option will prompt you for the name of a file. That file must be
a PAINSOFT.AN? format file (See THDPRO.DOC). It will then display the
main body ANSI portion of the file. At this point you can press "F" to
change the "F"oreground of the THDPRO header (the top two lines) or "B"
to change the "B"ackground colour of the header. When you find a colour
combination that is acceptable, hit the <ESC> key to quit. The program
will display a line of text similar to "Foreground=7 Background=0". This
line can be inserted into the PAINSOFT.AN? file (see THDPRO.DOC for
particulars) to cause THDPRO.EXE to display the selected header colours
on the remote view when this file is used.
- Quit/Back returns you to the Main menu.
-----------------------
- THDTERM (configure) -
-----------------------
This option handles the configuration of THDTERM which was previously
built in to THDTERM.EXE.
Once you have selected this option you will be prompted to enter the path
to THDTERM.EXE. If THDTERM.EXE exists in the current directory press enter to
accept the default. Otherwise, supply the full path and filename and hit
ENTER.
THDCFG will then check the validity of the file and prompt you to enter
some information. You will be prompted to enter the path to THDPRO.EXE twice.
- Path to THDPRO.EXE
The first time you're prompted to enter a path to THDPRO.EXE, it will be
the copy of THDPRO.EXE to run if the program is run under DOS. The second time
you will be asked to enter the path of the copy of THDPRO.EXE to use when
running under OS/2. If you run in a single environment you can configure both
to the same file.
- Test Directory
You will be asked to enter a path to an EXISTING directory to be used as
the default test directory. This is the directory which THDTERM will test when
run without parameters.
- Pass Directory
You will be asked to enter a path to an EXISTING directory into which to
move files which pass testing by THDTERM.
- Fail Directory
You will be asked to enter a path to an EXISTING directory into which to
move files which fail testing by THDTERM.
- Final screen
From here, you can opt to modify the existing configuration. review the
setting, and modify them (if necessary) by selecting their corresponding
letter, or simply hit ENTER to accept all the values as shown.
---------------------
- Author / Register -
---------------------
This is where the action is. Yes.. this is where you get the information
on where to send your Registration fee. And yes this is where you can
INSTANTLY register the program.
Once you have selected this option, you will be shown the author contact
information and a prompt to hit "R" to register the program. If you wish to
send a registration fee then press "R", otherwise press any key to exit back
to the main menu.
Having decided to register you can press "R" to go to the Registration
information section. As soon as you do this, you will be presented with a menu
showing different geographical locations. It is IMPORTANT that you select the
geographical location which best suits where you reside. The reason for this
is that the author is NOT the "only" person who accept registrations, and if
you do not live in Canada the author wishes you to register with one of the
other two approved registration sites.
It is also important to note that promissory notes (cheques etc) should be
made payable as described by the appropriate registration screen and NOT to
the author unless specifically told to do so.
Once you have selected the CORRECT geographical location by using the
arrow keys and pressing "ENTER" you will be presented with the information for
registering from your location.
Once you have SENT your registration fee, you may press "R" to register
the program. Doing so registers the copy of THDPRO.EXE in the current
directory.
Person who have NOT sent their registration fee may not hit "R" and must
press another key to exit without registering the program. If you accidentally
register the program, you may follow the steps above and you will be shown how
to 'un-register' the program.
You will then be returned to the main selection screen. If you have
changed the registered status of the program you will need to update your
language file as the registered program cannot use the unregistered language
file (or vice-versa).
...end of document...