home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Frostbyte's 1980s DOS Shareware Collection
/
floppyshareware.zip
/
floppyshareware
/
GLEN
/
SF31-2.ZIP
/
SFBUSY.ZIP
/
SFBUSY.DOC
< prev
Wrap
Text File
|
1990-08-15
|
7KB
|
163 lines
SFBUSY
Version 1.0
Copyright (C) By Mike Woltz 1990
Buffalo Creek Software
A Member Of
The Association Of Shareware Professionals
INTRODUCTION
------------
SFBUSY is a utility written in Turbo Assembler by Mike Woltz
and is intended to be used with SPITFIRE Bulletin Board System.
SFBUSY is used with SFWHOSON.DAT for the purpose of discovering
whether a caller is logged on SPITFIRE, to set SFWHOSON.DAT to
disallow any caller from logging on SPITFIRE and to reset
SFWHOSON.DAT to again allow callers to log on SPITFIRE. With
the expansion of SPITFIRE to multi-node capability in Version 3.0,
this will be desirable, if not mandatory, for some BBS maintenance.
For instance, when packing message conference files using Bob
Browne's SFPACK, you will want to insure that no callers are on any
of the available BBS nodes before beginning the pack and then after
beginning the pack you will want to insure that no callers can log
on while the pack is being performed. Once the maintenance is
performed, SFBUSY, used with the /C parameter, makes the BBS
accessible to callers once again.
*SFPACK is a utility copyrighted by Smart Office Solutions and
part of the SFUTI driver written by Bob Browne.
COMMAND LINE USAGE
------------------
Two command line parameters are used with SFBUSY. These are
/S to SET the utility to perform maintenance and /C to CLEAR
the maintenance parameter.
SFBUSY should be located in a directory included in your PATH
so it can be properly executed regardless of the then current
directory. In the event SFBUSY is not being executed from the
directory in which SFWHOSON.DAT resides, then it must be executed
by providing the path or the drive and path to your WORK file directory
in the command line prior to the /S or /C parameter. For instance:
SFBUSY D:\WORK /S
Using SFBUSY with the /S parameter from either the WORK file
directory or with the WORK file directory specified will result
in either an ERRORLEVEL 0 or an ERRORLEVEL 2 being returned to
DOS.
If all nodes on the system are free from use, SFBUSY reports:
Setting maintenance parameter!
Sending ERRORLEVEL 0 to DOS!
Once this is done, callers can not log on the BBS. When a caller
attempts to log on, SFPRELOG.BBS and the WELCOME1.BBS/CLR screens
are displayed and then prior to the caller entering their name,
SPITFIRE will display a default message:
"A maintenance operation is being performed!
Please try again in a few minutes..."
The Sysop may choose to create SFMAINT.BBS/CLR display files which
would be shown in place of SPITFIRE's default message.
In the event, a caller(s) is on one or more nodes of the BBS, an
ERRORLEVEL of 2 is returned to DOS and the maintenance parameter
is not set.
Anytime the maintenance parameter is set, SFBUSY MUST be executed
with the /C parameter afterwards, to clear the maintenance parameter
and to once again make the system accessible to callers.
In the event SFBUSY is unable to find SFWHOSON.DAT, the following
message is displayed:
SFWHOSON.DAT Not Found!
Sending ERRORLEVEL 1 to DOS!
If an ERRORLEVEL 1 is returned to DOS, SFBUSY will not set the
maintenance parameter within SFWHOSON.DAT which prevents a caller
from logging on the BBS.
SFBUSY USAGE
------------
SFBUSY will most likely be used within the SF.BAT when executing
SPITFIRE scheduled events. Such an example, again using SFPACK, might
look like this:
:EVENT_I
D:
CD\PCRELAY
SFBUSY C:\WORK /S
IF ERRORLEVEL 2 GOTO EVENT_I
IF ERRORLEVEL 1 GOTO I_END
SFPACK AREA:1-2 MSGS:200 DAYS:30 NOBAK
SFPACK AREA:3-20 MSGS:200 DAYS:10 NOBAK NODUP
SFBUSY C:\WORK /C
:I_END
C:
CD\SF
GOTO LOOP
Notice, SFBUSY is executed with the /S parameter and once the
desired maintenance is performed, executed again with the /C
parameter. IMPORTANT - SFBUSY MUST BE RUN WITH THE /C PARAMETER
AFTER IT WAS RUN WITH THE /S PARAMETER. IN THE EVENT SFBUSY WAS
SUCCESSFULLY RUN WITH THE /C PARAMETER, SPITFIRE WILL NOT ALLOW
A CALLER TO LOG ON UNTIL SFBUSY IS RUN USING THE /C PARAMETER.
Please not that in the above example, in the event SFBUSY sends
an ERRORLEVEL 2 to DOS (meaning a caller is logged on SPITFIRE) then
it continues to be executed until a permissionable ERRORLEVEL is sent
to DOS.
IF ERRORLEVEL 2 GOTO EVENT_I
Further, please not that in the above example, in the event SFBUSY
sends an ERRORLEVEL 1 to DOS (meaning SFWHOSON.DAT was not found) then
the scheduled maintenance is skipped and control is returned to
SPITFIRE.
IF ERRORLEVEL 1 GOTO I_END
DISTRIBUTION
------------
SFBUSY is distributed under the shareware concept. You are free
to distribute the SFBUSY program as long as it remains unmodified and
no fee is charged. If you use this program and find it beneficial, a
$1.00 registration fee is required.
The registration fee should be sent to:
Buffalo Creek Software
Attn: Mike Woltz
913 - 39th Street
West Des Moines, Iowa 50265
DISCLAIMER
----------
Mike Woltz and/or Buffalo Creek Software shall in no way be held
responsible for any damage incurred while operating SFBUSY. All
responsibility lies with the user of the software.
The documentation for SFBUSY is contributed by Jacque Shipley and
The Mother Board BBS. The shareware version of SPITFIRE, SFBUSY and
other utilities written by Mike Woltz are available for download from:
Buffalo Creek's BBS The Mother Board BBS
Mike Woltz, Sysop Jacque Shipley, Sysop
(515) 225-8496 - 2 Nodes (515) 986-3464
38400/9600/2400/1200 Baud 19200/9600/2400/1200 Baud