home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
UTILITY
/
UCHECK2.ARJ
/
UC.DOC
next >
Wrap
Text File
|
1990-05-20
|
5KB
|
111 lines
Welcome to UserCheck!
Written by Rob Miller
v 2.0 Released 5/20/90
Sysops currently using UserCheck 1.x are encouraged to upgrade to
version 2. See below for details.
About UserCheck
The purpose of this utility is to assist WWIV sysops in the maintaining of
their users' accounts. UserCheck will delete "stale" users after a length
of time you define.
You may wish to keep certain users who have not called in a given number
of days. When this applies, you may exclude these callers from UserCheck's
wrath by either setting the cutoff SL to above their SL, *or* by setting
the AR to an AR that you give them.
Example:
I use 60 days, SL of 70, AR of G. This simply means that UserCheck will
delete any caller who has not been on the system in 60 days or more UNLESS
they have a seclev of 70+ or an AR of G. This gives the sysop a lot of
flexibility when confronting the stale user problem.
*** GOOD NEWS!! ***
There are a couple of advantages this version of UserCheck has over previous
(1.x) versions. First, and perhaps most important, is that this version
runs as a *STAND ALONE*. You may set it to run from your daily.bat, or you
can set it up to run as a chain if you like, or even from the command line.
I run mine from daily.bat. THIS MEANS THAT USERCHECK IS NOW AVAILABLE TO
THOSE SYSOPS WHO DO NOT HAVE THE SOURCE CODE TO WWIV.
Secondly, the ease of installation UserCheck 2 offers over previous
versions that had to be placed inside the code effectively zeros the
possibility of creating bugs. You cannot run this utility incorrectly.
(See note about command line parameters and where you need to place the
uc.exe file.)
Another benefit will be seen when your system calls out using Zmodem. You'll
notice about 20k more room while calling out. Additionally, those sysops
who have modded their WWIV's to the max and are constantly running into
"DGROUP error" messages, UserCheck 2 is for you.
*** IT'S EASY!! ***
Place the executable file, UC.EXE, in the same directory as your CONFIG.DAT
file. (On my system, D:\WWIV> contains most .EXE files and some .DAT files
as well.)
UC Prints out a screen of instructions.
UC i Runs the init program. You need to run this FIRST in order to set
up your parameters, and whenever you want to change them.
UC u Runs UserCheck, the main program. Set this on your command line either
in your daily.bat file, on your "B)Filename" in your //CHAINEDIT, or
from the DOS command line.
QUESTIONS??
I'm reachable in the following ways:
1 @8880 (WWIVnet) The Loop, 818-998-7777
5 @18 (WWIVnet) The Federation, 818-407-0419
96 @ 1 (WWIVnet) Amber, 213-208-6689
If you find what you believe to be a bug, please let me know. If you have
any questions or suggestions, please email me at one of these systems. Also,
if you find UserCheck to be of any benefit, please let me know. I'd appreciate
hearing from you.
You are free to distribute UserCheck 2 as long as you do not charge any fee.
** IMPORTANT!! **
UserCheck needs to write to some VITAL files: USER.LST, NAMES.LST,
STATUS.DAT, SMW.DAT, VOTING.DAT and EMAIL.DAT. It also will need to read from
CONFIG.DAT. Since the integrity of these files is crucial to the smooth
operation of your BBS, *please* back them up each night in a batch file
*before* running UC.
In addition to these files, UserCheck also will report its results in your
daily log. You'll get a listing of which users it deleted and it will remind
you what your parameters are set to. It also copies the date and time it was
run. UserCheck also will create UCHECK2.DAT where it stores the init() data.
If you were running version 1.x, you may delete any and all .DAT files that
pertained to UserCheck 1.x. Besides the WWIV DAT files, UCHECK2.DAT is the
only .DAT file it will need.
** DISCLAIMER **
By running UserCheck (any version), you agree to NOT hold me responsible for
any damage it might cause. I certify that this software is VIRUS and TROJAN
free, but cannot be held responsible for bugs that may already be in your
own code. I'll gladly take proper and effective action should any bugs be
discovered in UserCheck. UC 2, however, has been running on a few systems for
what I believe to be an adequate length of time and no difficulties have
been reported.
Thanks for running UserCheck!