     THD ProScan is a collective effort by myself and a number of others.
While most of the time you associate only myself with the various releases,
I feel that I need to take a moment to acknowledge that were it not for the
great users and fantastic beta testers, this product might have long since
been history.
     Since the inception of THDscan (about 6 years ago) there have been
many people who have helped to find problems and offered assistance in many
other ways. This version of THD ProScan is dedicated to all of those people.
Without regard for how great or how small their contribution, these are the
people who have made it possible for you to receive this version.
     Please take a moment to read the credit section of this documentation.
Although only a few are specifically listed in that area, it is worth noting
that there are in fact many other contributors. Some who have made donations
or incurred costs, or perhaps even simply made a comment or suggestion are
still deserving of a mention.
    Among those rarely ever mentioned, I would like to thank the makers of
the products that THD was designed to replace. While I would never recommend
some of the products that fall into that category, I can't help but remember
that had it not been for those inferior products, THD might never even have
made the drawing board.
     The early creators of file processors missed a great many details now
considered standard, however without their original ideas, this product and
many others may not ever have come into existence.
     And to my competitors, without whom this product might be only a shadow
of what it is today. Some have been friendly and other have downright
destructive, but all have helped in the creation of various versions.
     While no implementation in THD has ever been taken directly from another
product, many of the "toys" are based on suggestions from users who had seen
similar options in other products. As I'm sure on occasion users of other
products have made suggestions based on things they have seen in THD.

     I could never hope to mention everyone who has made a relevant
suggestion for the improvement of THD. Nor could I hope to recall all the
people who have made a significant difference in it's development. What I
can do is to thank them all here for their contributions, whether
intentionally or by circumstance.

     So, to all the testers, users, non-users, nay-sayers, praisers, critics
and competitors...
Thanks for your contributions, no matter how great or how small...

       This one is dedicated to you.

                                 -------------
                                 - COPYRIGHT -
                                 -------------

         The following  copyright covers  THD ProScan and  all of it's
         parts,  including  (but  not limited to),  THDPRO,  THDINSTL,
         THDPLUS, THDTERM, THDDOC and THDDEMO. The TESTINFO.DAT format
         is covered by a separate copyright.  Please see  TESTINFO.INC
         for details.

         These programs  and  all  of their  associated names,  files,
         logos  and  makeup  are  Copyright  1992 - 1994 by  PainSoft.
         Absolutely  no  duplication  in whole or in  part is allowed.
         With the exception of  duplication of the entire archived set
         of files  for distribution to those in need of it's services.
         None of the  copyrighted material  may be changed in any way,
         except by the author.  Changes made by the author's original,
         unmodified  installation  program will be  considered to have
         been made by  the author for the purpose  of this  copyright.
         The files may be  rearchived in  ANY  fashion which  requires
         them to be  restored to their original condition before  use.
         (Portions are Copyright  Borland  International).  The Author
         accepts  no responsibility  for the  actions of this program.
         It is  FREEWARE  and NO  charge may be made for distribution.
         It is  NOT  a commercial  product  and  the  ONLY  acceptable
         charge for it will be "actual, physical cost of duplication".

         Other products mentioned are  copyrighted by their respective
         owners and  include their  own  restrictions  for use. Please
         be  sure to  register  those  products  if  requested  by the
         copyright holders.

                              ----------------
                              - INTRODUCTION -
                              ----------------

- The Product -
---------------

- Overview -

     THD ProScan is an File Processor. It was conceived as a security 
conscious method for testing the integrity of archived files and has
evolved from a 50 line batch file to what you see now.

     The general purpose of an file processor is to perform a series of 
tests on a given file (usually an archive) and report the passing or failing 
of the various tests. The types and number of tests done will vary with the 
program being used, but the one test viewed as the most important is the 
Virus Scan. Others tests are (or are not) performed depending on the 
software being used. Normally things like CRC testing and commenting of 
archives are standard procedure.
     These products are known by many names, almost all of which are a
