home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
s
/
sfclu12.zip
/
SFCLU.DOC
< prev
next >
Wrap
Text File
|
1992-01-22
|
6KB
|
144 lines
┌───────────┐
│ SFCLU.EXE │
└───────────┘
SPITFIRE 3.x Caller's Log Update
Tom Kellen
ßETATech Computer Consulting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PURPOSE: Beginning with version 2.9, Spitfire BBS supports multiple
nodes. Because of this, during each logon, a file called
CALLERS.TMP is created in the home directory of each node
and everything that happens during that session is logged
to this file. After the caller's session is over this file
is appended to the main CALLERS.LOG in the \WORK directory.
This little utility will append a line of text to the
CALLERS.TMP file for the node it was called from.
INTRODUCTION:
With the advent of multi-node Spitfire, each node creates a temporary
log file in the home directory of that node. SFCLU will allow you to
append a line of text to this file. Basically this is a rewrite of
Bob Zimmerman's excellent SFLOGIT utility which is for versions of
Spitfire prior to 2.9. SFLOGIT will update the CALLERS.LOG file in
the \WORK directory and because it does this before CALLERS.TMP is
appended to CALLERS.LOG, your CALLERS.LOG will not have the events in
the order they happened. SFCLU solves this problem on the multi-node
system. SFCLU has a multitude of uses, it can be called from your
external protocol batch files to indicate that a certain protocol was
used, or from any other batch file to log a happening into your
Spitfire Caller's Log. SFCLU is written using Buffalo Creek's BCSHARE
Turbo Pascal File Locking and Sharing Unit to be totally compatible
with multi-node use.
INSTALLATION:
You will need to place a copy of SFCLU into each node's home
directory. For instance, if you are running on a network and Node 1
is run from C:\SF and Node 2 is run from F:\SF you would need a copy
of SFCLU.EXE in each of those directories. If you are multi-tasking
and running Node 1 from C:\SF1 and Node 2 from C:\SF2, place a copy
of SFCLU.EXE in each of those directories. When SFCLU is run, it will
find the directory it was run from and append it's command line to the
CALLERS.TMP file in that directory.
OPERATION:
SFCLU will append the text that is on it's command line to the
CALLERS.TMP file that is in the same directory as the SFCLU.EXE file.
As an example you might put a line in your external batch file similar
to the following:
SFCLU **ZModem has been used.
The line of text (including the leading spaces) will be appended to
the local CALLERS.TMP file. Now you will know which external protocol
was used. If you are multi-tasking or both Spitfire Node's home
directories are on the path you should call SFCLU with an explicit
path like this:
C:\SF2\SFCLU **ZModem has been used.
Make sure that you test out the number of leading spaces so that the
comment line will line up with the others in your caller's log.
NOTE: JP Software's 4DOS command processor (COMMAND.COM
replacement) is a superb program, but for some reason eat's
the leading spaces you might want to use as we did in the
example above. SFCLU can detect when it is running under
4DOS and will manually insert the 8 spaces that is the
standard to line up with other items in CALLERS.LOG. This
is less flexible but should be acceptable to those running
their BBS under 4DOS.
That is all there is to it. This will help you keep track of
happenings on your BBS.
EPILOGUE:
This is a Free Spitfire utility. I retain the copyright, but you may
use it to your heart's content. If you find this utility of use, per-
haps you would consider making a donation (monetarily or in time) to
help our environment. This is the only planet we will get for a
while!
AUTHOR CONTACT:
Problems, solutions, kudos and ideas are welcomed. I can be reached
at the following:
The Paradigm BBS ßETATech Computer Consulting
(404) 671-1581 P. O. Box 566742
1200-19,200 Baud 24 Hrs/Day Atlanta, GA 31156-6013
DISCLAIMER:
Use of this program acknowledges this disclaimer of warranty: "This
program is supplied as is. ßETATech Computer Consulting disclaims all
warranties, express or implied, including, without limitation, the
warranties of merchantability and of fitness of this program for any
purpose. ßETATech Computer Consulting assumes no liability for
damages direct or consequential, which may result from the use of this
program."
ACKNOWLEDGMENTS:
My thanks to Mike Woltz for his fine Spitfire BBS Software and for
providing sample Turbo Pascal source code for us novice programmers
and for Buffalo Creek's excellent BCSLOCK Turbo Pascal Unit used for
all file locking and sharing routines in this program. Thanks to John
Newlin for being an inspirational programmer and providing excellent
shareware to the computing public, and to Sammy Mitchell for his
superb QEdit text editor, how can anyone do without it? And special
thanks to Bob Zimmerman for writing the original SFLOGIT and for his
BZ_CMD Turbo Pascal Command Line Handling Unit which provided the
inspiration for this program.
REVISION HISTORY:
16-JUL-1990 v1.0 Initial Release.
18-NOV-1990 v1.01 Recompiled with BCShare v0.7 to correct some
error checking.
01-DEC-1990 v1.1 Recompiled with Turbo Pascal v6.0.
22-JAN-1992 v1.2 Added automatic 4DOS recognition and default
spacing for working under 4DOS.