Category : BBS Programs+Doors
Archive   : PCBV403.ZIP
Filename : UPGRADE.DOC

PCBVerify 4.0 UPGRADE documentation
-----------------------------------

Use this file only if you are upgrading from PCBVerify 3.1. Also, you may
wish to use the full set of documentation as an additional source of
information. This file is here essentially to help those who are already
fairly familiar with PCBVerify's setup.

Steps to upgrading PCBVerify from 3.10 to 4.0
---------------------------------------------

1 - Back up your old copy of PCBVerify
2 - Upgrade your PCBVTEXT file(s)
3 - Add the 6 lines below to the config line
4 - Change PCBVAL so that it doesn not contain any dial strings


Additions to the PCBV.CNF file: (add to the end)

1 - CallerID file (or N for none)
2 - Status line foreground color [should be 0 for PCBoard]
3 - Status line background color [should be 15 for PCBoard]
4 - Default text foreground color [@X commands override]
5 - Default input foreground color
6 - Error-corrected dial string [ATDT]
7 - Non-error-corrected dial string [AT&Q0DT]

Colors:

0 Black
1 Blue
2 Green
3 Cyan
4 Red
5 Magenta
6 Brown [hi intentity = Yellow]
7 White

Add 8 for bright colors

PCBVAL enhancements/changes
---------------------------

PCBVAL restructured for better number checking -- numbers are checked before
the user is asked to enter long distance flag. If a match is found which
does not require an answer (the field = ?, ?N, or ?Y) then the user is not
asked. If a match is found first which does require an answer (either a Y
or a N) then the user is asked. Afterwards the file is rechecked.

The "ATDT" is no longer necessary in the PCBVAL file -- see the .CNF info
above. A sample PCBVAL file has been included which will handle Knoxville --
the prefixes listed are all the local Knox area prefixes, and the remaining
entries are pretty well self-explanatory.

Here's an example PCBVAL file -- the lines afterward explain how it works.

615-588-????,N,?,A,"%2-%3" ;These are local prefixes, dial as
xxx-xxxx and remain online. Use time
format A. The ? mark (third field)
indicates that the long distance flag
is not needed for numbers matching
this entry.

615-???-????,N,N,A,"%2-%3" ;If it gets this far, and the number
matches this entry, then it stops and
asks if the call is long distance. If
N, this entry is used.

615-???-????,N,Y,B,"1-%2-%3" ;If Y, this entry is used.

800-???-????,N,?Y,A,"1-800-%2-%3" ;800 calls, don't ask, identify on screen
as long distance (the Y forces that).
Use time A, and don't disconnect after
verify.

???-???-????,Y,?Y,B,"1-%1-%2-%3" ;All other calls -- assume long distance,
don't ask. Disconnect after call. Time
format B.

The old system will work, but the "ATDT" strings must be removed from your
PCBVAL file. The ? is the key to activating the "no ask" mode of operation.

Other additions:
----------------

CallerID file = support for Callerid. This file, if exists, is assumed to
contain the user's phone number in the format it would be in PCBVAL. For
example, xxx-xxx-xxxx. If it doesn't exist normal mode is assumed.

DIALOUT = new file, which gives user the last instructions before dropping the
call and dialing his number

COM3/4 support, 115kbaud, proper handshaking for CTS/RTS

REVERIFY mode, allows a user to verify again if security level matches new
user level, even if number is in PCBVVER. If number and name both match, will
allow the call, otherwise will not. Useful for verifying users that have
expired.

"More" prompt improved -- now has (H)elp text, contained in PCBVTEXT for easy
multi-lingual use.

CTRL-X and CTRL-S are supported, local and remote.

Error logging greatly improved.