contraction of one of FILE, ARCHIVE, or UPLOAD and TESTER, PROCESSOR or
CHECKER. Whatever they call themselves, their usual goal is to offer some
assurance that the files have been reasonably tested for integrity.

     The difference between this and many other upload testers is one of
priorities. Most upload/file testers regard the testing of the file as the
single most important factor. THD ProScan, on the other hand, has a
different view.
     THD ProScan is designed with security as the single most important
factor in a file tester. It is with this in mind that THD ProScan has been
programmed from day one. This is also the reason why some things that you
might "like" to see are not present. You cannot change a number of things
which others allow. The reason being that the options used in this tester
are the ones most likely to stop people from gaining access to your
computer. Simple things like not allowing user definable commands to be run
and insisting that full paths be supplied, help to ensure that the sysop
without a full working knowledge can get as much benefit from this tester as
the seasoned pro.
     By the same token, THD ProScan also attempts to compete and defeat the
so called "competitors". It attempts to do as many things as could be
realistically asked of an upload tester, while maintaining the security that
prompted its creation as well as being generic enough to be used by as many
BBS programs as possible.
     I think you will find that the number and types of options available in
this tester rival or exceed those available with a number of other testers.

                      If you need an upload tester...
                      -------------------------------
                      ---- YOU NEED THD PROSCAN -----
                      -------------------------------
- Registration / Donations -
----------------------------

     While THD ProScan is a FREEWARE product, the author (that's me) does
gladly accept donations. There is no "set" amount or for that matter it
doesn't even have to be cash.
     Since my main concern is to upgrade my current computer (an XT), I will
also accept hardware in the hopes that it will assist me in building my new
computer.
     Details are available in DONATE.PLS and the address is found in the
author section of this documentation.

- History -
-----------

     Long, long, ago and far, far, away.. I used to call about 40 BBS'es a
day. I became concerned one day when I uploaded a file and it failed
something called an "upload test".
     I quickly downloaded the program which failed my file and was amazed at
what it was attempting to do. (cool I thought). However upon looking closely
into what it was doing and how it was being done, I became VERY concerned.
This program could give a user COMPLETE control of the sysop's computer if
they created just the right archive.
     Being the conscientious little co-sysop that I was, I went searching
for a similar program without the flaws present in this one. Believe it or
not, I couldn't find one (I did find some 15 other programs, none of which
addressed all of my concerns). I decided instead that I would create a
"secure" batch file for this sysop to process his uploads. I made one that
worked on my system, then I made it configurable (so that the sysop could
customize it for his system).
     And such was born a 4DOS dependant batch file called THDScan. (are you
still with me?). Others of course called and saw the "neat" screen output
and inquired as to where they could get a copy and so on.. Many were amazed
at what could be accomplished through batch processing and began to use it.
As is normal, problems began to arise and improvements were requested. And
so development of THDScan continued.
     This development saw many changes and additions to THDScan through the 
two years it was being improved. But alas, as is always the case, some 
spoilsports refused to use it because it was a batch file (not to mention it 
needed 4DOS or NDOS to properly run). And so Development of an executable 
version of THDScan began.
     No-one was willing to "program" it my way, so I started to learn Turbo 
Pascal in the hope of creating it myself.
     And after much hair pulling, on August 20, 1992, the world was 
introduced to THD ProScan Version 1.0. (more like about 45 local systems). 
Things continued on with bug reports and so on (what can I say, I never 
programmed anything before). And so began the upgrading of THD ProScan.
     Somewhere around version 6.0, I was surprised to receive a netmail from 
Ireland making inquiries about my program (whoa.. all the way from Ireland). 
I asked this person for explanations, what I could do etc. and he was most 
helpful in showing me what he wanted added/changed to support his particular 
use.

     Soon thereafter netmail started coming from everywhere (okay .. almost 
everywhere). THD had somehow become a popular program. From that point onward 
THD has been treated by me as a major endeavour.
     The Version 10 being released today, is the result of many such
communications and many, many hours of work. None of which I have ever
regretted.
     For those of you who are dying to know, THD actually stands for
