Automated Verification Algorithm version ---------------------------------------- AVA SF v2.0 ----------- February 15, 1991 AVA SF incorporates all the changes and features as listed for AVA v4.0 below. The SpitFire version of AVACFG and AVA SF differ in that the configuration file can be any name. When invoking AVACFG you can supply an optional file name as well as the path to your AVA.Exe file. Example: d:> AVACFG MyAVA.Cfg * AVACFG will use and load MyAVA.Cfg. If no file name is supplied on the * command line AVACFG will be default use and load AVA.Cfg. d:> AVA MyAVA.Cfg C:\SF\Work\ * Although you still must include your .Cfg file on the command line when * invoking AVA, it is no longer particular what name you use for the .Cfg file AVA v4.0 -------- February 15, 1991 Sped up modem calling routines - no more call collisions Supports ANSI type embedded color codes in *.Asc textfiles Avatext.Exe utility provided to view customised *.Asc colorcoded textfiles New textfiles: Nocall.Asc; displayed to the caller if unacceptable phonenumber Editnum.Asc; explains why NOT to edit the phonenumber Youare.Asc; displayed if the caller is already verified New Phonenum.Ava format supports 'smart' dialing (does not ask caller how) New Nocall.Num controlfile - numbers or parts thereof that AVA will NEVER call Supports AVATAR code definitions in RemoteAccess 1.00 DORINFO?.DEF file New option to use Direct Screen Writes or BIOS screen writes Corrected Long Distance bug as a result of AVA v3.7 AVA Registration is now $20.00 US Dollars Please read the Ava.Doc, Avacfg.Doc and Register.Ava files for complete info. AVA v3.7 - AVA SF v1.2 ---------------------- Date: January 29, 1991 AVA and AVA SF will now ABSOLUTELY run in Verify Only Mode. Callers failing the verification check be it by misspelling their names or input of an incorrect password will NO LONGER be brought back to your bbs on your dime! If Long Distance calls for verify only or Toll calls for verify only or Verify Only Mode is set to Yes then AVA and AVA SF will act as expected. *** NOTICE *** As of February 1st, 1991 registration for AVA and AVA SF will be $20.00. $15.00 registrations received and postmarked after February 1st, 1991 will require a $5.00 upgrade fee. As usual, your registration is valid for future versions of AVA and AVA SF. Note: A future version of AVA and AVA SF is currently in beta testing by myself and the beta team. Releasing AVA v3.7 and AVA SF v1.2 was necessary due to the severity of the aforementioned situation. Automated Verification Algorithm version 3.06 --------------------------------------------- AVA - QuickBBS compatible ------------------------- Added a routine that will check the telephone number(s) for the existence of 911, 911-, 411 and 411- before the first screen is displayed. If found, the caller will not be able to be verified and is returned to the bbs. Because AVA assumed that the telephone numbers were check against PhoneNum.Ctl, it was thought it not necessary to check the numbers. Com ports 1-4 are now supported (hopefully). If you use the standard irqs for com 3 and 4 then it should work. This has not been through extensive testing. AVA SF 1.01 ----------- Will now run in Verify Only mode. Also added the same above telephone number checking routine. Automated Verification Algorithm version 3.05a ---------------------------------------------- September 1990 AVA SF 1.0, supporting SpitFire BBS systems v3.0, is released. Download or FREQ as AVASF10.Zip. AVA v3.05a reflects changes within the code and squashes an unappealing display screen regarding the choosing of which LD or Toll number AVA will dial. Automated Verification Algorithm version 3.05 --------------------------------------------- August 1990 Changed the algorithm involved with calculating whether or not a long distance or toll caller is in the SysOp defined calling times. This change reflects a reliable way of calculating this. Minor editing changes to AVACFG. This change did not correct an error but was a cosmetic change. Current suggestions being pondered are: Add support for SpitFire BBS Add support for Telegard BBS Your comments and suggestions are always welcomed. Automated Verification Algorithm version 3.04 --------------------------------------------- August 1990 After optimizing the code, the print to local console routine was not operating correctly. Although some of the program's text was not being printed to the local console AVA did operate as it should. This has been fixed. Automated Verification Algorithm version 3.03 --------------------------------------------- August 1990 This version represents a fix in the way AVA interprets users' flags as they are read from ExitInfo.BBS. This should fix the problem with flags not being toggled after verification. A correction was made in the way AVACFG interpreted defining of flags. My thanks to Bruce Bodger for his incredible patience and the time he spent to alert me of those annoying bugs. ;-) Automated Verification Algorithm version 3.02 --------------------------------------------- August 1990 This represents a fix in the command line routine. It was inadvertantly looking for Ava.Cfg in the path you specified on the command line. Automated Verification Algorithm version 3.01 --------------------------------------------- August 1990 The first caller verifier to bring you multiple options, brings you more! New with AVA 3.01 - RemoteAccess Setup and AVA now includes BRUN45.EXE, there have been alot of SysOp's hunting this down on our boards. *** Previous configuration files are not compatible with AVA 3.01 *** To upgrade from an earlier version, copy Ava.Exe and Avacfg.Exe *** into your AVA directory. Delete your old Ava.Cfg file. The most noticable difference with version 3.01 is the optional use of an external file to check for valid numbers. The description and format of this file, Phonenum.AVA, is explained in Ava.Doc. The second noticable difference, is Avacfg.Exe. It has been completely rewritten. I'm sure you will find it easier to edit your Ava.Cfg. Read Avacfg.Doc for information regarding changes and enhancements. Two new options has been added to Ava.Cfg! One option determines whether or not AVA should use Phonenum.Ava to check for valid numbers. The other option determines whether to grant minimum access or deny verification of callers whose telephone numbers were not found in Phonenum.Ava. Many have suggested that they would like to re-word the beginning screen and the 'last chance' screen to suit their needs. You've got it. First.Asc and Second.Asc have been included for your convenience. They must be in the same directory as AVA and be in standard ASCII format. Do not save these files in ansi color format, AVA will color the text if the caller is in graphics mode. You can optionally include a drive\path to your QuickBBS main directory on the command line. Example: C:\QBBS\AVA> Ava Ava.Cfg C:\Qbbs\ Don't forget to include the trailing back slash. AVA now supports free style phone number formats. This is geared towards RemoteAccess systems who are using AVA. AVA will convert a xxx-xxxx into the xxx-xxx-xxxx format that AVA understands by adding the area code you entered in Ava.Cfg. AVA will not perform any conversion on telephone numbers with 11 digits or more. Remember: $10.00 registrations post marked after July 31, 1990 will require a $5.00 upgrade fee. You will be issued a registration number for AVA version 2.1, however. Automated Verification Algorithm version 2.5 -------------------------------------------- May 1990 Added options/features/corrections ---------------------------------- *** Previous configuration files are not compatible with AVA version 2.5 *** To upgrade from an earlier version of AVA, copy Ava.Exe and Avacfg.Exe *** into your AVA directory. Delete your old Ava.Cfg and run Avacfg.Exe. A new configurable option has been added. You can configure the minimum remaining minutes a caller must have before AVA will do the actual dial out. You can disable this feature with 0. The prompt 'Press [Enter] to continue' has been added to every screen that preceeds termination of a call. This deemed necessary for Verify Only mode. The information screen was cleared before callers were able to read it. The SysOp's status line and keys have changed. The SysOp keys are now the Alt + key combination similar to that of QuickBBS/RA SysOp keys. AVA now supports one word names! Pressing [Enter] at most of the menu prompts will print the menu again. This is helpful when returning from Dos or exiting from Chat. Color has been added to Avacfg.Exe. MISC ---- Many RemoteAccess SysOps have made inquiries regarding data file structure compatibilities. AVA was written primarily for QuickBBS 2.6x however, AVA will run fine using RemoteAccess. Setup AVA using a Type 7 Menu command, and no conversion utilities for QuickBBS to RemoteAccess DORINFO1.DEF and EXITINFO.BBS are needed. Please see Ava.Doc regarding RemoteAccess setup. I am not aware of the current data file structures of RemoteAccess and so I will not be of much help regarding such questions. You should be able to get a better response from RA SysOps who are using AVA. Reporting problems ------------------ When reporting problems please include as much information as possible. Pinpointing problems can be done faster and easier if you also include a copy of your DORINFO1.DEF and Ava.Cfg files. Automated Verification Algorithm version 2.3 -------------------------------------------- Added options/features ---------------------- * Previous configuration files are not compatible. You will need to * reconfigure AVA if you are upgrading from a previous version. * Please read AVACFG.Doc and this file thoroughly before upgrading. > 911 and 411 Hard Coded If a caller entered a number of NNN-xxx-xxxx or xxx-NNN-xxxx, AVA would dial your emergency service agency. If you placed 911- or any combination thereof in your Phonenum.Ctl file, QuickBBS WILL still allow it. Therefore, 911 and 411 are now hard coded and AVA will not dial those numbers. > Define dialing prefix You may now use ATDT (tone) or ATDP (pulse) dialing. Refer to Avacfg.Doc for more information regarding this option. > Verify ONLY mode. You may now run AVA in a Verify ONLY mode. This feature is applicable to LOCAL calls. AVA will call and verify callers but will terminate the call after updating the necessary data files. However, not before informing the caller to call back at their earliest convenience or immediately after the call. This option is great for SysOps who run their BBS systems on measured telephone lines. > Long Distance or Toll Calling AVA now supports 3 types of LD or Toll numbers. If a caller answers Yes to '...is this a Long Distance or Toll call?' question, AVA will check the number against the numbers in AVA.Dat. Prior to dialing the number, AVA will present to the caller a list of his telephone number in three formats. The caller will have to choose which number format AVA will use. The format of the phone numbers are as follows: Telephone number entered: (602)951-8534 List presented to the caller: 1) 1-951-8534 2) 602-951-8534 3) 1-602-951-8534 AVA will then dial the chosen number. > Flags With this version, AVA respects current FLAG settings and will not reset them. If there are flags that you want to be reset after AVA verifies a caller then you must set these flags in your Ava.Cfg file. For example, through QConfig, I set bit 1 of Flag A for my new callers. This is so they can access AVA and be verified. I have also set bit 1 of Flag A in my Ava.Cfg file. Upon a successful verification, AVA will reset the flag. Flag A: X------- (In Config.Bbs defined for New Callers) Flag A: X------- (Defined in Ava.Cfg) Flag A: X------- (Menu option flag) After a successful verification the caller's A Flag will be reset: Flag A: -------- Resetting this flag will ensure that on future calls this caller does not have access to AVA. If you rely on security levels instead of flags then it is not necessary to set any of your flags in Ava.Cfg. Refer to FLAGS in Avacfg.Doc. > AVA's own directory AVA can now be run from its own directory. You must however, copy EXITINFO.BBS and DORINFO1.DEF to the directory before running AVA. You must also, copy EXITINFO.BBS and DORINFO1.DEF to your main QuickBBS directory after AVA completes its run and before you re-load QuickBBS. Remove - Ava.Dat packer ----------------------- This utility has been upgraded to allow for a path to your Users.Bbs data file. Please read Remove.Doc for more information. AVACFG 2.3 - Configuration Utility ---------------------------------- AVACFG is NOT compatible with previous versions of AVA or AVACFG. Changes have been made to the input routines. When creating or editing your configuration file, pressing enter at the prompt will use the default value. Messages to me via NetMail -------------------------- Messages regarding AVA recieved by me via NetMail will be moved to the OTW Programming Message Base for others benefit when suitable. Registration Note ----------------- You are hereby granted 30 days to evaluate AVA. If after 30 days you continue to use AVA, registration is required. When registering please use Register.Ava included in the distribution file. January 16, 1990 As of version 2.1a, Remove.Exe has been added to the distribution files. Please refer to Remove.Doc for an explanation and usage of this utility.