CBVTAG.EXE - Call back verifier for T.A.G. 2.7
(c) Copyright 1993,1994 by Mark McKay,
The Skeleton Closet BBS (Mark & Debbi McKay sysops),
1:275/138,139,140 (804-671-8547,804-499-5150,804-473-2217)
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Disclaimer/Legal Stuff ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
Although this program has been tested, this software has no warranty,
either expressed or implied. The use of this software is at the user's own
risk. Mark McKay shall in no way be responsible for any special, incidental,
consequential or other damages resulting from the use and/or misuse of this
software. Every effort has been made to test this software and its
documentation for possible errors, but no guarantee to that effect is made.
There are no written or implied guarantees of updates to this program.
This program must be distributed AS IS in it's original archive. This
program may not be distributed as part of any other software package without
the expressed written consent of the author, Mark McKay. It may not be
altered or reverse engineered in any way, shape or manner.
The usual I don't promise it will do anything and if it messes up/you mess
it up, you own the pieces. If you use it, you alone are liable for the
results.
There are no promises either expressed or implied of updates to this
program.
This program has the ability to make Long Distance phone calls. The author
"Mark McKay" is in no way liable for the results of the use/misuse of this
program in regards to your phone bill even if it it is the result of a
programming error on my part. Your use of this program relieves the author
of any liability in this regard.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Features ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
- Can optionally Make Long Distance call backs
- Checks for duplicate user names, addresses, phone numbers.
- Checks for illegal characters in User names.
- Can optionally allow users to change the phone number they are calling
from
- Can Update TAG Security Levels, AR and SF Flags
- Can optionally only call a number once (ie checks to see if another user
has used that number to call)
- Can hangup on Long distance callers shortly after call back
- Can hangup on Local callers shortly after call back
- Redial tries are configurable
- Password tries are configurable
- Time to wait for the modems to connect is configurable
- Time between calls is configurable
- SL and DSL to need to use the door is configurable
- You can give LD callers a special SL & DSL
- You can configure the SL that needs to use the door
- You can configure the AR & SF flags to give validated users
- Modem init string is configurable
- Supports non-standard dial out prefixes
- Long distance prefix is configurable
- Can use more than one area code as a local call
- Considerable phone number checking
- Uses a bad number file to not call a user
- Send User#.msg to configurable user
- Sends configurable Fido, Hudson or JAM style email to users
- Gives the user several chances to quit the door.
- Sysop can abort call back
- Has a tutorial for users to practice a callback before the actual
callback.
- Desqview aware
- Share aware
- Multi node compatible
- Has separate configuration files for each node (up to 99 nodes)
(Now supports multiple different modems running the same .EXE file)
- Doesn't let locked out users validate with a different Handle.
- Allows user to use Voice number, Data number or Extra number from TAG.
- Checks to see Area Code to State given on logon to check for untruthful
users.
- Supports local calls in other Area Codes for those who border other states/
provinces/area codes by dialing either prefix and full number or the same
as a local call depending on how calls are handled by your phone company.
If this applies to you ask your phone company so that you won't do it the
wrong way and get charged LD rates for local calls.
- If the user is in the same area code but CBVTAG says the number is Long
Distance, CBVTAG allows the user to try to have CBVTAG call them. This
makes only a local call. The worst that will happen is that you will get
your configured redial tries worth of phone company "Number is LD"
recordings. If the number really is local then CBVTAG will automagically
add it to CBVTAG.LOC so future users will be seen as local.
- As of v3.0 uses TAG validation flags if set or else uses defaults setup
in the configuration.
- As of v3.0 can optionally check for dupe phone numbers, real names and
addresses.
- As of v3.0 only active and locked out user records are checked for
dupes.
- And much, much more!!!
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Limitations ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
- You MUST use a fossil driver such as BNU or X00. CBVTAG has been tested
successfully with BNU v1.70 and X00 v1.49 & v1.50. As of version 2.35
CBVTAG has added DESQVIEW support in the Comm routines for X00 users
that was supplied with X00 by Ray Gwynn.
- Versions of CBVTAG prior to 2.35 occasionally had CTS errors with "some"
modems. This should be fixed now.
- CBVTAG only supports COM1 through COM4 with standard addresses.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Quick Notes ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
These docs are fairly long, but hopefully not that complex. This door is
not a simple 2 minute setup although I have tried to make it as simple and
as user friendly as possible.
To get the wanted results please read the entire doc file (printing it out
is recommended) and set the program up "per the docs". I have tried to
not get overly verbose but have probably gone into too much detail in some
instances.
Please read the entire doc file before contacting me with questions/comments
that may be spelled out below.
┌────────────────────────────────────────────────────────────────────────────┐
│ | | | | | | | | | | │
│ | | | | | | | | | | │
│ \|/ \|/ \|/ \|/ \|/ \|/ \|/ \|/ \|/ \|/ │
│ ┌──────────────────────────────────────────────────────────────────────┐ │
│ │ FIRST TIME USERS!!! │ │
│ │ NOTE : You must make a NEW directory for CBVTAG to live in. │ │
│ └──────────────────────────────────────────────────────────────────────┘ │
│ /|\ /|\ /|\ /|\ /|\ /|\ /|\ /|\ /|\ /|\ │
│ | | | | | | | | | | │
│ | | | | | | | | | | │
└────────────────────────────────────────────────────────────────────────────┘
I didn't forget to tell you this time! <grin>
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Brief Description ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
CBVTAG is full-featured Call back verifier for T.A.G. 2.7 and is hopefully
the best working CBV around for T.A.G., and I believe it offers more
features than any others that I have seen. For ANSI users, it is colorful
so the user won't be bored to death while using it. <g>
It also includes my "CKLOGON" door ("built in" with minor bug fixes) that
checks for duplicate user information (Real Name, Address, Phone numbers).
I no longer have anything to do with my Remote Access BBS callback verifier,
MC_CBV. I just wrote the original program.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Setup ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
The Configuration Program - CBV_CFG.EXE
---------------------------------------
CBV_CFG now has one commandline parameter, the node number of the
configuration file to edit. If none are specified the CBVTAG1.CFG
will be edited automatically.
CBV_CFG tells you "which" node configuration file it is editing (for
those with short memories like myself).
Examples:
1. CBV_CFG 1 or CBV_CFG will edit CBVTAG1.CFG, Node 1's Config file.
2. CBV_CFG 2 will edit CBVTAG2.CFG, Node 2's config file.
3. CBV_CFG 3 will edit CBVTAG3.CFG, Node 3's config file.
4. CBV_CFG 4 will edit CBVTAG4.CFG, Node 4's config file.
5. CBV_CFG 5 will edit CBVTAG5.CFG, Node 5's config file.
etc.....
Run CBV_CFG and answer/fill in all the fields for all of your nodes. It
should be pretty self explanatory as to what things are. There is a long
description of what each thing does on the bottom line in the config
program.
NOTE: In the Modem init string you MUST at least use verbose result codes
from your modem. ("ATV1" Hayes AT command i.e. after you type the
ATZ command and hit enter it comes up "OK" and not "0")
Sample init strings:
US Robotics Courier HST 14.4k Dual Standard : ATZ
US Robotics Courier HST 14.4k V42bis : ATZ
Generic 2400 Hayes compitable modem : ATZ
Hayes Accurra 144B+FAX144 : ATE1Q0V1X4&C1&D2
Note that the "|" symbol is not needed on the end of the init string.
CBVTAG while add it automagically when sending a command to the modem.
If you have a modem other than those listed above, I would appreciate if
you would please netmail me with your Modem init string "if" ATZ didn't
work for you. I will add it to these docs to help other sysops setup
CBVTAG for TAG in the future, giving you credit where due.
Available Options in CBV_CFG
----------------------------
1. "BBS Name" - The Name Of Your BBS
2. "Sysop Name" - The Sysop's Name
3. "BBS Location" - The Location of Your BBS
4. "Make LD Calls" - Should the CBV Make Long Distance Calls? Yes/No
5. "Change Number" - Should The User Be Allowed To Change His/Her
Phone Number? Yes/No
6. "Make Bulletin" - Should The CBV Make A List Of Users Don't Use
The CBV correctly? Yes/No
7. "Fix Security" - Should The CBV Upgrade SL & DSL Of Users
completing verification? Yes/No
8. "Let LD Back" - Should the CBV Let The User Back To The BBS
After A LD Call? Yes/No
9. "Let Loc. Back" - Should the CBV Let The User Back To The BBS
After A Local Call? Yes/No
10. "Use AC if Loc" - Dial Local Call in Different Area Code how?
(Y=X-XXX-XXX-XXXX, N=XXX-XXXX)
11. "Lock Fossil?" - Is your fossil driver locked at a particular
baud rate.
12. "Check Names" - Should The CBV Check For Duplicate Names?
Yes/No
13. "Check Address" - Should The CBV Check For Duplicate Addresses?
Yes/No
14. "Check Phone Numbers" - Should The CBV Check For Duplicate Phone
Numbers? Yes/No
15. "Dorinfo Path" - Path to Dorinfo#.Def.
16. "User.Lst Path" - Please Enter The Path to Your User.Lst
17. "MBoards Path" - Please Enter The Path to MBoards.Dat file
18. "Redial Tries" - How Many Times Should The CBV Try to Call The
User? (0-99)
19. "Password Tries" - How Many Tries Should The User Get To Enter
Their Password? (0-99)
20. "Carrier Delay" - How Long Should The Modem Wait to Connect Fully
(30-45 sec. recommended)
21. "Redial Pause" - How Long Should The Modem Wait Between Call
Attempts
22. "Validated SL" - What SL Should A Successful Callback User Be
Given
23. "Validated DSL" - What DSL Should A Successful Callback User
Be Given
24. "LD SL" - What SL Should A Long Distance Caller Be
Given (If no LD calls)
25. "LD DSL" - What DSL Should A Long Distance Caller Be
Given (If no LD calls)
26. "SL To Not Use" - What SL Must A User Have To Not Need To Use
The CBV
27. "File points" - How many file points should a New User be
given (0-65535)
28. "Netmail Credit" - How much netmail credit should a New User be
given (0-65535)
29. "Time Bank" - How much time should a New User be given in
their Time Bank (0-65535)
30. "AR Flags" - What AR Flags Should A Successful User Be
Given
31. "SF Flags" - ALL Special Flags A Successful User Should
Have Given (A-O)
32. "Modem Init." - Enter Your Modem Initialization String
(Normally ATZ will work fine)
33. "Dialing Prefix" - Prefix to Add For Your Modem To Dial A Phone
Number (Normally ATDT)
34. "Comm Port" - Which comm port is the modem for this node on?
35. "LD Prefix" - Prefix to Add For Your Modem To Dial A Long
Distance Number (Normally 1-)
36. "LD Val Flag" - Validation Key to Give LD callers if CBVTAG
set not to dial LD numbers.
37. "Good Val Flag" - Validation Key to Give ALL callers who use
CBVTAG successfully.
38. "Sysop User #" - User Number To Send "Sysop" EMail & Messages
To
39. "Use AC on all" - Should the CBV Keep the Area Code on *ALL* LD
Numbers? Yes/No
40. "Access Days" - Days Online To Give LD Callers If CBV Set Not
To Call LD (0 = Don''t Care)
41. "LD Access Days" - Days Online To Give Local Callers For Successful
Callback (0 = Don''t Care)
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Command Line Parameters ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
NOTE: From version 2.2 on, CBVTAG has new commandline parameters
There are a lot less command line parameters now!!
Here they are (they are NOT case sensitive and can have a "-" or a "/"
preceding them) :
Example : if parameter is "X" then -X,/X,-x and /x will all work.
N : Node using the CBV (always 1 for single node) [ TAG's %9 ]
C : Connect rate (actual baud rate of caller) [ TAG's %8 ]
R : Real Connect rate (locked baud rate of caller) [ TAG's %1 ]
U : User number of the user. [ TAG's %3 ]
These may be in any order but you MUST use them all!
Example: CBVTAG /N%9 /C%8 /R%1 /U%3
You must use all 4 for the door to work.
CBVTAG is Share and Desqview aware and is fully multi node/multiline
capable. You only need to run one (1) copy of CBVTAG.EXE regardless
of how many nodes you run. Just make sure that you get the configuration
files entered correctly for each node.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Running CBVTAG from TAG ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
NOTE : IF YOU HAVE MORE THAN ONE AREA CODE THAT IS A LOCAL CALL LINE #1
OF CBVTAG.LOC MUST BE ONE WITH YOUR AREA CODE!!!!! OTHERWISE YOU
CAN ONLY CALL LOCALLY IN YOUR AREA CODE.
Create a batch file to run CBVTAG. Note the TAG % parameters in 2.7 are
the same for NEWLOGON.BAT and a door batch file called from a ":"
(dorinfo?.def) menu call. I run mine from my Main Menu and NEWLOGON.BAT.
A sample batch file, SAMPLE.BAT, is included with the CBVTAG archive.
The batch file goes in your Main BBS directory and cannot have the same
name as another .BAT, .EXE or .COM file located in that directory.
If you are not running CBVTAG from NEWLOGON.BAT, add a menu entry with
the following:
PKey : ":" <- Create DORINFO?.DEF
PData: "Batch file name" <- Without the .BAT
If you only want to run CBVTAG from NEWLOGON.BAT you do not need a menu
entry.
If you run multi node you only need 1 directory for the file. Just write
a batch file for each Main BBS directory and put it there, the Main BBS
directory for each node.
Sample batch file for CBVTAG for TAG Main directory in D:\TAG with
a locked fossil driver:
------------------------------------------------
@echo off
cd\tag\cbv
CBVTAG /N%9 /C%8 /R%1 /U%3
cd\tag
exit
------------------------------------------------
NOTE: The command parameters "SOUND" complicated, but if you look at it
there are only 2 that you have to even waste a brain cell on.
The parameters may be in any order but must have a space before each "/"
and have no space between the /<letter> and the information.
These parameters are not case sensitive.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Optional Information Text Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
CBVTAG allows up to 7 text files to be used to describe the door for the
users. If the file isn't present then CBVTAG will use default text.
Brief descriptions are as follows:
1. LOCHANG.TXT - Tells users why the door is hanging up on them after
a successful local call back.
2. LDHANG.TXT - Tells users why the door is hanging up on them after
a successful long distance call back.
3. TELSYSOP.TXT - Message to user if he/she says the number the door
will call them at doesn't look right.
4. ASKPHONE.TXT - Message to user to see if the phone number looks right
before calling.
5. PRECALL.TXT - Shown just prior to dialing users number explaining
how to make their modem answer when they are called.
6. NO_LD.TXT - Shown to Long Distance users if you don't allow LD
calls.
7. BADPNUM.TXT - Shown to a CBVTAG user who entered a phone number
they can't be reached at. This may be a nice
message or nasty message, the default is a
nasty message <g>. Shown only if you configured
CBVTAG NOT to let the user change his/her number.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ EMail Template Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
As of version 1.3 CBVTAG will send EMail to your user when they use the
door in several instances. CBVTAG creates a Fido, Hudson or JAM Style
EMail message in the directory assigned in your T.A.G. configuration
file, MBaords.Dat, using the text you type into the sample "template
files". The To, From, Subject, Date and message attributes are
automatically added by CBVTAG. All you need is the ASCII text files
described below for the ACTUAL message content. If the file is not
found a message will not be sent.
The Available Email Template Files:
1. EM_WELC.TMP - EMail msg sent to a CBVTAG user after successfully
completing the call back.
2. EM_NOUSE.TMP - EMail msg sent to a CBVTAG user who enters the door
and leaves it without being validated.
3. EM_PHONE.TMP - EMail msg sent to a CBVTAG user who entered a phone
number they can't be reached at. This may be a
nice message or nasty message, the default is a
nasty message <g>. Sent only if you configured
CBVTAG NOT to let the user change his/her number.
You MUST edit the following files or else you'll be using the defaults
for my BBS <grin>.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Data text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
NOTE: As of version 2.2 the old MC_CBV*.* files need to be renamed to
CBVTAG*.*!.
Data Text files: (* - means it's required)
* CBVTAG.LOC - List of just the first 6 numbers of phone numbers that
are local to you separated by a - sign. For a total
of 7 characters.
Please note that the numbers MUST start at column 1.
Start at the area code. You don't need the "1-", it
is added if needed by the door AFTER checking to see if
the number is local.
YOU MUST MAKE THIS FILE!!!!!!! If you run FrontDoor
you already have this information in FDNODE.CTL.
Just copy the file to CBVTAG.LOC, do a minor amount
of editing and you'll be ready to go.
NOTES :
Note1: IF YOU HAVE MORE THAN ONE AREA CODE THAT IS A
LOCAL CALL LINE #1 OF CBVTAG.LOC MUST BE ONE WITH YOUR
AREA CODE!!!!! OTHERWISE YOU CAN ONLY CALL LOCALLY IN
YOUR AREA CODE.
Note2: ALL LINES IN TIHS FILE MUST BE PHONE NUMBERS,
NO COMMENTS ON BLANK LINES!!!
Example: If you had only the following 4 local exchanges
the file would have the following 4 lines and
nothing else..
804-671
804-499
804-555
708-999
It's done this way to allow those bordering area codes
which are local to you to be processed right.
These numbers can be found in the front of most
"Genuine Bell" phone books in those pages you usually
skim right over <grin>. Any local numbers you forget will
be treated as long distance calls.
The format is similar to the FrontDoor's FDNODE.CTL. To
save some typing and research you can copy FDNODE.CTL to
CBVTAG.LOC and edit it to CBVTAG's format.
CBVTAG.HOW - IF THIS "OPTIONAL" FILE EXISTS THEN IT WILL BE USED INSTEAD
OF CBVTAG.LOC. (CBVTAG.LOC must still exist because the
first entry in it has to be a number in YOUR AREA CODE)
This file is a variation of CBVTAG.LOC. Instead of having
all the Yes/No answers in the config. It became necessary
because phone companies are getting stranger in some areas
on how you should dial calls.
For an example assume you have the following numbers as
local (area code followed by first three digits):
222-234
222-235
222-236
333-234
Now assume to dial the numbers you have to do it as
follows for the listed numbers:
222-234 you just dial 234,
222-235 you have to dial 1-222-235,
222-236 is dialed as 236 and finally
333-234 dialed as 1-333-234.
CBVTAG.HOW would have to be as follows:
222-234 234
222-235 222-235
222-236 236
333-234 333-234
If the length of the second number listed in the line
is 3 then the area code is stripped and no LD prefix
is added. If the length of the second number is 7
(counting the -) then the LD prefix is added and the
number is dialed like a long distance number although
it's local.
CBVTAG<Node #>.LOG - Log of the doors activity. Made by the door.
Each node gets it's own separate log file,
CBVTAG.BAD - List of phone number NOT TO CALL (ie your local police
stations, fire stations, phone sex hot line, your ex-wife,
etc.) CBVTAG will automatically not call 411, 911, 800,
900 numbers and 555-1212 (directory assistance in any area
code).
(You have to make it and it is only read up to column 12.
The rest may be used for comments as to why it's there )
*** COMMENTS MUST BE AFTER COLUMN TWELVE IN ALL CASES ***
Examples:
To not call an ENTIRE number (police, fire, YOUR BBS
number, twits on your system, ANY full number you
DON'T WANT TO CALL) use all 12 characters.
804-671-8547 <-* Mark & Debbi McKay's BBS Node 1
To not call an ENTIRE area code (900 numbers, etc.)
use the FIRST "4" characters. Must be 3 numbers
followed by a "-".
900- <- Pay by minute number
000- <- no such animal anywhere
To not call an ENTIRE Local prefix (say your police
department has all the 444 numbers, 411 (directory
assistance in some areas), 911 (Emergency TRACED
number), etc.) use "4" characters. Must be a "-"
followed by a 3 numbers.
-411 <- directory assistance (some areas)
-911 <- Emergency number
-000 <- no such animal anywhere
To not call an ENTIRE Local suffix (best example is 0000)
use "5" characters. Must be a "-" followed by a 4 numbers.
-0000 <- no such animal anywhere
To not call a specific number in ALL area codes
the number should be entered using "XXX-" and
the number. XXX must be in capital letters. The
number MUST be 8 characters, ex. 234-5678.
XXX-555-1212 <- Directory assist for ALL area codes
CBVTAG.OK - List of phone numbers the door has successfully called.
CBVTAG will not call the same number twice if "Check for
dupes" is set to Yes in CBV_CFG. If you have lots of
families calling your BBS then set this option to no or
be ready to answer the "The mother, father, sister, brother,
dog, cat, boyfriend, girlfriend, roommate is already on here
why can't I get on" questions in EMail <g>.
CBVTAG.TWT - Semi-informative Log of callers to the door who have been
validated by the door.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Utility Programs ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
CBVLTRIM.EXE - Trims your CBVTAG Logs when you think they're hogging too
much space. Starts at CBVTAG01.LOG and goes to
CBVTAG99.LOG (if you have 99 nodes up) and if it finds the
log in the current directory it removes all entries older
than the date specified on the command line.
Usage: CBVLTRIM <Date to keep entries since>
Example: CBVLTRIM 04-01-94
This example will trim "ALL" CBVTAG logs in the current
directory of ALL entries older than April 1, 1994.
MKOKLIST.EXE - Makes a CBVTAG.OK file containing the full phone numbers
(Phone,Phone2,ExtraPhone) of all users with an SL >= the
one you specify on the commandline.
Usage: MKOKLIST <SL> <Path to User.lst>
Example: MKOKLIST 30 C:\TAG\GFILES
This example will read User.Lst in the C:\TAG\GFILES
directory and create CBVTAG.OK for all users with a
security level greater than or equal to 30 in the CBVTAG
directory.
Why have it: So people with the same phone number can't log on under
another name.
MKOK2.EXE - Makes a MKOK2.LST file list of all users with an SL >= the
one you specify on the commandline.
Usage: MKOK2 <SL> <Path to User.lst>
Example: MKOK2 30 C:\TAG\GFILES
This example will read User.Lst in the C:\TAG\GFILES
directory and create MKOK2.LST for all users with a
security level greater than or equal to 30 in the CBVTAG
directory.
Why have it: So you can look through your user list for bogus looking
phone numbers and see the users user number, record number
and user name.
WRONGCHK.EXE - Makes a WRONGNUM.LST file - a list of all users with an SL
>= the one you specify on the commandline, whose record
number is not the same as the user number ("locked out").
Usage: WRONGCHK <SL> <Path to User.lst>
Example: WRONGCHK 30 C:\TAG\GFILES
This example will read User.Lst in the C:\TAG\GFILES
directory and create WRONGNUM.LST for all users with a
security level greater than or equal to 30 in the CBVTAG
directory who's user and record numbers don't match (they
are either locked out or deleted).
Why have it: A couple of beta versions of CBVTAG locked out users
for some unknown reason. Measures to insure this doesn't
happen anymore have been instituted.
To Unlockout a user do the following:
1. Go into your TAG user editor.
2. Hit "U" at the prompt.
3. Type in the "RECORD NUMBER" of the user to unlockout.
4. When the users record comes up hit "#" and type in the
"RECORD NUMBER".
The user is no longer locked out and the record number
should now be the same as the user number.
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓ Registration ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘
CBVTAG is not now, has never been and will never be "FREE" software.
CBVTAG is provided as "Shareware" for those T.A.G. BBS sysops looking
for a "User call back verification program" for T.A.G. BBS.
If you honestly plan on registering the program within 30 days if you
find it useful then feel free to test it out to see if it meets your
needs. If you have no intention of ever registering it, then don't
even bother setting it up.
You "should" be able to tell within a few days if the program is "what
you have been looking for". It you have not registered the program
within 30 days of setting it up you must remove it from your system.
Registration is for you and you alone. You cannot "sell" your key to
your buddy down the street or across town.
Registration is for the version of the program that you tested. There
are no guarantees either expressed or implied of any updates to the
program or addition of any "new features" if you register. You are
registering it "as is". When you do register you are entitled to use
all future versions of "this" program as a "registered user" should
there be any.
Registrations normally take between 2 days and 2 weeks to get to me.
When I do "receive" it you will be able to get your key within 1 to 2
days. Sorry, but "Checks in the mail" doesn't work, I've heard it too
many times.
If you are in "Fidonet" I will send your key file to you within 2
days of receiving your registration via Fidonet Netmail File Attach.
Otherwise you must call my BBS twice to "pickup" your key file.
Once to log on (if I am around and I see you log on you will only need
to log on once) and another time a day or two afterward to "get your
key".
Pricing as of 15 October 1994 :
Number of Keys "Proper Amount"
-------------- ---------------
1-2 $15.00 each
3-10 $10.00 each
11-20 $7.50 each
20+ $5.00 each
-------------- ---------------
This means that if you and two other TAG sysops in your area want to
register CBVTAG together you'll each save $5 on the registration.
These rates apply only if it is in the same envelope. It doesn't mean
that if "Joe down the Street" and "Sally next door" registered a month
ago that you get yours for $10. It means that if you, "Joe" and "Sally"
get together and send $30 with the proper info, you will each get a key.
If you send less than "the proper amount", you "won't" get a key,
you will get the amount you sent minus the cost of a stamp and a money
order provided it covers such. Plain and simple. Amounts in excess of
"the proper amount" are cheerfully accepted and considered "donations".
All registrations must be in US funds. If you live outside of the US
you must send a money order drawn on US funds. For example a personal
check from Canada is worthless paper. Most Canadian banks will give
you a money order drawn on US funds with little to no hassle.
You will receive one key made with the information that "you" supply
below. If you run a multi line system you only need to register one
copy provided the sysop name is the same for all of the nodes.
If you use different names on different nodes you need to register each
one separately.
If the key doesn't work because you gave me the wrong information or you
change the information at a later date then you must pay a $5 processing
fee for the updated key file for the extra time involved in making
"another key". If "I" messed up then I will give you a free replacement
key. Please ensure the information you give me is correct.
With the payment include the following information:
Sysop name from your "System configuration" (case sensitive), ie if your
real name is "Anthrax Buttsnorkler" but the name you give on the BBS is
"John Doe" then you need to supply the name "John Doe". If you use the
name "FuNkY sPeLlEr" then give it as "FuNkY sPeLlEr".
If you are a public Fidonet node holder (no points), include your Node
number.
Sysop name from TAG config :______________________
Fidonet Node Number (if in Fidonet) :______________________
BBS Phone Number :______________________
Send the CBVTAG registration fee (money order preferred) to
Mark McKay
PO Box 68063
Virginia Beach, VA 23455
┌─────────────────────────────────────────────────────────────────────────────┐
│▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
└─────────────────────────────────────────────────────────────────────────────┘