"The Head Doctor" (the alias of the sysop for whom the original pre-version
1.0 THDScan Batch file was created). I have long since lost contact with
him, and many of the people whom I knew at that time. But I suppose I ought
to thank him for lending me his monogram.
     So there it is.. everything you never wanted to know about THD ProScan.

                               --------------
                               - THE AUTHOR -
                               --------------

- History -
-----------

     Who am I?

     Hi. I'm David Muir, born in the winter of 1962. I was introduced to 
computers about 8 years ago by a friend. BBSing at that time was something 
that I hadn't even considered.
     Not too long after that I got my first IBM compatible computer. I 
played games, made notes, and used it to keep my company records. It was a 
tool. After scooping some neat toys from a friend, I began to inquire how he 
came about getting them, he explained about modems and BBS'es. I soon after 
purchased a neat 2400 bps modem and got a few numbers off of him.
     In no time flat I was a BBS junkie. Calling up to 40 BBSes at a time 
and trying my best to help people out. I eventually got to co-sysop on about 
15 of those boards and was quite in demand as a co-sysop (due mainly to my
security conscious approach). But time took it's toll, and eventually I had 
to lessen my outgoing calls. Somewhere in there THDScan was born and later 
THD ProScan.
     So now I'm a 32 year old computer junky, who loves nothing more than to 
get netmail from places I've never been and help people with problems I 
don't have.
     THD ProScan is my way of helping. And a pretty good reason to talk to 
people from distant places. I still use that same computer (an XT compatible 
that cost darned near as much as my car). Generally I'm a pretty boring 
kinda guy who's more than willing to lend a hand when I can.

- How to contact me -
---------------------

     I can be reached via Netmail at Tim Strike's BBS

The Forbidden Knights
1:259/423.0 (fidonet)
(905) 820-7273
Mississauga, Ontario
User name- David Muir
Alias - Pain

     Home is...

David Muir
198 Leyton Ave
Scarborough, Ontario
Canada, M1L 3V6

     I'm also available in numerous other nets (look for Tim's BBS) as well
as following many of the public echos which relate to BBS support.


                             -------------------
                             - PRODUCT SUPPORT -
                             -------------------

     Product support is available directly from the author according to the 
information above. However, you might find that many people in the public
echo areas are willing to help as well.
     Most of the sysops listed as distribution sites will be happy to try to
assist you and if unable to do so, will generally forward questions and
comments to me.
     Questions regarding interaction with your particular BBS type are
generally best answered by those who use the same BBS software as yourself.
If however you're stuck and no-one seems to know the answers, please give me
a shout, either by mail or via netmail (or possibly in the public echos if
you happen to spot me).

- Commentary (THD vs other Archive Processors) -
------------------------------------------------

     In the last year or so, it seems that the Archive Processing field has 
become VERY competitive. I have done my best to uphold my friendly 
disposition in the face of numerous attacks, both on me personally as well 
as on my product.
     So people who don't want to know how I REALLY feel should not read 
this.

     Still with me? Okay...

     THD ProScan is NOT a hobby. It's not something I do to rip the nice 
sysops off for their money. It's not a pastime that I use to fill my empty 
hours. It IS an obsession. THD is what I do. To attack it, is to attack me. 
I do engage in employment as well, but that is something which I am paid to 
do and do not do because I "desire" to do it.
     In the past year, I have been called everything from a complete fraud 
to a liar. I am neither. THD has been called ineffective, inefficient and 
unreliable. It is none of those things.
     What THD is, is quite simply my way of saying thank to the many sysops 
out there who need something and may not know what. THD is built with 
security in mind. To date NOT even ONE other archive processor has been able 
to match THD in its efficiency and security. Now to be fair, there are some 
that I have not tested. In those cases I have not come across them or have 
found them not to run on my XT.

     I do not begrudge the other authors who believe that their product is as 
