home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
SPITFIRE
/
SFMNUEXT.ZIP
/
SFMNUEXT.DOC
< prev
next >
Wrap
Text File
|
1994-01-26
|
19KB
|
395 lines
SFMNUEXT
SPITFIRE MENU EXTENSION
Version 1.5a
Copyright (C) By Mike Woltz 1989, 1994
Buffalo Creek Software
INTRODUCTION
------------
SFMNUEXT is a utility written by Mike Woltz, author of SPITFIRE, to
expand the Sysop Configurable Menu options available from SPITFIRE's
Main, Message and File Menus. SFMNUEXT will allow a menu to be created
from each of the existing Sysop Configurable command options which will
allow up to 24 additional features per menu. SFMNUEXT will also work
from the SPITFIRE Door Menu but is not intended in any way to replace
or substitute Wildfire. Each SPITFIRE Menu Extension can also be used
to call another Menu Extension, so that the number of options which
SFMNUEXT can expand to is unlimited.
HOW IT WORKS
------------
It is recommended that SFMNUEXT.EXE be placed in a directory
made directly off your main SPITFIRE directory. For the purpose
of explanation, this directory will be titled SFEXTEND. If you need
additional information on making a directory, refer to your DOS
manual. If you are running SPITFIRE from drive C:\ and your
main SPITFIRE directory is named SF and the directory created
for SFMNUEXT is named SFEXTEND it would look like this:
C:\SF\SFEXTEND
Place SFMNUEXT.EXE in this directory. SFMNUEXT is designed so
it is NOT necessary to have multiple copies existing on the drive.
One common file will work for each of the functions you wish to perform,
whether the menu you wish to extend is from the Main Menu, Message Menu,
File Menu, Door Menu, or any combination of these.
If you wish to use SFMNUEXT from the Main, Message or File Menu's
Sysop Configurable command, the appropriate .BAT file (SFMAIN.BAT,
SFMESS.BAT and/or SFFILE.BAT) should be replaced (or modified) with
those included in the SFMNUEXT.ZIP file archive. Similarly, if you
wish to use SFMNUEXT from the SPITFIRE Door Menu, the SF.BAT will
need to be modified to CALL the SFDOREXT.BAT included in the
SFMNUEXT.ZIP file archive. These batch files provide the necessary
Errorlevel commands to execute a particular SFMNUEXT menu option.
The(se) batch files must reside in the main SPITFIRE directory.
To properly understand how all this ties together, a brief
description of what happens when using SFMNUEXT will be beneficial.
For purposes of explanation, let's assume SFMNUEXT is being run from
the Sysop configurable command of the Main Menu. When the Sysop
Configurable option is selected, SPITFIRE shells to the SFMAIN.BAT
file. The SFMAIN.BAT will copy the SFMAIN.DAT file to the directory
where SFMNUEXT resides (C:\SF\SFEXTEND) and change to the \SF\SFEXTEND
directory. The SFMNEXT.MNU is displayed to the caller. When an
option is selected from the Menu, the corresponding Errorlevel will
execute the appropriate commands (to enable program execution).
During the execution of the program, SFMNUEXT will terminate from
memory. When the selected program is terminated, the caller is
returned to the SFMNUEXT. Here, another program may be selected
(if available), or the caller may opt to <G>oodbye & LogOff the BBS
or <Q>uit and return to SPITFIRE. (NOTE: The <G>oodbye & LogOff
option will not display when logged on locally. It will only
display to a remote caller.)
SFMNUEXT MENU FILES
-------------------
Regardless of whether, SFMNUEXT is run as one of the Sysop
configurable command options or from the SPITFIRE Door Menu, a menu
file must be created. The extended menu can be created using your
favorite text editor (as long as it saves in ASCII format) and should
describe the features you have available. When SFMNUEXT is executed,
depending on which data file is found (SFMAIN.DAT, SFMESS.DAT, SFFILE.DAT
or SFDOORS.DAT), SFMNUEXT will look for the corresponding menu. These
are SFMNEXT.MNU, SFMESEXT.MNU, SFILEEXT.MNU or SFDOREXT.MNU. In other
words, if you are using SFMNUEXT as a Sysop Configurable Command from
the Main Menu, a SFMNEXT.MNU will need to be created, or from the
SPITFIRE Door Menu, a SFDOREXT.MNU will need to be created, etc. Sample
*.MNU files are included in the distribution package.
Alphabetical characters are used to initiate the SFMNUEXT commands.
A through Z, with two exceptions. The <G>oodbye is used to log the
remote caller off the BBS and the <Q>uit is used to return the caller to
the menu from which the SFMNUEXT is executed. The menu files used by
SFMNUEXT should be created using the following format:
Program description,[xx],,[=]
with each program listed on a separate line of the .MNU file. Notice
each line begins with the description of the program to executed,
followed by a comma, the security level required by the caller for
the program to be able to be accessed, followed by two commas, and
an equal to or greater than sign. If the equal to sign is used the
caller's security must be equal to the security specified and if
the greater than sign is used the caller's security level must be
either equal to or greater than the security level specified. The
program description must be no longer than 24 characters. Also
notice, it is not necessary to include the command character (A
through Z) since these are automatically added by SFMNUEXT.
SFMNUEXT will also allow Sysop created RIP, Ansi and Non-Ansi
menu display files to be created. These are MNEXT[x].BBS/CLR/RIP,
MSEXT[x].BBS/CLR/RIP, FEXT[x].BBS/CLR/RIP and DREXT[x].BBS/CLR/RIP
where [x] is equal to the security of the caller. The [x] security
is used to insure the caller does not have options displayed that
are unavailable to their particular security level. The
MNEXT[x].BBS/CLR/RIP would be accessed from the Main Menu Sysop
Configurable command. The MSEXT[x].BBS/CLR/RIP would be accessed
from the Message Menu Sysop Configurable command. The FEXT[x].CLR/BBS/RIP
would be accessed from the File Menu Sysop Configurable command.
And the DREXT[x].BBS/CLR/RIP would be accessed from one of the SPITFIRE
Door Menu options. Sample MNEXT10.BBS/CLR/RIP, MSEXT10.BBS/CLR/RIP,
FEXT10.BBS/CLR/RIP and DREXT10.BBS/CLR/RIP are included in SFMNUEXT's
distribution package.
USING SFMNUEXT FROM A SPITFIRE MENU
-----------------------------------
SPITFIRE has a Sysop configurable command for the Main, Message
and File menus. The Sysop configurable command is executed through
a batch file which corresponds to the menu it is being run from. In
other words, SFMAIN.BAT runs the Sysop configurable command from the
Main Menu, SFMESS.BAT runs the one from the Message Menu and SFFILE.BAT
the one from the File Menu. The commands necessary to execute SFMNUEXT
and enable the extended menus are set up in the batch file which
corresponds to the menu you wish to have program run from.
The first thing you will need to establish is which of these menus
you wish to use to run the SPITFIRE Menu Extension program. For
this purpose, let's assume that it is going to be set up so it can be
run from the Main Menu. (It should be noted the set up procedure will
be the same regardless of which Menu you are running SFMNUEXT from.)
Next, you will need to decide what you wish to name the command
option and establish what security level will be required for
users of your system to be able to access this option. Once this
is determined you will need to modify the SFMAIN.MNU file using
your favorite text editor, as long as it saves in ASCII format.
(Refer to the SPITFIRE manual for further documentation on this
if needed. It should also be noted that if SFMNUEXT were being
set up to run from the File Menu, you would need to modify the
SFFILE.MNU file and if it was being set up to be run from the
Message Menu you would need to modify the SFMSG.MNU file.)
Examining the default SFMAIN.MNU file, you will notice the Sysop
configurable command appears as:
<K>............. Main Menu Extension,,1000,@
This will need to be replaced with a Command Character that will
be used to select the option from the menu. It is ASOLUTELY IMPERATIVE
that the Command Character must not duplicate an existing Command
Character for another menu option. You will then need to include
a brief description of the Extended Menu option you will be using,
two commas, the security level required to access this feature, and
another comma followed by the a @. The @ must not be changed! (For
more detailed information on modifying your SFMAIN.MNU, SFMSG.MNU or
SFFILE.MNU refer to your SPITFIRE manual.) When finished, your
menu line should look something like this:
<K>.... Brief Program Description,,10,@
When this is completed, you will need to create a SFMNEXT.MNU file
as described earlier in this documentation (SFMNUEXT MENU FILES).
Now you will need to modify the corresponding batch file, SFMAIN.BAT,
so that it can be executed from the Main Menu. Do this using your
favorite text editor, as long as it saves in ASCII format. (Again, it
should be noted that if SFMNUEXT were being set up to run from the File
Menu, you would need to modify the SFFILE.BAT file and if it was being
set up to be run from the Message Menu you would need to modify the
SFMESS.BAT file.)
Each of these .BAT files include the BRK OFF and BRK ON commands.
This is to prevent caller's from using CTRL BRK to break out of your
batch files and gaining access to your system at the DOS level. If
you are not currently using BRK (have DEVICE=BRK.DRV in your CONFIG.SYS)
it is strongly recommended that you do so before using SFMNUEXT.
(BRK is written and copyrighted by Solid Systems, 1985, but can
be downloaded from Buffalo Creek's BBS as well as a number of other
BBS systems.)
Notice the contents of the batch file provide the appropriate error
codes for the execution of each menu option. Further down the batch
file you will see:
:EXTEND_A
REM Place EXTENSION A Commands Here
GOTO LOOP
The commands you will need to run your desired option should be
placed between the :EXTEND_A and the GOTO LOOP statements in place
of the existing REM Place EXTENSION A Commands Here.
Once again, sample SFMAIN.BAT, SFMESS.BAT and SFFILE.BAT are included
in SFMNUEXT's distribution package. It is strongly recommended these
be modified and used in place of SPITFIRE's sample SFMAIN.BAT, SFMESS.BAT
and SFFILE.BAT to insure the proper ERRORLEVEL codes and Extended options
be available.
USING SFMNUEXT TO RUN A SPITFIRE DOOR
-------------------------------------
The first thing you will need to be concerned with when using
SFMNUEXT to run a SPITFIRE door will be to create or modify an existing
SFDOOR.MNU. Using your favorite text editor you will need to
include a line that contains a brief description of the extended menu
you intend to run, a comma, and the security level required by the
user to access this extended menu. (The line number should correspond
to the door number you are running your extended menu in. In other
words, if the extended menu will be option A of your SPITFIRE Door
Menu then it should be on the first line of the SFDOOR.MNU file,
option B, the second line, etc.)
A typical line of your SFDOOR.MNU might look like this:
The Extended Menu Description,10
If you are using SFDR[x].BBS/CLR Sysop created non-Ansi and Ansi
menus these will need to be modified also.
Once this is completed, you will need to modify the SF.BAT using
your favorite text editor (as long as it saves in ASCII format) to
run SFMNUEXT from the SPITFIRE Door Menu. Sysops using DOS Version
3.3 or higher can use DOS's CALL command to execute SFDOREXT.BAT
from the SF.BAT. Sysops using DOS versions 3.2 or older may use
Buffalo Creek Software's "CALLBAT" utility to execute SFDOREXT.BAT
from the SF.BAT.
DOS's CALL command and the CALLBAT utility allows one batch file
to be run from another batch file and then returns to the original
batch file when the called batch files execution is completed or
terminated. Without using the CALL command or the CALLBAT utility,
when the second batch file is completed or terminated, the caller
would be returned to the DOS prompt. For this set up, refer to the
sample batch files which are included for reference. These are
SFBAT.SAM and SFDOREXT.BAT.
**IMPORTANT NOTE** If you have DOS version 3.3 or higher, Buffalo
Creek Software strongly recommends this be used rather than the
CALLBAT utility.
Using The CALL Command In SF.BAT For SMNUEXT
--------------------------------------------
The first thing you will need to do is modify your SF.BAT file
with your favorite text editor. Locate the line which contains
:DOOR_A. Your SF.BAT should look like this:
:DOOR_A
CALL SFDOREXT
GOTO LOOP
:DOOR_B
When this is completed, you will need to create a SFDOREXT.MNU file
as described earlier (in the SFMNUEXT MENU FILES section of this
documentation).
Next you will need to modify the included sample SFDOREXT.BAT to
include the program(s) you wish to run with your extended menu.
Notice the contents of the batch file provide the appropriate error
codes for the execution of each menu option. Further down the batch
file you will see:
:EXTEND_A
REM Place EXTENSION A Commands Here
GOTO LOOP
The commands you will need to run your desired option should be
placed between the :EXTEND_A and the GOTO LOOP statements in place
of the existing REM Place EXTENSION A Commands Here. These must be
valid DOS commands, program execution, etc.
Using The CALLBAT Utility In SF.BAT For SMNUEXT
-----------------------------------------------
The first thing you will need to do is modify your SF.BAT file
with your favorite text editor. Locate the line which contains
:DOOR_A. Your SF.BAT should look like this:
:DOOR_A
CALLBAT SFDOREXT
GOTO LOOP
:DOOR_B
When this is completed, you will need to create a SFDOREXT.MNU file
as described earlier (in the SFMNUEXT MENU FILES section of this
documentation).
Next you will need to modify the included sample SFDOREXT.BAT to
include the program(s) you wish to run with your extended menu.
Notice the contents of the batch file provide the appropriate error
codes for the execution of each menu option. Further down the batch
file you will see:
:EXTEND_A
REM Place EXTENSION A Commands Here
GOTO LOOP
The commands you will need to run your desired option should be
placed between the :EXTEND_A and the GOTO LOOP statements in place
of the existing REM Place EXTENSION A Commands Here. These must be
valid DOS commands, program execution, etc.
Including SFDOREXT.BAT Within The SF.BAT
----------------------------------------
Although not recommended, the contents of the SFDOREXT.BAT could
be included in the SF.BAT. To do this, simply copy the SFDOREXT.BAT
and place it between, for example, the :DOOR_A and GOTO LOOP command.
This however, greatly magnifies the size of the SF.BAT and using the
CALL command or CALLBAT utility is definately much preferred to
using this option.
Disabling the <G>oodbye Command
-------------------------------
SFMNUEXT provides callers logged on from a remote location with
the ability to log off the by use of the <G>oodbye command. The
<G>oodbye feature is ONLY available when someone is logged on from
a remote location. The <G>oodbye feature can be disabled for remote
callers by the use of a command line parameter. Executing SFMNUEXT
in the following manner will disable the <G>oodbye feature:
SFMNUEXT /NG
The /NG is derived from NoGoodbye. This information is provided
just to help you remember /NG. (smiling)
DISTRIBUTION
------------
SFMNUEXT is distributed under the shareware concept. You are free
to distribute the SFMNUEXT program as long as it remains unmodified and
no fee is charged. If you use this program and find it beneficial a
fee is required. A $1.00 fee is required of registered SPITFIRE Sysops
and a $5.00 fee is required of all others.
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 SFMNUEXT. All
responsibility lies with the user of the software.
The documentation for SFMNUEXT is contributed by Jacque Shipley and
The Mother Board BBS. The shareware version of SPITFIRE and other
SPITFIRE utilities are available for download from:
Buffalo Creek's BBS The Mother Board BBS
Mike Woltz, Sysop Jacque Shipley, Sysop
(515) 225-8496 (515) 986-3464
38400/19200/9600/2400/1200 Baud 19200/9600/2400/1200 Baud
REVISION: SFMNUEXT Version 1.3 - June 1, 1992
The ability to disable the <G>oodbye feature was added!
REVISION: SFMNUEXT Version 1.4 - November 20, 1992
Previous versions of SFMNUEXT would not display the command lines
when a caller would break out of a menu display. This has been
corrected.
REVISION: SFMNUEXT Version 1.5 - October 15, 1993
Added support for RIP Graphic format.
REVISION: SFMNUEXT Version 1.5a - January 26, 1994
SFMNUEXT was revised to recognize the use of an irregular IRQ