THD ProScan Version 13.0
for DOS and OS/2
THDTERM.EXE
-----------
- Outline -
-----------
This document outlines the operation of THDTERM.EXE.
- General Information -
-----------------------
This is an excellent tool for sysops as well as users. For a sysop, it
will allow them to use THD ProScan with their fossil active without
attempting to send output over the modem. Thus making it the perfect
tool for a sysop or user to test his/her downloads.
For users in general it provides the same security that many sysops have
become accustomed to.
Needless to say, THDPRO.EXE will need to be configured properly before
this program will be of any use.
Reasons for failure are not reported by this program, but all such
instances should be accounted for in your THDPRO.LOG created by THD ProScan.
With the exception of possible runtime errors, this program will ALWAYS
exit with errorlevel "0". The only indicators left by this program will be
the presence of the tested files in the pass or fail directory. In keeping
with the tradition of THD ProScan, this program will NOT delete files for any
reason. Files are left for you to do with as you choose.
This program was outwardly inspired by THDPRO TERMINAL EXTENSION. A
program created for the same basic purpose as this one.
- command line syntax -
-----------------------
THDTERM accepts 2 parameters. Default is to run THDTERM with no
parameters to process "as configured".
- /C# {where # is a digit from 0-8}
A single digit from 0 to 8 which represents the comport to which it
should have THDPRO.EXE send it's output. The default is to use "0"
which will cause THDPRO.EXE to run in local mode. A comport is always
sent to THDPRO.EXE, even if none is supplied.
- /S (source directory)
Running THDTERM.EXE /S {drive:\source\dir\to\test} will cause
THDTERM to process the supplied directory instead of the internally
configured directory. Also, when run with the "/S" parameter, moving
of "passed" files is suppressed, and only those files which fail are
moved (to the fail directory).
- Requirements -
----------------
THDTERM requires a configured copy of THDPRO.EXE and about 2k of memory
above that which will be required by THDPRO.EXE. As well, since it runs
THDPRO.EXE, it also requires the same things required by that program. If you
can run THDPRO.EXE normally and have an extra 2k of memory, then you have met
the requirements.
- Configuration -
-----------------
This tool must be configured using THDCFG.EXE. See THDCFG.DOC for
details.
- Function -
------------
Functionally speaking THDTERM doesn't actually "do" a whole lot. It's
purpose is entirely single minded. It is designed to replace a simple dos
"for..in..do.." statement. Meaning that it runs THDPRO.EXE on each file in
the default directory (or alternately the supplied "source" directory).
The advantage to using THDTERM is singular. It runs THDPRO.EXE on each
file, and moves it (in default mode) to either the pass or fail directory,
depending on whether it passes or fails testing by THDPRO.EXE.
The singular advantage to this method is that it will never duplicate a
test as might be seen by a dos for..in..do.. statement and it provides a
little error checking prior to moving any files.
Basically it is a glorified batch file.
- Features -
------------
None to speak of. It serves a very basic purpose in a very basic way.
This program should be used where you might like to use wildcards with
THDPRO.EXE but are unable to. Or where you want tested files to be moved after
testing.
- Basic Operation -
-------------------
Basic operation is achieved by configuring the program and running
THDTERM.EXE. This will cause it to run THDPRO.EXE on each file in the default
(or alternately the "source") directory. Files will be "moved" to the
directories internally configured depending on whether THDPRO.EXE passes or
fails them.
- THDTERM and Filedoor -
------------------------
THDTERM now accepts a comport as a parameter. As with THDPRO.EXE, the
comport must be the last parameter and must be a number between 0 and 8. If
supplied with a comport, THDTERM will tell THDPRO.EXE to use that comport
instead of "0" which it uses by default.
This modification will allow Filedoor users to use THDTERM to run
THDPRO.EXE while still sending the remote output to the user. Those sysops
should have their exitafteruploads command as follows.
ExitAfterUpload1 C:\THDPRO\THDTERM.EXE /S $U $P $M $N
I also recommend that the "exitmask" not be defined and that THDPRO.EXE
be expected to test ALL uploads.
Note... I do not use Filedoor myself and have based the above strictly on
the documentation for that program. Some modification may be necessary.
Also note that, newer versions of filedoor may not work as described here
and may in fact be able to pass the filename as required by THDPRO.EXE.
Versions capable of passing the filename should use THDPRO.EXE for this
purpose and not THDTERM. Use THDTERM only in those instances where file names
cannot be supplied.
---------------