good or as secure as my own (or those who believe that theirs is superior to 
mine). But I can tell you, in all honesty, that with the singular exception
of THD ProScan there does not exist an upload tester (of which I am aware)
through which I cannot pass a KNOWN virus in a legitimately testable archived 
file. This refers to a virus that will be recognized by McAfee's VirusScan if 
all archives are expanded and all resulting files are tested. This does not 
refer to any underhanded encryption technique or creation of the virus after 
being tested. But an honest to goodness real virus in a file type which those 
other do test.
     Some of those other products can even be manipulated by an uploaded 
archive to allow the remote user "FULL" access to the host system.
     If it's any consolation, the last statement refers to fewer and fewer 
products as time goes by. Most regularly updated processors do guard against 
this particular instances.. BUT NOT all of them, so watch for these.
     I specifically will not mention any of the people who have attacked 
myself or my tester. But I will be honest, in saying that if I ever actually 
tell you not to use a specific product (something I would rarely ever do), I 
do have my reasons and they are never related to anything as petty as 
revenge.
     I stand behind my product. I believe what I tell you about it, and most 
of all I make it for you.. not me. (I have no use for about 90% of what is 
coded in there, 10% is coded for me the other 90% is coded for the people 
who use it). Remember that I am not a sysop and most of the features in THD 
are BBS related.
     As a final note. Many of my competitors in the Archive processing field 
are not described above. Many are very friendly and professional people who 
have never said anything to belittle myself or my product (or anyone else's 
product). Many of them are good intentioned hard working people, bringing 
you what they believe is an excellent product. Please if you use one of 
these other products and the author requests registration... be sure to 
register the product. The amount of work that goes into these things is not 
petty and those who request registration have worked long and hard to 
produce that product for you. Be sure to remember that when you see them 
asking for registration.
     Above all. Remember that I truly do believe that THD is a superior 
product. (and I have tested enough of them to make a reasonable judgement)
     If you feel that another product is better (or better suits your needs)
then use it with my blessing. The final consideration must be what you 
believe you need and not what myself or another author thinks.
     Thanks for reading my babblings...

     David Muir... Author THD ProScan.


- Requirements -
----------------

         This tester requires...

         - PC/XT (or compatible)
         - MS-DOS 3.3 (or higher)(other "DOS" systems MAY be acceptable)
         - A FOSSIL DRIVER (user output will not be sent if no fossil is
                           found but the testing will still be done)
         - At least one Harddisk (drive assignment C: - Y:)
         - at least ONE of i) McAFEE's VIRUSSCAN (2.x.x supported by default)
                                               (1.x.x support through THDOPT)
                          ii) F-Prot
                         iii) TBScan
         - Enough free memory to run each of the utilities used by this
           program (+3k). THDPRO.EXE requires about 225k itself to load, but
           releases all but 3k of that to run external programs.

         The following utilities are required depending on which file types
         you wish to test.

         - ARJ.EXE        for "ARJ" files (version 2.41a)
         - GIFTEST        for "GIF" files (version 4.xx)
         - HYPER.EXE      for "HYP" files
         - LHA.EXE        for "LZH" files
         - PAK.EXE        for "ARC" files
         - PAK.EXE        for "PAK" files
         - PKARC/PKXARC   for "ARC" files
         - PKPAK/PKUNPAK  for "ARC" files
         - PKZIP/PKUNZIP  for "ZIP" files (version 1.10 - 2.04g)
         - RAR.EXE        for "RAR" files (version 1.51)
         - SQZ.EXE        for "SQZ" files
         - TDCHECK.EXE    for "TD0" files
         - UC.EXE         for "UC2" files (revision 2)
     (Where versions are specifically mentioned, it is believed that
      versions other than those mentioned "may" not work as expected.)

