Category : BBS Programs+Doors
Archive   : AVA40.ZIP
Filename : AVA.DOC

** # # ### ## # # ## ### ### ###
* * # # # # # ## ## # # # # # #
**** # # # # # # # # # #### # ## # #
* * ## # ## # # # # # # ### ###

* * ### ### ### ### ### ### ## ### ### ## # #
* * # # # # # # # # # # # # # ## #
* * ## ### # ## # # #### # # # # # ##
* ### # # ### # ### ### # # # ### ## # #

** # ## ## ### ### ### # # # #
* * # # # # # # # # # # ## ##
**** # # ## # # ### # # #### # # # #
* * ### ## ## # # ### # # # # # #
and
Automated Verification Algorithm SF

The SysOp's Answer to Caller Verification
(c) 1989, 1990, 1991 by Cat Miller


This program is supported by:
Cat Miller
Off-The-Wall Programing
13610 N. Scottsdale RD. STE 146
Scottsdale, Arizona 85254


Documentation by Cat Miller and Geoffrey Booher






























TABLE OF CONTENTS
=================


PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Files and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Configurable options. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Installing AVA - QuickBBS . . . . . . . . . . . . . . . . . . . . . . . . 7
Installing AVA - RemoteAccess . . . . . . . . . . . . . . . . . . . . . . 8
Installing AVA - SpitFire . . . . . . . . . . . . . . . . . . . . . . . . 8
Batch File for QuickBBS . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring AVA . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Optional Command Line Parameter . . . . . . . . . . . . . . . . . . . . .11
Phonenum.Ava - External file. . . . . . . . . . . . . . . . . . . . . . .12
NoCall.Num - External number checker. . . . . . . . . . . . . . . . . . .14
External text files - Ansi codes. . . . . . . . . . . . . . . . . . . . .15
AVAText.Exe - The Utility. . . . . . . . . . . . . . . . . . . . . . . . 15
SysOp Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
From the Beginning. . . . . . . . . . . . . . . . . . . . . . . . . . . .17
From the Beginning (cont) . . . . . . . . . . . . . . . . . . . . .18
Derrors.Txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Registration (cont) . . . . . . . . . . . . . . . . . . . . . . . .21
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Gratitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
cont . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25






































PREFACE


Disclaimer
----------

Automated Verification Algorithm and its utilities is provided AS IS, without
warranty of any kind, expressed or implied. In no way shall OTW Programming
or Cat Miller be held liable for any damages by use or misuse of the
forementioned program and utilities. Your use of these programs imply your
acceptance of these terms and you will bear full responsibility.






















































Page 4





Introduction
------------

AVA is an acronym for Automated Verification Algorithm. It is a SysOp
utility designed to call back and verify first time callers. The time
spent voice validating every caller can be very consuming. Since most of us
are computer hobbyists time is something we'd rather spend tinkering instead
of dialing.

AVA is very flexible and can be customized to suit your needs by way of the
many configurable options. These options are covered in detail in Avacfg.Doc.

User friendliness are the key words. AVA is straightforward and doesn't
utilize coined computer words or phrases. A neophyte doesn't need the added
confusion brought upon by a simple task such as validation. The minimum key
strokes expected from a caller are five. AVA is simple yet powerful.

SysOps can expect the same user friendliness. The configuration utility is
menu driven. This alleviates all of the hassles of putting together another
configuration file with your word processor.

AVA was written with QuickBasic 4.5. A 'DTR' patched version of BRUN45.EXE,
the external run time library, is included for AVA to run. We decided to
distribute it with AVA because many SysOps were complaining about locating
it. Place the Brun45.Exe file somewhere in your DOS path.

AVA has been tested on many computers, however there are a few requirements.

o QuickBBS 2.xx, RemoteAccess 0.xx or 1.00, SpitFire 3.0
o An IBM PC, AT or 100% BIOS compatible
o Hayes compatible asynchronous modem
o CGA card/monitor
o DOS 3.x or greater













Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 5





Files
-----

The following files were distributed in the .ZIP archive:


Ava.Exe............................The Main AVA Program
Ava.Doc............................This documentation text file
Avacfg.Exe.........................AVA Setup utility
Avacfg.Doc.........................Documentation for above
Avadat.Doc.........................Structure for Ava.Dat file
AvaText.Exe........................Preview utility for *.Asc files
Remove.Exe.........................External Ava.Dat utility *
Remove.Doc.........................Documentation for above *
Phonenum.Ava.......................Sample Phonenum.Ava control file
Register.Ava.......................Registration Form to register AVA
NoCall.Num.........................List of non-callable areacodes/prefixes
Thelist.Ava........................List of registered AVA SysOp's
Question.Ava.......................Common questions from SysOp's about AVA
Whatsnew.Ava.......................Notes on changes with AVA by version
Brun45.Exe.........................QuickBasic Runtime Module required
ErrCodes.Txt.......................List of error codes
SFBat.Doc..........................Included with SpitFire version

External configurable text files:

First.Asc..........................Opening screen displayed to caller
Second.Asc.........................Final screen displayed before calling
NoCall.Asc.........................Displayed if number found in NoCall.Num
YouAre.Asc.........................Displayed to already verified callers
EditNum.Asc........................To explain why NOT to edit phonenumber















Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 6





Configurable options and features
---------------------------------

Long distance or toll calling
Grant minimum access to long distance or toll callers
Edit phone numbers before calling
Verify duplicate phone numbers
Long distance calling for verification ONLY
Toll numbers calling for verification ONLY
Run AVA in Verify Only Mode
* Daily download byte limit for both minimum and verified access
Daily time limit for both minimum and verified access
* All four FLAGS, A, B, C and D are supported. Previous settings
respected.
Long distance or toll calling during specified times ONLY
Recognizes local calls even if area code differs
Modem handshake support
Supports baud rates from 300 to 38400 (locked or unlocked)
ATDT or ATDP dialing
Define minimum minutes remaining before AVA will dial out
Formats 'free-style' phone numbers
Specify path on command line
Optional external file to check for valid area code and prefixes
Define phone numbers and combination of numbers that you will
absolutely NOT call
Display screens
Embed ansi codes
* Recognizes RemoteAccess 1.00 AVATAR flags in Dorinfox.Def
...and more!

* Not supported by SpitFire systems















Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 7





Installing AVA - QuickBBS
-------------------------

Use a TYPE 15 menu option to run AVA with QuickBBS. Please refer to your
QuickBBS documentation regarding this kind of menu setup. The following
files must be present in the same directory as AVA.Exe:

Ava.Cfg
PhoneNum.Ava (optional)
First.Asc
Second.Asc
YouAre.Asc
NoCall.Asc
EditNum.Asc (optional)

AVA and its associated files need not be run from your main BBS directory.
You can use the optional drive\path command line parameter which will be
explained later. For simplicity sake, this documentation will illustrate the
installation of AVA in your bbs main directory. AVA utilizes Phonedup.Log
and Phonenum.Ctl so specifying a path to your bbs main directory is necessary
if you intend to run AVA from its own directory. For further information
about Phonedup.Log, Phonenum.Ctl please refer to your bbs documentation.

After you have set up your TYPE 15 menu option, set the errorlevel in which
to exit with, you need to add this to your QuickBBS or front end mailer
batch file. See the batch file example for QuickBBS on the following page.

Note: AVA has been successfully setup with SuperBBS. Use the QuickBBS setup
directions for use with SuperBBS.

















Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 8





Installing AVA - RemoteAccess
-----------------------------

Use a TYPE 7 menu option to run AVA with RemoteAccess. RemoteAccess *M
can swap all but 20k of RA out of memory to disk. RA creates both
DORINFO1.DEF and EXITINFO.BBS with a TYPE 7 exit, and rereads both files
upon return (unlike Quick) so using a TYPE 7 with RemoteAccess is the
recommended method. TYPE 15's are not needed with RA.

Using a TYPE 7 menu option, the AVA command would be entered like this:

Optional Data: Ava.Exe Ava.Cfg *M

That's all there is to it. Note: DOOR conversion utilities that are
available to convert QuickBBS to RA and back to QuickBBS are *NOT* needed.

Also, RemoteAccess TYPE 7 installation eliminates the need for a batch file
to run AVA.


AVA 4.0 will also recognise the new AVATAR codes in DORINFO?.DEF for
RemoteAccess 1.00. If the caller has AVATAR ONLY selected, they will be
shown an ASCII screen. If the caller has ANSI and AVATAR selected, they
will be shown the ANSI screens. A future version of AVA will support
AVATAR display screen codes.





Installing AVA - SpitFire
-------------------------

AVA can be run as a Door or menu extension. Please refer to your SpitFire
documentation for installation information.











Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 9





