Contents of the USERCHEK.DOC file
SYSOP DOCUMENTATION USERCHEK
IBM Personal Computer
246 Gardner Avenue
Northwood, Ohio 43619
Voice (419) 691-9700
Data (419) 691-1125
This program is not public domain. It is distributed under the
concept of shareware. Please contribute to this process as it
is the only way it can work.
This product is provided "As Is" with no warranty, either expressed or
implied. All risk when running this product is with you.
1.0 Program Description
This file will take control of your bbs and callback users to
verify they are who they say they are. Userchek is strictly
written for RBBS. It uses whatever user interface files that
are provided by rbbs.
2.0 Required files
You must have a batch file that you are running your RBBS from.
The purpose of the files are as follows:
1. Userchek.exe Main EXE program.
2. Userchek.doc Documentation for Rbbs sysops.
3. Userchek.bat Batch file to execute when rbbs exists
to your door program.
4. Readme.now Updates as they have occured.
5. Update.new Version 1.5 added parameter to
usrchk1.def. Special precautions
in installing this version.
Normally, making a userchek subdirectory off of your rbbs
subdirectory is the best way to set up this door. Do this
by typing MD USERCHEK in the rbbs subdirectory.
Setting up this door is easy as all you have to do is invoke
the userchek.exe program. You will be asked to enter various
locations for files. There are suggested defaults that you
might want to accept. The following questions will be asked.
To get to this process, it is recommended that to type:
DOS PROMPT>USERCHEK LOCAL
It is recommended that you run in the local mode for the first
time as you will probably get an error when userchek tries to
access your com port.
1. Enter the name and location of the dorinfo file.
Normally, the location of this file is the same as the
location of rbbs-pc.exe. Rbbs creates this file when
it goes to a door. If you press return, the default
will be used.
If the Dorinfo file cannot be found, userchek will
create one for you.
2. The next question will ask you to enter the name of
door control file rbbs uses to adjust the user's
Normally, this file is named DOUT1.DEF. Userchek
makes this file when returning to rbbs thereby,
adjusting the user's security level.
3. The next question will ask you if you want your bbs
to be calling long distance.
4. The next question asks what the security level is that
will invoke the door to verify callers. On my system
it is -3-. Enter whatever security level you wish
5. Here, enter the level of security to assign to the
caller should the caller pass the verify callback.
6. This question selects the prefix added to the dial
for your modem. ATDP for pulse dialing and ATDT
for touch tone dialing.
7. Enter the location and filename where a log will be
kept of user verify tries. Hitting enter will accept
8. This entry of a filename keeps track of the trash
numbers you want to check before your system dials.
9. This file keeps track of the numbers that were
successfully verified. If a users phone number is in
this file, it will not be called again.
10. The is the opportunity for you to enter a string to
be sent to the modem just before the phone number
is dialed. The default is ATM1 which turns the modems
At this point you might not want the speaker on so
enter ATM0, which turns the speaker off. Having no
effect cause it's off already.
4.0 Running the Doorware program
After completing the setup as stated above insure that items
#107 and #108 are completed.
Item #107 requests the name and location of the file to be invoked
by rbbs when the verification takes place.
Item #108 requests the security level to watch for to invoke the
Userchek is invoked by the running of the batch file userchek.bat
by rbbs. Typical userchek batch file would be as follows:
NOTE: You must not invoke a watchdog program to check for carrier
as this will reboot your machine during the callback process.
The watchkit timer line below is only there to keep things
going should there be an untrapped DOS error that results in
Abort, Retry, ...etc.
echo Please Standby....... > com1
Line#1 of this file will send a message to the caller to please
standby. Change the comm port if applicable.
Line #2 invokes a program called watchkit that will reboot the
bbs should an error occur that hangs the system. Carrier detection
is provided in the Userchek program.
Line #3 points to the userchek directory to run the userchek
Line#4 invokes the userchek program for the specific node.
Line #5 get us back to the rbbs subdirectory to give control back
You can run Userchek and NOT have it check for carrier by using
the word LOCAL on the command line when starting it up. During
normal operation, the word local is not used.
You can provide caller security checking in the form of lower, equal,
and more than required for callback. When rbbs passes control to
userchek for callback, the userchek.def file has the newusers
security level to be verified. If the callers security level is
lower than callback level, the caller must not have done something
you wanted him to. On my board, the caller must fill out the
newuser questionnaire. If the caller comes to userchek with the
proper security level, he is passed to the callback program to be
verified. If the callers security level is more than the newuser
callback level, you must now want the caller verified and they will
be passed back to rbbs with the higher security level.
5.0 Installation Summary:
I had to change my old user's security level to something less
than 9 so that rbbs would run them thru the callback door. This
might be the most time consuming part of this project.
1. Caller logs on BBS. If security level is below level set for
verification, rbbs asks users if they want to register. If
they do, rbbs asks them to do newuser questionnaire. After
questionairre, rbbs exits rbbs to the userchek program.
2. After userchek takes over, it gives users the necessary inform-
ation in order to complete the registration callback.
3. The callback routine generates a random 5 digit number. The
caller is asked to write this number down and remember it. Then
the users screen is erased and they are asked to key in the 5
digit number in again. If successful up to this point, the
callback door disconnects the user and attemplts to call back.
4. If the connection is established, the callback routine asks the
user to enter the 5 digit number. If the numbers match, the
callback routine gives control back to rbbs and the users sec
level is raised to the level specified in the program init
If you register your copy of userchek, I will send you via U.S.
MAIL any and all improvements and fixes as they are implimented.
Full registration for userchek is $25.00 per bbs.
If you send me $10.00, I will send you the latest version as of
the day I receive your request.
I have a 24 hour bbs online. If you have comments or questions
give us a call.
8.0 Multi-user Operation
In order to run this door multiuser, one must set up a usrchk?.def
for each node to be accessed by userchek.
For Instance, node 1's def file would be usrchk1.def and node 2's
def file would be usrchk2.def.
Specify the dorinfo1 or dorinfo2 file as appropriate.