- Function -
------------

         WHAT WILL IT DO..
              THD ProScan will ..
         1) Check (and/or reject) files from a user supplied list of files
         2) Strip the file comment
         3) CRC test the file
         4) FIND a drive with enough space to test the file
         5) Create a directory called "THDTEMP.???" on that drive
         6) Remove files (if configured) from the archive.
              (Removal by name, by crc, or by both)
         7) Check dates to reject old files (if selected).
         8) Expand the archive into that directory while recreating
               its internal path structure.
         9) Extract and process VENDINFO.DIZ if configured.
         10) It then selectively searches each of the subdirectories created
              for testable archives. If found, it repeats the above process
              until no more archives are found.
         11) It will then scan each of the files in that directory and
              all subdirectories below it.
         12) THDPLUS will run if so configured.
         13) Add your loaders to the archive
         14) It maintains a log in your BBS directory of all actions
              performed.
         15) Perform a complete accurate conversion (if selected).
         16) Add your file comment.
         17) It then proceeds to remove the temporary directory structure.
         18) Updates all of the log files.
         19) Reports the appropriate errorlevel to dos.

              The full process is actually much more complex than this basic
         outline, but the above gives a reasonable representation of what
         happens.
- Features -
------------

- Support for ARC/ARJ/GIF/HYP/LHA/PAK/RAR/SQZ/TD0/UC2/ZIP file formats.

- Two testing methods.
    THDPRO.EXE starts out in default mode. In this mode THDPRO.EXE will
    attempt to expand the main file and all of it's imbedded files prior to
    beginning the virus scan. This method is designed for speed, but can
    require a significant amount of disk space. If unable to expand one
    of the embedded files, THDPRO.EXE will drop back to the "FALLBACK"
    method.
    The "FALLBACK" method, extracts and scans each imbedded archive
    separately. This method may not require as much disk space (in some cases
    it requires significantly less), but will take longer to run. This is the
    method used by all previous versions of THD ProScan. The drop to the
    FALLBACK method is automatic and only used when space prohibits the use
    of the default method.

- Intelligent processing of LHA files.
    The handling of LHA files is done in an "intelligent" manner. The file
    type is diagnosed to see if it is expandable on a DOS based system. If it
    cannot be expanded, it will be CRC tested only. If it can be expanded, it
    will be checked for the use of the root directory. If it attempts to use
    the root directory, a clone will be built which makes no attempt and the
    clone will will be expanded and tested in its place.

- Complete logging of file testing.
     All aspects of the test are logged in a file called THDPRO.LOG in
     a directory which you configure in THDINSTL. The size of this log
     is configurable, and it reports processes and failures.

- Logging of heuristic testing only when suspicious code is found.
     It seemed unreasonable to log all heuristic testing, considering that
     MOST of the time there are no infections. The logs kept for failures
     or for suspicious code are generated by the virus scanners themselves.

- Sysop can opt to NOT test files if they are too large.
     During the installation, you can choose to not test files over a given
     size. If you choose this, you may pick from files over 1,2,3 or 4
     megabytes (1048576 bytes per megabyte). If this option is enabled
     and THD ProScan is asked to test a file larger than the "acceptable"
     size, it will prompt the sysop for 5 seconds to press a key. (in this
     way you can still test these files manually by pressing a key). If no
     key is pressed, the file is passed without testing.

- 100% share aware and compatible (share.exe is not a requirement)
     Before any file is opened by THDPRO.EXE, the presence of share.exe
     is determined. If SHARE is loaded, then the file is opened in a
     shared mode, so that other processes may also use the files. If
     share is not loaded, files are opened in standard mode.
     If file access is denied, THD ProScan will wait for up to 30 seconds for
     the file to be released. If the file is not released in 30 seconds,
     the test is aborted and the file passed. Otherwise, if the file is
     released, testing will resume without incident.

- File descriptions can be directly imported into the file data bases. Through
    the use of THDPLUS, file comments can be added to the file bases
    for users of REMOTEACCESS 2.00(+), Telegard 2.7, Renegade 07-17 and the
    many FILE.BBS supported BBS'es. THDPRO.EXE will create a data file with
    the necessary file information and then call THDPLUS to make changes.
         VENDINFO.DIZ if found will be processed and used regardless of the
    presence of the following files. Without a VENDINFO.DIZ these description
    files will be prioritized in the following order.
       i) FILE_ID.DIZ - if found it will be used.
      ii) DESC.SDI - will be used in the absence of FILE_ID.DIZ.
     iii) DESC.SDN - will be used if neither of the above are found.
    In the event that no description files are in the archive, THD ProScan
    will make no attempt to alter the user's description.

