home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
w
/
who503n.zip
/
WHOCALL.DOC
< prev
next >
Wrap
Text File
|
1992-12-31
|
10KB
|
238 lines
WhoCalled? PRO! Version 5.00
30 December 1992
PCBoard is owned by Clark Development Inc.
WhoCalledPRO is owned by Bill Fink - User Friendly Systems And NCCBBS.
* * * New In Version 5.03N - WhoCalled Professional Is "N"etwork Smart! * * *
If you use a previous version of whocalled, you'll want to start
version 5 from SCRATCH. (This INLCUDEs Owners Of Version 4.0)
"WhoCalledPRO!" Is "WhoCalled?" TOTALLY RE-Written.
PLEASE read this WHOLE note BEFORE You report problems.
You need NOT go on any further with "WhoCalled?" if you alter your PCBTEXT
files. I search the "callers" file for literals, that MATCH text EXACTLY in
the PCBTEXT file. For example; if you change "(D)ownload Completed" to
"(D)OWNLOAD COMPLETED", note the case of the letters, or alter
PCBTEXT.fil, WHOCALLED may NOT work for you. Please keep in mind,
those who use optional languages, those optional languages are simply
modified PCBTEXT files.
The first item I guess everyone goes over with any utility that's written is
the "I am not responsible" routine. Sorry guys/ladies, the same goes here. You
KNOW what I mean. You are using WhoCalled? at your own risk.
I WILL say this, WhoCalled? is a VERY simple utility that merely LOOKS at the
callers file. It writes NOTHING to PCBoard's associated files.
Let's get on with the installation, I know you're in a hurry.
Log into the "\WHOCALL" subdirectory. HIGHLY recommended to use this utility
in It's OWN directory. (on the HOME PCB machine for networks.)
Run whoSETUP and answer some brief questions. Please READ the help lines
in the middle of the screen during each question.
At The DOS Prompt, (AFTER either using whoSETUP or editing whoCFG.X
yourself)
type;
whoCALL whocfg.n/x
(where whocfg.n = which configuration file you want to use.)
(n=machine number)
(where x = the node number - ZERO for Clark's new TWO node BBS)
(This file does the work of sorting out all of the information)
(and puts it into the "temp" files. Explained below.)
whoNODE whocfg.n/x
(where whocfg.n = which configuration you want to use.)
(n=machine number)
(where x = the node number - THIS FILE IS FOR THE WHOBULL.xxx)
(do NOT run this, if you ONLY want a bulletin of ALL your nodes)
(in ONE bulletin!)
whoALL whocfg.n/x
(this creates the bulletin WHOBULL.ALL for ALL nodes. - Do NOT)
(run this one, if you ONLY want a bulletin for EACH node.)
You'll obviously want to include those lines in your $$LOGOFF.BAT.
For those of you who are new at this, if that file exists ($$LOGOFF.BAT)
in your PCB's "home" directory, PCBoard V14.5a will run this batch file
each time a user logs off.
Your $$LOGOFF.BAT should look like this:
cd [d:\] whocall
whocall whocfg.n/x
whonode whocfg.n/x
whoall whocfg.n/x
cd [d:\] pcb
When those programs are through running, you'll have two files.
WHOBULL.XXX and WHOBULL.ALL, THOSE are the files you'll want to be
displayed to your users. (The final output from WhoCalled.)
Version 5.03"N" command line is slightly confusing to glance at, but here's
a VERY brief explaination. The WHOCFG.n file, can be ANY configuration file
so long as it meets the guidelines I explained in EXPLAIN.CFG.
Doing things this way, makes the utility EXTREMELY flexible for
WHATEVER your setup consists of.
I wanted to accomodate network users. JUST AS PCBoard has a different
PCBOARD.DAT file for each node, WhoCalled TOO, needs to know
where certain files are. That information is contained in the file(s);
WHOCFG.n.
My Node I $$LOGOFF.BAT looks like this:
CD C:\WHOCALL
whoCALL c:\whocall\whoocfg.1/1
whoNODE c:\whocall\whocfg.1/1
whoALL c:\whocall\whocfg.1/1
CD C:\PCB
If you have a single machine, but multi-nodes, you can STILL use the
SAME configuration file. i.e. for my Node II, my $$LOGOFF.BAT looks
like this:
CD C:\WHOCALL
whoCALL c:\whocall\whocfg.1/2
whoNODE c:\whocall\whocfg.1/2
whoALL c:\whocall\whocfg.1/2
CD \PCB2
(Network Users - For example, if you have THREE nodes on ONE REMOTE
MACHINE, you CAN use the SAME WHOCFG.x file, for a different node
on the SAME machine. Use the syntax WHOCALL WHOCFG.n/x, and simply
use N as the machine number, and again, X as the NODE number.)
You'll need to include the SLASH!
If you are running ONE node, there's NO need to run whoALL, likewise if you
are running multiple nodes, and you ONLY want an ALL NODEs bulletin, then
omit whoNODE.
Please note, PLEASE, I KNOW I'm going to get calls on this one. WhoCalled,
when FIRST ran, needs to BUILD UP the temporary files up to the limit of the
number of calls you specified in your configuration files for either the NODE
bulletins or your ALL bulletins. What I'm trying to say is that the first time
you run it, it will have ONE caller logged in there. The second time you run
it, it will have the second caller logged, and so forth, until it reaches the
maximum number of callers you told WHOCALL.CFG to track.
When you run whoCALL.exe, if the LAST caller is the SAME as THIS caller, it
will NOT append your bulletin. (Makes sense, doesn't it?)
Your output bulletin(s) should look similar to this:
BBS Name Goes Here - Node : 9
Who Called? - V2.98 - Written By: Bill Fink
Time Min. Connect #Msgs Files Files Avg
Date User Name On Used Speed Left U/L D/L CPS
----------------------------------------------------------------------------
03-23-92 HORACIO CRISTINO 20:51 4 (2400) 0 0 0
03-23-92. ALEX BOWMAN 20:07 25 (19200E) 4 0 0
03-23-92 MARTIN HARDY 18:48 52 (2400) 0 0 2 230
03-23-92 MITCH KRZYZEK 18:43 1 (2400) 0 0 0
03-23-92■ BILL FINK 13:32 10 (2400) 1 0 0
03-23-92 MIKE GERARDI 12:55 8 (2400) 0 0 1 232
03-23-92 BILLS TESTING 00:06 0 (Local) 0 0 0
Previous xx Callers Tracked.
Note: The period next to Alex Bowman's name above indicated this user logged
off "Abnormally."
Note: The ANSI character next to Bill Fink's name above. This indicates that
the user *MAY* be the victim of a "Hack" attempt. (More than TWO attempts
were made with different passwords.)
I am making a vow RIGHT HERE AND NOW, that I will NEVER post anything to the
effect of "Your SysOp Is Cheap" in ANY "Who Called?" products!
* * * SINGLE NODE USERS! MAKE SURE YOU USE A ZERO "0"
as your node # when you invoke WhoCalled.
This software WILL work with Clark's new 2 Node
version of the code as well.
The BBSes who DID test the product did NOT have ANY problems with their
"CALLER" or CFG file(s). If YOU DO, I trust I have written enough error
trapping to catch any mistake that MAY have happened on your part. If this is
the case, the utility will beep at you and the bulletin created will simply
have the bulletin header (and nothing else) and go on about it's business.
Your board will be back up when it's through.
You WILL run into problems if you've edited your CALLERs file. The contents of
PCBoard's CALLERS file is written as a relative type file and if you edit the
file with an ASCII editor, (OK in MOST cases) you COULD have a distorted
output file as your bulletin.
* THIS IS OK * WHOCALLED? WILL trap it, but needs
to cycle through.
WhoCalled needs a temporary file for EACH node running. Forgive me on this one
but to read a file (a RANDOM type file) from the bottom up, I needed to create
those files to read from. Otherwise, it would run like the OLD WhoCalled?
V3.x, and take anywhere from 15 seconds to 20 seconds in between each call for
say a 35 call limit.
There is GREAT news now! (New In Version 5) If you're inclined to NOT like my
header or footer files, you can simply ADD YOUR OWN. You MUST have something,
even if there are blank lines. But, the choice is yours now to use mine OR
yours.
WHOCALL.HDR and WHOCALL.FTR are the files that are appended to the bulletins
before and after the raw data is placed, respectively.
WhoCalled? Uses the CALLER file for it's information. You can limit the
number of callers that it checks and writes to your bulletin using the
WHOCFG.n file. See the WHOCFG.n FILE and read the EXPLAIN.CFG help file.
I can be reached at (401) 848-9176. PLEASE this is my HOME VOICE PHONE, try to
keep it EARLIER than 6PM. (I'm taking into account Pacific time) Let's face
it, it's a lot easier if we can talk voice.
My BBS free access phone number is (401) 846-1763, which is v32bis, should you
prefer to SEE the bulletins in action. (And keep tabs on any upgrades.)
Use node II (401) 846-1763 to browse my bulletins files, take a look at my
bulletin #16, #17, #18, and leave a comment, asking for help should you need
any.
What EVER you do, PLEASE don't try WHOCALLED and if something went wrong, just
delete all the files and forget about it. Please call me, and let me know if
the utility is not working for you for your configuration. I can NOT attempt
to fix something, if I don't know it's broken.
I will NEVER know if you want something added, or something special for YOUR
BBS if you don't call. Please CALL!
It's getting to the point that I've spent MANY hours with WhoCalled. If you
REALLY want to see MORE upgrades, send a $10.00 "suggestion" to keep me at
programming for WhoCalledPRO.
Bill FINK
4204 East Bay Village
Middletown, RI 02840
Chris, thanks for your suggestions!
That's it, have FUN with WhoCalledPRO!
Bill FINK - SysOp / Owner / Manager - NCCBBS
Middletown, Rhode Island