
                                 PROOF V1.3

                              by John Augustine

  Proof was written in Assembly for MS Dos systems, but can be used at the Dos
"prompt" (Windows 3.1/95/98/ME/etc.). It uses little memory, and requires no
"installation".

  PURPOSE:

  The purpose of Proof is to see if a file, a group of files, or all the files
in a directory/folder has changed.  Also, Proof can be used to compare your
file/s with someone's file/s, without using a direct comparison, to verify
that it/they is/are exactly the same.  One example, if you send someone a
file/s attached to email.  Another example is to check your system files with
someone who has the same system, without that person sending you the files for
a direct comparison.

  PROOF'S SENSITIVITY:

  Proof can "detect" a change as small as one "bit".  The odds of two files,
that should be the same, with the same number of bytes, producing the exact
same checksums, but are not exactly identical is 4.3 billion to 1!

  CHECKING YOUR FILE/S:

  In order for Proof to be useful for checking your file/s for a change, you
must run Proof and write down the number of files (if a wildcard was used),
the total bytes, Checksum A and Checksum B for future reference (keep a
record).  One example for using Proof is for checking all your system files,
usually stored in "SYSTEM" directory/folder within the "WINDOWS" directory.
These files should never change unless you made an upgrade, added an
application, or removed an application.  If the checksums changed, see if the
number of files changed and/or total number of bytes.

  DOS "PROMPT" (WINDOWS) WARNING:

  Do not use Proof to "proof" all the files in the "WINDOWS" directory/folder
due to a couple of files that prevent access while Windows is "running".
Anyway, some files in the "WINDOWS" directory are always changing, so
"proofing" here is not a good idea.

  COMMAND EXAMPLES FOR RUNNING "PROOF" (without quotes):

  "PROOF QTIM.DLL" (single file)
  "PROOF *.DLL"    (all .DLL files in a directory/folder)
  "PROOF *.*"      (all files, including hidden, in a directory/folder)
  "PROOF QTIM.DLL /10000" (single file, but in 10,000 byte blocks)

   "PROOF FILENAME /NN" ("NN" = a number from 100 to 60,000):

  This feature operates on a single file.  If you use a "wildcard" (*) in the
filename, this feature will be ignored.  It allows you to "proof" a file in
parts (blocks).  NOTE: The final checksums usually will not be the same as
"proofing" the entire file in a single pass (without adding a "/NN").

  I added this feature because I have a use for it.  Most users will probably
not use it, but I wanted to explain what it is about.


  CONCLUSION:

   "Files Validator" is another type of files integrity checker program with
advanced features that will identify an individual file/s out of a group that
changed or is missing.  See (use "HELP.EXE") "OTH-PGMS.TXT".

  Comments or complaints are always welcomed via email.

                     John Augustine N3AOF
                     3129 Earl St.
                     Laureldale, Pa 19605

            E-Mail:  jaugust@bellatlantic.net