- Allows the sysop to use any combination of
  SCAN.EXE / F-PROT.EXE / TBSCAN.EXE  (1, 2, or all three)
    SCAN.EXE is no longer required due to it's memory needs. Instead
    you may opt to use any or all of the noted virus testers. Or any
    combination of them. However note that at least ONE MUST be used.
    Simply tell THDINSTL the full path and filename of the tester(s)
    that you wish to use and all selected scanners will be run on
    every file. Support for the SCAN 1.x.x series is available through the
    proper use of the THDOPT environment variable (explained later).

- Supports "heuristic" testing for suspicious code using F-PROT.EXE
  or TBSCAN.EXE.
     When testing is done using F-Prot or TBScan, the tests are always
     performed in "heuristic mode". This will enable these testers to
     find some unknown viruses as well as the known viruses.

- Optionally pass or fail files which contains suspicious code found
  by the heuristic testers.
    You can choose to consider "suspicious" files as being virus infected
    and thereby cause THD ProScan to consider them failed. Normally, I
    recommend against this but there are many valid reasons to fail such
    files. DO NOT fail these files if your BBS deletes failed files. This is
    only optional if SCAN.EXE is used. in absence of SCAN.EXE heuristic
    failures will be considered virus infected.

- Optionally display a "changed" internal interface.
- Allows the sysop to supply up to 9 user side "interfaces" .
     New in version 9.0 is the ability for the sysop to supply up to 9
     user side interfaces and 9 replacement corners for the internal
     interface. Giving a total of 21 possible remote screens to be
     chosen at random during any one test run.
- The file after testing can be time stamped with one of four date
  selections.
    Original date - Choosing this option will date the finished file with the
         same date and time it had at the start of the test.
    Current Date - Choosing this option will date the finished file with the
         time and date of the completion of the test.
    Newest date - Choosing this option will date the finished file with the
         time and date of the newest file included inside the archive.
    Best Guess - Choosing this option will date the finished file with the
         time and date of a calculation of the average date and time of the
         five newest files internal to the archive.

- Identifies all archives by their internal signatures.
- Including self extracting archives.
    All archive types are recognized by their archivers unique signatures.
    Even the self extracting files are done by signature, so the name of
    a file will have no bearing on whether or not it is tested. If it is an
    archive type which you have configured for testing, it will be tested.
    This may be limited by some bbs programs ability to tell THD ProScan
    what to test, since some will only pass the file for testing based on
    it's extension.

- Allows files to be rejected based on the dates of the files inside the
  archives.
    You can choose to limit the acceptance of files on your BBS based on the
    actual date of the files inside the archive. OR you may choose to limit
    them based by how old they are. The difference? You may choose to reject
    files older than "3 months" (you choose the age) and thereafter never
    update the limit as age is compared to the date of testing.
    Or you may choose to not accept files created before "January 1 1990"
    (again you choose the date), and files will be failed based on their
    "date". Note that the dates referred to here are the date INTERNAL to
    the archive and not the archive date.

- Can reject files by name using a "hack list" (HACK****.COL and IDX
  files can be read directly).
    You can choose not to test files which have specific names. This is
    useful for avoiding testing of known viruses/hacks/pirated software.
    You can create a list of file names to be rejected or use the
    official "Hack Report" files. Or you can mix the two. Files rejected
    by this method will be considered to have FAILED testing.

- Support for remote ansi or ASCII as determined by auto ansi detect.
    The presence of ANSI on the remote side is automatically detected.
    If ansi is found, it is used. Otherwise output is plain ASCII.

- Suppression of remote output through the use of "comport 0".
- Suppression of remote output through the use of a user defined comport.
    Remote output can be suppressed when run locally (to avoid sending
    the ASCII output to an unsuspecting user). It can also be suppressed
    when told to send to a "legitimate" comport. (Not recommended except
    in some very odd circumstances)