Batch File for QuickBBS
-----------------------

Echo Off
Cls
Echo ***** Loading QuickBBS Now *****

:Start
QuickBBS -E0

:After_Quick
If Errorlevel 10 Goto AVA
If Errorlevel 9 Goto RightHere
If Errorlevel 8 Goto Somewhere
If Errorlevel 0 Goto Start

:AVA
Ava Ava.Cfg <--- Configuration filename supplied on the command line
Goto Restart

:RightHere
Rem - Doing something here

:Somewhere
Rem - Do something else here

:Restart
QuickBBS -R -E0
Goto After_Quick

For this example an ErrorLevel 10 signifies the use of AVA. Control will
resume at the label :AVA. When AVA is completed the batch file jumps to the
label Restart to reinstate the bbs. Note, labels ARE case sensitive!

Of course your batch file will be different.











Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 10





Configuring AVA
---------------

AVA requires a configuration file. The filename must be supplied on the

command line. Example:

D:\> Ava Ava.Cfg

Detailed information on the various configurable options are covered in
AVACFG.DOC. They will not be covered in this documentation.




































Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 11





Optional Command Line Parameter
-------------------------------

You can specify a drive\path to your bbs main directory. This allows you to
run AVA from its own directory. If a FULL drive\path is not specified, AVA
will default to the current drive\directory.

Examples:

Loading and running AVA specifying a path:

D:\QBBS\AVA> Ava Ava.Cfg D:\Qbbs\

) The ending backslash is required when specifying a path

Loading and running AVA without specifying a path:

D:\QBBS> Ava Ava.Cfg


SpitFire systems:

If you intend on running AVA from its own directory, then you will need to
copy the appropriate *.Dat to your AVA directory prior to running AVA.
When AVA returns control to you batch file, copy the .Dat back to its
original directory. This is so SpitFire will read the updated .Dat file
prior to running itself.

Sample SpitFire batch:

:AVA
Copy C:\SF\SFDoors.Dat
AVA AVA.Cfg C:\SF\Work\
Copy SFDoors.Dat c:\sf

This also holds true if you intend on running AVA from a SFSEC.Bat file.










Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 12





PhoneNum.Ava - External file
----------------------------

AVA will optionally use an external ASCII file known as Phonenum.Ava to
check for valid phone numbers. Valid phone numbers are numbers that AVA
will call and verify. You can create this text file with your text editor.

PhoneNum.Ava uses its own keywords and format. The keywords are Local, Toll,
LD and End. The use of these keywords help in AVA's calling decisions as
well as create a more descriptive and informative log file.

PhoneNum.Ava will use by default the following number formats:

Local numbers: xxx-xxxx
Toll numbers: 1-xxx-xxxx
LD numbers: 1-xxx-xxx-xxxx

The format of PhoneNum.Ava follows:

File: Phonenum.Ava

; Text following a semi colon are ignored. Use the semi colon for
; comments. Entries must follow the format of this example. Local phone
; numbers are entered first then Toll and LD phone numbers.
; calling area.
Local ; Local keyword to signify local phone numbers
602-951- 951- ; Areacode-prefix followed by dial string
602-788- ; No dial string will default to Local format xxx-xxxx
Toll ; Toll keyword to signify toll phone numbers
602-342- 1-602-342- ; Areacode-prefix followed by dial string
602-587- ; No dial string use default: 1-xxx-xxxx
LD ; LD keyword to signify long distance phone numbers
808- ; No dial string use LD default 1-xxx-xxx-xxxx
LD ; OR
808-623 1-808-623 ; Use 1-808-623 to call this number
End ; End of list - must be the last entry in the list

Since PhoneNum.Ava is read in order, the first matching sequence is what is
used. When a match is found, AVA will use the associated dial string to
call or if there is no associated dial string, AVA will use the predefined
default. So long as you define a dial string, AVA will use it. If no match
is found, AVA will act according to its associated option as found in Ava.Cfg.




Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 13





PhoneNum.Ava (cont)
-------------------

Since the function of PhoneNum.Ava is to determine whether the caller is a
local call from your system, you should include all of your local area
codes and prefixes.

If you do not plan to support Toll or LD calls, then it is not necessary to
include those keywords in PhoneNum.Ava.

Selectively omitting numbers from Phonenum.Ava will ensure that those numbers
will not be called.

