Version 1.2

        Added a pause at the end of the run so the summary statistics
        can be viewed before the screen is cleared.  In interactive
        mode, GAP_Verify will delay until a key is pressed.  In
        command line mode, it will pause for 15 seconds before 
        exiting.  If, during this 15-second period, a key is pressed,
        GAP_Verify will pause until another key is pressed.

        Added the /M parameter to override the default pause
        behavior at the end of a command line mode run.  If /M is
        specified on the command line, GAP_Verify will wait for a 
        key press at the end of the run.

        Added a full-screen status display that shows all sorts of
        information about the current run of GAP_Verify, including
        counts of files and total bytes processed.  (The "Content
        Bytes" field won't display a meaningful value unless you 
        are extracting FILE_ID.DIZ's during the current run.)  The
        history window is essentially the information that used to
        be displayed in v1.1 and earlier, though it's been condensed 
        a bit.  Only files that have been updated are displayed here.  
        Following the name of the file are one or more letters that 
        indicate what was changed.  The letters DSLDKZ are displayed 
        in fixed positions to indicate the Date, Size, Location, 
        Description, Keywords, or DIZ was changed.  In the case of DIZ, 
        it really means a DIZ was extracted and used instead of the 
        current enhanced description.

        Fixed a problem with the deletion of old keywords.  This
        bug shouldn't have caused any harm to your filebase, though
        you may have more keywords than necessary associated with
        some files.  If you're concerned about this, have GAP_Verify
        re-parse the keywords and the extra keywords will be cleaned
        up.

        Special note:  It wasn't mentioned in the docs previously, 
        but it's a good idea to run GAPMAINT and pack both the 
        Files and Keywords after you've done a major update with
        GAP_Verify, particularly if you've extracted FILE_ID.DIZ
        descriptions.  Because GAP_Verify adds the contents line to
        the end of the enhanced description when extracting DIZs, 
        many of the filebase records will have to be moved to accomodate
        the longer descriptions.  This will leave a lot of "holes" in
        the filebase.  No harm there, but your filebase may take up
        a bit more disk space than it needs to.  Packing the filebase
        will take care of the "holes".


Version 1.1

        Fixed an insufficient memory problem that occurred when a
        board had several hundred forums.  Also added an error message
        (which should have been there all along) in the extremely
        unlikely event that there should be another memory shortage
        in this area.  (You'd have to carry every echoed conference
        known to man to run into memory problems in this particular
        area, but you'll get an error message if it happens!)

        Changed the version number to 1.1.  It was mistakenly left
        at 0.9 in the 1.0 release.

        Changed the screen output functions to provide better speed.

        The change to the screen output resulted in inconsistent 
        fielding of Ctrl-C and Ctrl-Break, so the keyboard is now 
        checked after each file is processed.  If any key has been 
        pressed, you'll be specifically asked if you want to terminate.