- Protection for "ZIP" archives which have a valid "AV".
    Zip files which contain a valid "AV" (Authenticity Verification)
    will not be modified, since this would corrupt the "AV". These
    files will be reported in your THDPRO.LOG so that you may see
    if they have legitimate "AV"'s. All "testing" will be performed as
    usual.

- Strips comments from all archives before any processing is done
    Ansi bombs are avoided by stripping the comments of all archives
    without allowing the comments to be displayed to the screen. This will
    protect your system from ansi bombs while THDPRO is running.

- Recreates full directory structure "from" the temporary directory,
    Although the process involved is very complex to explain, if an
    imbedded archive exists in an archive it WILL be found and tested.
    No matter how many subdirectories or other imbedded archives must
    be searched in order to find it. This is limited by the types of
    archives supported by your system. But if it can be found with
    what is configured...IT WILL BE.

- Does not allow the "overwrite" option on any of the archive types.
  (stops some forms of "hacking")
    Some upload testers use the "overwrite" option to avoid having
    the archivers prompt the sysop for input. THD ProScan does not allow
    overwrites of any kind. The reason being that one of the most popular
    methods to corrupt your system was to create archives which would
    expand over your system files. THD ProScan will not allow this.

- Add loaders to the main archive.
    THD ProScan can (if configured) add loaders (insert files into
    an archive).

- Insert your file comment
- Insert a specific comment depending on the location of the file.
    THD ProScan can add file comments in a number of ways. It can be told to
    add a single comment to every file tested. OR it can select at random from
    list of such comments. OR it can insert a comment based on the file's
    location at the time of testing. The options are further explained in
    the "COMMENT" portion of this document.

- Configurable file specific text in file comments.
    Key words can be used in file comments to be replaced by file specific
    information. Please see the section on Configurable comments later in this
    documentation.

- Will use one of as many as three drives to test files by searching in
  order to find enough available space on one of them.
    THD ProScan will search up to three drives (as selected in THDINSTL) to
    find one which has enough free space to expand the archive to be tested.
    Testing will only be done if sufficient space is found.

- "Intelligent" installation which will attempt to do as much of the
  installation for you as is possible.
    The installation tries to find any file which it prompts for by name.
    If it finds a file by that name it will ask you if you want to use
    it and optionally allow you to insert the path to a different file.
    (in this way you are not limited as to the location of your utilities)

- Online help during the installation.
- Dos shell from the installation.
    While running THDINSTL, online help is available by pressing F1, a dos
    shell is available by pressing F2. and the installation can be aborted
    by pressing "CTRL-C".

- The configuration of THDPRO.EXE (from ver 6 or higher) can be used
  automatically.
    THDINSTL can import the configuration of any previous version of
    THDPRO.EXE (6.0 or later). You can then modify that configuration
    to suit your needs with this version.

- Will Virus scan all file types regardless of types configured.
    If THD ProScan is asked to test a non supported archive or a "normal"
    file, it will simply virus scan the file. In this respect it is
    a good idea to have all uploads tested by THD ProScan.

- Remove unwanted files from the archives tested (using name and/or CRC).
    Files can be removed from archives based on their name, their CRC
    or both. A more complete explanation is available under the heading
    "CRC MODE".

- Option to hang up on users who upload viruses.
    Sysops who are tired of users not virus scanning their software before
    upload may choose to drop carrier on those offenders.

- Option to reboot after a viral detection.
    You may also reboot after a viral detection. Although usually not
    necessary, It does make some people feel better.

- THD ProScan also supports a "fall back" to the original processing
    method. If an imbedded archive fails to expand for testing, THDPRO.EXE
    will fall back to the old method which extracts and tests each
    imbedded archive separately (thus requiring less space).

- No Known ways to "alter" the operation of your BBS through it's use.
    As stated this tester is designed with security in mind. I have done
    everything in my power to use the options best suited to that purpose.



{NOTE} The support BBS of this magaine uses THDpro as our upload scanner!
We highly recommend it!