Phonenum.Ava must reside in the same directory as AVA. If you do not wish
to use this method of checking phone numbers, AVA will ask the caller if
he is a local call. However, AVA will check the phone number using its
internal checking processes regardless of the answer.

Do not include remarks after a dial string. The remarks you see here are
there for your benefit only.

A sample PhoneNum.Ava is included with the distribution archive.
























Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 14





NoCall.Num - External number checker
------------------------------------

NoCall.Num is an ASCII file containing portions of or entire telephone
numbers which you will absolutely not call. What makes this different from
PhoneNum.Ava is that the caller's phone number(s) is checked prior to the
display of First.Asc. If the caller's number is found in NoCall.Num, AVA
will not proceed with verification but instead will display NoCall.Asc and
return the caller to your bbs.

If your system supports home and data phone numbers then AVA will check both
numbers against the entries in NoCall.Num. If one of the numbers is found,
then it will be ignored and AVA will use only the valid number.

The syntax for NoCall.Num is different from PhoneNum.Ava. NoCall.Asc uses
the x as a mask. Valid entries would be:

xxx-911-
xxx-411-
xxx-976-
111-
000-
333-
602-951-8534

As you can see, you can use portions of a number or include the entire
number. It wouldn't be a bad idea to include your bbs number, police
station, fire department or any combination.

Do not include remarks in this file. They will be treated as valid entries.

A sample NoCall.Num is included with the distribution archive.














Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 15





External Text Files - Ansi codes
--------------------------------

The use of external text files allow you to customize the instructions and
information according to your setup. AVA now supports the use of embedded
ansi codes. The external files, First.Asc, Second.Asc, YouAre.Asc and
NoCall.Asc must be in the same directory as AVA. A fifth and optional
text file, EditNum.Asc should also be in the same directory if you intend
on supporting the editing of phone numbers.

The ~ symbol is what alerts AVA to the presence of an ansi code. You must
preceed each numeric code with this symbol. Due to its limitation, you
cannot use ~ anywhere else in your text file. This will be corrected in
a future version.

The following is a list of codes recognized by AVA:

~01 Blue ~09 Bright Blue
~02 Green ~10 Bright Green
~03 Cyan ~11 Bright Cyan
~04 Red ~12 Bright Red
~05 Magenta ~13 Bright Magenta
~06 Brown ~14 Yellow
~07 White ~15 Bright White

Included is a little utility AVAText.Exe which will display on the local
console your .Asc file. This utility is helpful when creating your
screens. It will ensure that you have your screens just the way you want
them. AVAText can be envoked directly from DOS or supplied with a
filename, ie:

d:> AVAText First.Asc

AVAText will instantly display First.Asc. If no filename was supplied on the
command line then you will be prompted for a filename.

These external files are included in the archive as examples or they can be
used as is.








Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 16





SysOp Commands
--------------

The options available to the SysOp while a caller is online are:

ALT + C Chat
ALT + H Hangup the caller
ALT + J Jump to DOS
ALT + L Lock out caller
ALT + R Return caller to BBS
HOME More help
END Normal Window
Cursor UP Add 1 minute to caller's time
Cursor DOWN Subtract 1 minute from caller's time

Chat
----
Online chat has word wrapping. However, the caller's online time is still
affected while in chat. Press [Esc] to exit chat and return to AVA.

Hangup the caller
-----------------
This is a true twit key. That is, DTR is dropped thereby disconnecting the
caller from AVA and your BBS. AVA will sense the loss of carrier and
graciously return control to your BBS. A twit is a twit. This option works
only if there is a caller online.

Jump to DOS
-----------
This is your Shell to DOS key. To return to AVA type EXIT at the dos prompt.

Lock out caller
---------------
The ALT + H taken a degree furthur. This will zero out the caller's security
level and hangup the caller.

Return caller to bbs
--------------------
This will promptly bring the caller back to your BBS. This works whether
or not there is a caller presently online.






Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 17





From the Beginning
------------------

AVA retrieves the phone number(s), security level and password from
EXITINFO.BBS or SFDoors.Dat for SpitFire systems. The phone number(s) and
security level are checked. AVA will not accept callers whose security
levels are greater then the minimum access securtiy level and lower then the
SysOp's security level as defined in your configuration file. If this is
found to be true, the contents of YouAre.Asc is displayed to the caller then
is return to your bbs. AVA will also compare the caller's phone number(s)
with that which you have defined in NoCall.Num. If there is a match, AVA
will display to the caller the contents of NoCall.Asc and return the caller
to your bbs.

