Revision History:

2.30 - 4/30/94 - Major revision (public release)

Revised bltcap2 to use an initialization file. This eliminates the need to
edit the script directly. Re-wrote the @icom.scr install script to be a
generic installer. This really speeds up creating a new version.

2.20 - 04/28/94 - Minor revision (internal release)

Modified the Check_Version code. Fixed the use of the newarea command.
Verified that 2.01B6 had indeed resolved a while/endwhile bug. Changed the
format of this file from a changes document to a revision log.

Changes since 2.00

1) Bltcap2 now properly checks which beta version is being used. Since it
   won't work properly with anything less than 2.01B4, this was a necessary
   modification.

2) In order to handle multiple BBS's with the same script, the logic has
   been modified. The BBS variable initialization has been moved into a
   subroutine with the same label as the BBS's BIF name. When bltcap2
   executes, it does a 'gosub $BIF_NAME' which assigns the BBS specific
   variables for the current BIF.

3) The @icom script has been modified to detect old versions of bltcap2 and
   grep and will automatically rename them with the extension ".old". 

Changes since version 1.x:

Since bltcap2 is a complete re-write, everything's changed ;-). However,
here are some of the major new features compared to version 1.x.

1) Bltcap2 is entirely script based. Version 1 relied on a 'C' program
   to search for new bulletins and then generate a custom script. Bltcap2
   uses the support script grep.scr to search for the new bulletins and
   takes advantage of Icom's powerful script language to generate the
   required commands on the fly.

2) No initialization files. Since Icom's script language allows access to
   everything in its INI and BIF files, no initialization files are required.
   All the required BBS specific information is determined at run time. The
   only information that isn't determined from the BIF is the new bulletins
   search string. If people provide me with a list of the search strings they
   encounter, I'll make detection automatic for those boards.

3) Since Icom automatically detects the operating system it's running under
   (DOS, Windows OS/2...) I take advantage of this to automatically slow down
   the capture operation when running under a multitasking environment. This
   reduces the chance of losing characters during the capture, but slows down
   the script a bit.

4) Bltcap uses lots 'o window dressing to make the bulletin capture more
   interesting...if that's possible.