Once the caller gets past this check, the first text screen, First.Asc, is
displayed to the caller. It should inform the caller what he can expect
from AVA and what AVA expects from the caller. Please keep this in mind
when editing First.Asc. This file is provided in the distribution file. You
may use this as an example or use it as is.

After reading this screen, the caller is prompted to whether or not he wants
to proceed with the verification. Depending on the caller's reply he will
either be returned to your bbs or proceed with the verification.

If your system requires both the home and data phone number from the caller,
then AVA will ask which one to call. If you have configured AVA so that
callers may edit their phone numbers, it will then ask if he wishes to edit
the phone number. If the caller successfully edits the phone number, both
the edited number and the original number is written to AVA.Log. The caller
is given 2 chances to edit the number. After the second attempt the caller
is returned to the bbs.

Second.Asc is the last screen the caller sees before AVA disconnects. As
per the example included in the distribution file, it is the 'last chance'
screen and is used to remind the caller to use ATA to answer the phone, etc.
You can edit this file as you wish.










Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 18





From the Beginning (cont)
-------------------------

Once connection is re-established AVA will clear its buffers, synchronize the
modems and announce itself to the caller. At this point the caller is
expected to answer 2 questions. The first question asks for the caller's
first and last names and the second question asks for his password. The
password entry is masked. That is, *'s are echoed to the remote screen while
what is actually typed is echoed to the local screen.

The caller will have 2 chances each to answer both questions. If either one
of the questions are not answered correctly, verification will fail.

After successfully answering both questions the new security level, download
byte limit and flags A, B, C and D will be written to EXITINFO.BBS. This is
where QuickBBS retrieves its information upon returning from a TYPE 15 exit.
The caller is returned to the BBS, verified and with a higher access level.

For SpitFire systems AVA will update the appropriate .Dat and SFUsers.Dat.
If you will be using AVA in it's own directory, you will need to copy
the appropriate .Dat from the AVA directory to your bbs directory so that
SpitFire will read in the updated caller information.

AVA keeps a log of activities in the file AVA.LOG. This file keeps a running
record of what occurred and did not occur during the verification process.
The log is appended to each time AVA is accessed. You can delete it when it
becomes too large.

In addition, AVA accesses Phonedup.Log and Phonenum.Ctl. If for some reason
a duplicate phone number was not detected by QuickBBS it will not be written
to Phonedup.Log. However, AVA also maintains an external data file called
Ava.Dat. The caller's name, phone number and time\date of verification is
stored in this file. AVA also checks this data file for duplicate numbers.













Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 19





Derrors.Txt
-----------

AVA will create or append a file called Derrors.Txt whenever it encounters
an error. Loss of carrier is also treated as an error and will be noted in
this file. If you are experiencing trouble setting up or running AVA more
than likely it will be listed in Derrors.Txt.

You should delete this file as it becomes unwanted.





































Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 20





Registration
------------

You are hereby granted permission to evaluate AVA for 30 days. After this
evaluation period a $20.00 registration fee is required. If you do not plan
to register, then remove AVA from use.

Upon receipt of your registration fee, a serial number will be issued to you.
Use this serial number to register your copy of AVA with AVACFG. Once you
have registered your copy you will no longer see [Evaluation] [Copy]. When
AVA is operating you will see your FULL serial number in the upper right hand
portion of your screen. When seeking help, comments or suggestions please
include your FULL serial number.

Please use the file Register.Ava to send in your registration information.

Send your information, plus $20.00 check or money order (US Funds) to:

OTW Programming
c/o Cat Miller
13610 N. Scottsdale RD STE 146
Scottsdale, AZ 85254

Please make checks or money order payable to Cat Miller.






















Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 21





Registration (cont)
-------------------

Your registration number is generated based on the bbs name as well as the
SysOp's name. If you change your name or your bbs name, then you will need
to aquire another registration number. To do this, you must supply your
previous information and your 'old' registration number. Also, include
your new information. If you do not supply your 'old' registration number
then the request will be ignored. This is for your protection only.

Your registration number is valid for future versions of AVA unless otherwise
noted. The cost of registration is subject to change without notice.

Due to the increasing flow of netmail regarding AVA, it has become necessary
for me to place your replies on hold. If you have sent netmail and expect a
reply, you may begin polling my system for a reply after 48 hours.


Non $20.00 registrations postmarked after February 1st, 1991 will require a
$5.00 upgrade fee.


























Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 22




Support
-------

Updates and or new releases of AVA can be downloaded or file requested from
the support board, The Alternate Choice, 114/39, (602)951-8534,
300/1200/2400 and 24 hours a day. The magic filename: AVA will get you the
latest version.

If you are installing AVA for the first time I will offer assistance.
You may leave your questions, comments and suggestions to Cat Miller if I
am not available for chat.

If you are experiencing problems, you need to be exact with your description
of the problem. Include as much detail as possible such as computer hardware,
TSR's, fossil driver, your AVA configuration, a listing of your Derrors.Txt
file and so forth. This kind of detail will help tremendously in tracking
down the problem.

You may also contact the following Support Systems for assistance.

* AVA Distribution/Support System *

SysOp: Geoffrey Booher
BBS: The Gateway Net BBS - a FrontDoor/RemoteAccess System
14.4 HST / 14.4 V.32bis / 9600 V.32 / V.42bis
FidoNet: 1:11/233
Number: (815)233-5008 23 hrs. Freeport, IL - USA
Comments: FREQ magicname: AVA for the latest version
QuickBBS, RemoteAccess, SuperBBS support USA

* AVA SF Distribution/Support System *

SysOp: Russell Mikami - SpitFire System
BBS: The Hawaiian Hawke BBS - a SpitFire system
9600 V.32 / 14.4 HST
FidoNet: 1:114/67
Number: (602)272-4887 24 hrs. Phoenix, AZ - USA
Comments: Fido netmail - SpitFire support









Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 23





Gratitude
---------

Geoffrey Booher for his comments and suggestions for version 1.0 and
later. He has been very instrumental in the release of version 4.0 as well
as the release that is soon to follow.

Bob Lucas for his comments and suggestions for version 1.1f and earlier.
Also for his willingness to beta test version 2.0.

Travis Smith for his willingness to beta test version 2.0.

Todd DolBeer for his patience and support in testing and correcting an
oversight in the modem routine.

Lance Alexander for his help in beta testing AVA.
His is reachable at Cactus Quick Net 7:800/9

Jason Harper for his help in beta testing AVA.
His is reachable at 114/46.

Bruce Bodger for his help in corrections/fixes to AVA.
He is at The Truckstop BBS - 1:170/400


Acknowledgements
----------------

QuickBasic 4.5 a product of MicroSoft.
QuickC com library used by AVA is written and developed by Jeff Sumberg.
RemoteAccess is a product of Continental Software.
QuickBBS 2.6x is a product of the QuickBBS Group.














Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 24





Appendix A
----------

Currently we are using a US Robotics MicroLink 2400. The dip switches on my
internal modem are set as follows:


1 2 3 4 5 6 7 8 9 10
OFF ON OFF ON ON OFF OFF ON OFF ON


Switch # Description
-------- -----------
1 Data terminal ready override
OFF = DTR Normal; Pin 20 controls modem
ON = DTR is always on

2 Verbal, numeric result codes
OFF = Verbal (word) messages
ON = Numeric result codes

3 Result code display
OFF = Quiet mode, no display
ON = Result codes displayed

4 Modem echo
OFF = Modem echoes commands sent from keyboard
ON = Modem does not echo

5 Auto Answer
OFF = Modem answers on first ring
ON = Auto answer suppressed

6 RS-232 Carrier Detect Pin
OFF = Pin 8 controls carrier detect
ON = Carrier detect signal is always on

7 Single/Multi-line installation
OFF = Single phone
ON = Multiple phones






Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller















Page 25





cont
----


8 AT command set recognition
OFF = AT command set disabled
ON = Normal operations


9 Escape Code Operations
OFF = Modem disconnects when +++ is entered.
ON = Modem returns to command state when +++ is entered.


10 Volume control
OFF = Low volume
ON = High volume


AVA lowers DTR to disconnect the remote caller. Your modem must respect this.
If you leave DTR ON the caller will never be disconnected and AVA will try
desperately to lower it. After a certain amount of time the program will
terminate and verification will not be performed. The desired Hayes AT
commands to have are &C1 - software controls carrier detect and &D2 -
software controls data terminal ready. AVA will not work properly if the DCD
and DTR are FORCED on.




















Automated Verification Algorithm (c) 1989, 1990, 1991 by Cat Miller