Source: SPITFIRE.DOCEdition: searchable Web reading editionPresentation: historical wording retained
4.0 - SETTING UP THE SYSTEM RECORDS
------------------------------------
Message Conference records and File Area records comprise your
SPITFIRE system records. There are two ways to set up the system
records in SPITFIRE. The first is by using ALT key combinations at
the SPITFIRE "Ready..." prompt. The second is through the Sysop Menu
which is accessed from the Main, Message or File Menus. SPITFIRE will
allow 784 different Message Conferences and 65535 File Areas.
4.1 CONFIGURING MESSAGE CONFERENCE RECORDS
-------------------------------------------
Message Conference records are configured by pressing ALT+R at the
"Ready" prompt or by selecting option <M> from the Sysop Menu. When
this is done the following will display to the screen:
Conference Description.. : "Untitled Message Conference"
Msg Conference Access... : Equal To Or Greater Than Caller Security
Public Messages Only.... : No Message Entry Security.. : 25
Conference Security..... : 5 Net-Mail Conference..... : No
Maximum Msg Length...... : 99 Purge Msgs Older Than... : 120 days
Caller Message Deletion. : Yes Purge Unreceived Msg.... : No
Delete Old Thread Msg... : Yes Net ID Name............. : UNTITLED MSG
Allow Message Routing... : No Privileged Securities... : 0;0;0;0;0
>>>> RECORD [1 Of 10] MESSAGE SYSTEM RECORD MENU <<<<<N>.......... Net-Mail Toggle <M>... Conference Description
<S>...... Conference Security <@>........ Conference Access
<#>............ Record Number <A>........... Add New Record
<P>..... Public Messages Only <C>...... Caller Msg Deletion
<I>.....Insert New Conference <D>........ Delete Conference
<O>.........Old Message Purge <U>......Unreceived Msg Purge
<+>.......... Next Conference <->...... Previous Conference
<T>..... Purge Old Thread Msg <L>........Maximum Msg Length
<R>.... Allow Message Routing <E>....Message Entry Security
<!>...............Net ID Name <&>.... Privileged Securities
ENTER COMMAND - [N M S @ # A P C I D O U + - T L R E ! & <Q>uit ]?
Command <N> - Net-Mail Toggle
Allows the Sysop to configure whether an individual
message conference will allow net-mail. If a message
conference is set up to allow net-mail, callers are
allowed to leave messages to a person who is not a caller
on the BBS. If a message conference is not configured to
allow net-mail a caller can only leave messages to other
callers of the BBS. (This also applies to Carbon Copy
messages.)
Command <M> - Conference Description
You will notice that the default Message Conference
description is "Untitled Message Conference". Change
this to suit your needs. As an example, you may wish to
change the description of this conference to "Public
Messages".
Command <S> - Conference Security
This allows you to set the security level for this
Message Conference. You will notice that the default
security level is 5, which means that any caller with a
security of 5 or greater will be able to read messages
in this conference. If you wish to set a different
security level for this Message Conference, then select
<S> to change the security level of the conference.
Command <@> - Conference Access
You will note that SPITFIRE defaults the Message
Conference Access to "Equal To Or Greater Than". What
this means is that any caller with a security level equal
to or greater than the security level of this Message
Conference can access it. If you select <@>, SPITFIRE
will toggle this feature to "Equal To Caller Security"
and only callers with a security level equal to the
security level of the Message Conference will be able to
access this conference. Callers with a security level
greater than or less than the security level of this
conference will not be able to access this conference
(unless the caller has Sysop security or whose security
is equal to a specified Privileged Security).
Command <#> - Record Number
Allows you to enter a specific Message Conference record
number. After entering the number, the information for
the record number you specified is displayed.
Command <A> - Add New Record
Allows the Sysop to add a new Message Conference to the
Message base. The new record will be added after the
last existing Message Conference record. For instance,
if your system has 25 Message Conferences and the <A>
option is selected, a Message System Record Number 26
will be added.
Command <P> - Public Messages Only
Toggles whether the Message Conference will allow
non-public messages. The default setting of SPITFIRE is
to allow non-public messages. By selecting <P> you can
toggle this feature so that only messages marked as
public are allowed.
Command <C> - Caller Msg Deletion
Toggles whether a caller of the BBS is allowed to delete
messages. If set to Yes, the caller will be able to
delete messages either sent to or sent by them. If
this is toggled to No, a caller will not be allowed to
delete any messages. This option is set for each message
conference individually. You may toggle it one way for
one message conference and the other for another message
conference.
**** Although Buffalo Creek Software offers the Caller Deletion option
which the Sysop can use to configure whether a caller is allowed
to delete messages in SPITFIRE, it assumes no responsibility for
Sysops who use this feature. Legal judgments concerning the
ownership of messages on a bulletin board system could possibly
hold Sysops liable for denying callers control of their posted
messages.
Command <I> - Insert New Conference
Inserts a new Message Conference record between two
existing Message Conference records. Upon selecting
this option, SPITFIRE displays the prompt "Insert before
which conference?". A new Message System Record is
inserted preceding the Message System Record number
that is entered here.
***IMPORTANT NOTE***
When inserting a new Message Conference the SFMSG<x>.DAT,
SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR files are
automatically reset to correspond to the appropriate
Message Conference. For example, assume the BBS has
five active Message Conferences and a new Message
Conference is inserted prior to Message Conference #4.
The new Message Conference becomes Message Conference
#4. The previous Message Conference #5 now becomes
Message Conference #6 and the SFMSG05.DAT, SFMSG05.PTR,
SFMSG05.IDX and SFMSG05.LMR are appropriately renamed to
SFMSG06.DAT, SFMSG06.PTR, SFMSG06.IDX and SFMSG06.LMR.
The previous Message Conference #4 now becomes Message
Conference #5, and the SFMSG04.DAT, SFMSG04.PTR,
SFMSG04.IDX and SFMSG04.LMR are appropriately renamed to
SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.PTR.
SPITFIRE will also rename any SFMSG<x>.BBS/CLR/RIP
when a Message Conference is inserted. For example,
let's assume there are 25 Message Conferences on the
BBS. If a Message Conference is <I>nserted before
Message Conference #23, SFMSG25.BBS/CLR/RIP would be
renamed to SFMSG26.BBS/CLR/RIP, SFMSG24.BBS/CLR/RIP
would be renamed to SFMSG25.BBS/CLR/RIP, and
SFMSG23.BBS/CLR/RIP would be renamed to
SFMSG24.BBS/CLR/RIP.
Command <D> - Delete Conference
This option allows an existing Message System Record to
be deleted. Upon selecting this option SPITFIRE displays
the prompt "Delete which conference?". The number entered
here will cause that Message Conference to be removed.
***IMPORTANT NOTE***
When deleting an existing Message Conference the
SFMSG<x>.DAT, SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR
files are automatically reset to correspond to the
appropriate Message Conference. For example, let's again
assume the BBS has five active Message Conferences and
Message Conference #4 is deleted. The pre-existing
SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR
files are deleted when Message Conference #4 is deleted.
The previous Message Conference #5 now becomes Message
Conference #4. The SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX
and SFMSG05.LMR are appropriately renamed to SFMSG04.DAT,
SFMSG04.PTR, SFMSG04.IDX and SFMSG04.PTR.
SPITFIRE will also rename any SFMSG<x>.BBS/CLR/RIP
when a Message Conference is deleted. For example,
let's assume there are 25 Message Conferences on the
BBS. If a Message Conference #23 is <D>eleted, SPITFIRE
would rename SFMSG24.BBS/CLR/RIP to SFMSG23.BBS/CLR/RIP
and SFMSG25.BBS/CLR/RIP would be renamed to
SFMSG24.BBS/CLR/RIP.
Command <O> - Old Message Purge
Specifies how many days old a message in this particular
conference must be prior to it being purged during
SPITFIRE's message packing procedure. For instance, if
this is set to 120 days, when SPITFIRE packs this message
conference any messages older than 120 days will be
purged.
Command <U> - Unreceived Msg Purge
Specifies whether messages which are unreceived are
allowed to be purged from the Message Conference. If
set to Yes, when packing the message base any messages
older than the days set with the <O>..Old Message Purge
option will be purged even if they have not yet been
received. If set to No, unreceived messages will not be
purged.
Command <+> - Next Conference
This option is used to move forward from one Message
System record to another. Pressing the "+" key
initiates the progression from one Message Conference
record to the next in sequential order. Upon reaching
the last record, if the "+" key is pressed, SPITFIRE
will cycle to the first Message System record.
Command <-> - Previous Conference
This option is used to cycle through the Message
System records in reverse order. Pressing the "-" key
causes the previous conference number to be displayed.
From the first Message System record, if the "-" key is
pressed, SPITFIRE will cycle to the last Message
System record.
Command <T> - Purge Old Thread Msg
This option allows the Sysop to designate whether
threaded messages will be deleted when using SPITFIRE's
SFPCKMSG message packer. If this is toggled to Yes,
when the message base is packed, threaded messages
older than the days set with the <O>..Old Message Purge
will be deleted. If toggled to No, threaded messages
will not be deleted from the message base.
Command <L> - Maximum Msg Length
The option allows the Sysop to configure the maximum
lines that will be allowed per message in this message
conference. Valid options range from 25 lines to 99
lines. For instance, if 50 is entered, the maximum
length for all messages in this conference would be
50 lines.
Command <R> - Allow Message Routing
The Routing option is only applicable if the message
conference has been configured as a net-mail conference.
When set to Yes (and you are using BCSUTI Version 1.0 or
greater or responding to a message imported through
Buffalo Creek's SHILOH netmail system) SPITFIRE will
automatically default the message routing information
for you. Otherwise, you will need to manually enter the
message routing information.
The Routing feature also works with carbon copy messages.
So it is possible to send the same message to 10 different
people, routing it to 10 different locations.
When entering a routed message, SPITFIRE allows the
caller to specify whether the message should be sent as
public or non-public. SPITFIRE allows a caller to enter
a routed, non-public message even though the conference
has been configured to allow public messages only.
Command <E> - Message Entry Security
This option allows the Sysop to configure the security
level required before a caller is allowed to enter a
a message in this Message Conference. A caller whose
security is equal to or greater than the security entered
here will be allowed to enter messages in this Message
Conference. A caller whose security is less than the
security configured here will not be allowed to enter a
message in this Message Conference. To configure a
Message Conference as read-only, simply configure this
option at a value equal to or greater than the highest
security level of any caller. It should be noted that
if a caller receives a message in a Message Conference
where the caller's security is less than the configured
Message Entry Security, the caller will not be allowed
to reply to the message. Also, if a caller's security
is equal to a configured privileged security, the caller
will be allowed to enter messages in the conference even
though the caller's security might be less than the
configured Message Entry Security.
Command <!> - Net ID Name
When this feature is selected, the Sysop can configure
the Net ID Name for this conference. The Net ID Name
is a shortened conference description name used by LAKOTA,
(SPITFIRE's QWK Mail System), SHILOH (Buffalo Creek's
Netmail System) and BCSUTI (Buffalo Creek's UTI utility)
If the Sysop does not configure this, the Net ID Name
defaults to the first 15 characters from the Message
Conference description. (LAKOTA uses the first 13
characters of the Net ID Name while BCSUTI and other
mail exchange programs may use the full 15 characters.)
Command <&> - Privileged Securities
This feature allows the Sysop to configure up to five
privileged security levels per Message Conference. If
a caller logs on and has a security level equal to a
security assigned here, the caller will have access to
this Message Conference regardless of how the Message
Conference Security and the Message Conference Access
options have been configured. In other words, the
privileged security will always override the Security
and the Access configuration for the Message Conference.
A caller with a privileged security may also enter
messages in the conference even though the caller's
security might be less than the configured Message Entry
Security. As an example, assume a Message Conference has
been configured only to allow callers with a security
level greater than or equal to 50. Also, assume that 30
is configured as a privileged security. If a caller with
a security of 30 logs onto the BBS, the caller will have
full access to that particular Message Conference.
Command <Q> - Quit
Upon selecting this option, SPITFIRE will return to the
place from which the Message System Record Menu was
initiated. In other words, if invoked from the Sysop
Menu, SPITFIRE will return to the Sysop Menu. If
initiated from the "Ready..." prompt, SPITFIRE will
return to the "Ready..." prompt.
4.2 - CONFIGURING FILE AREA RECORDS
-----------------------------------
File Area records are configured by pressing ALT+F at the "Ready"
prompt or by selecting option <F> from the Sysop Menu. When this is
done the following is displayed to the screen:
Download Path..... : C:\SF
Upload Path....... : C:\SF
Area Description.. : "Untitled File Area"
Area Access....... : Equal To Or Greater Than Caller Security
Area Security..... : 5 No Charge (FREE) Area.. : No
Preview Area...... : No Privileged Securities.. : 0;0;0;0;0
CD Rom Area....... : No
Search File Area.. : Yes
>>>> RECORD [1 Of 10] FILE SYSTEM RECORD MENU <<<<<F>......... Area Description <U>.............. Upload Path
<D>............ Download Path <S>............ Area Security
<@>.............. Area Access <R>............ Record Number
<A>............. Add New Area <I>.......... Insert New Area
<P>............... Purge Area <T>...... Toggle Preview Area
<+>................ Next Area <->............ Previous Area
<C>...............CD Rom Area <$>......... Search File Area
(N>.....No Charge (FREE) Area <&>.... Privileged Securities
ENTER COMMAND - [F U D S @ R A I P T + - C $ N & <Q>uit ]?
Command <F> - Area Description
Notice that the default File Area description is
"Untitled File Area". Change the area description so it
appropriately describes the types of files stored in this
particular file area. For example, if the files in this
area could be categorized as system utilities, a suitable
description for this area might be "Utilities". Select
<F> to make this change.
Command <U> - Upload Path
To change the upload path, simply select <U> from the
menu. The Upload and Download paths are any legal DOS
path names telling SPITFIRE where it can find the files
associated with the File Area. It is possible to
configure uploads to go into a single "Recent Uploads"
File Area, or to different areas which you could specify
by subject. Here are a few examples of upload/download
paths:
The following example sends uploads to a sub-directory
called "UPLOADS" and allows the caller to download
programs from a sub-directory called "UTILITIES". (Note:
SF is the parent directory.)
Download Path.....C:\SF\UTILITIES
Upload Path.......C:\SF\UPLOADS
In the following example, uploads are sent to the same
sub-directory where the files available for downloading
exist:
Download Path.....C:\SF\UTILITIES
Upload Path.......C:\SF\UTILITIES
If you're running the BBS on a floppy-based system with
upload and download files on drive B, and not using
sub-directories, you could do the following:
Download Path.....B:\
Upload Path.......B:\
Command <D> - Download Path
You will notice that SPITFIRE sets the default download
path to the directory where SPITFIRE resides. To change
this DOS file path, select <D> to set the path for this
File Area. In the event that the file path set does not
exist, SPITFIRE will create it. For example, if you
set your download path to C:\UTILITY and the utility
directory doesn't exist on your drive, SPITFIRE will
create the directory. You will also notice once you
have entered the drive letter, SPITFIRE automatically
adds the colon ":" and the backslash "\" after it. If
an invalid path is entered, SPITFIRE will not accept it.
You will have to copy the files you want available for
download into this directory and create a SFFILES.BBS
(text file listing the files available for download) in
that directory. The SFFILES.BBS file must also reside in
that directory. (The utility, SFFILESA, which creates
your SFFILES.BBS for each file directory, is available
for download from Buffalo Creek's BBS - 515-225-8496.)
If the File Area is configured as a CD Rom File Area,
a SFFILES.<x>, where <x> represents the File Area number,
will need to be created and placed the directory that
is configured as the Display file path. SFFILES.<x>,
like SFFILES.BBS, is a text file listing the files
available for download for that file area.
To use SPITFIRE's extended download directory feature,
create an FA<x>.TXT, where <x> is equal the File Area
number, and place it in the SPITFIRE home directory.
FA<x>.TXT is a simple text file which can be created
using your favorite text editor, as long as it saves
in ASCII text. Each line of FA<x>.TXT should contain
the drive and directory of any extended download
directories for the File Area. For instance, if File
Area 5 was configured for Games, the contents of the
FA5.TXT in the SPITFIRE Home directory might look like
this:
F:\GAMES
G:\NEWGAMES
If SPITFIRE does not find the file to download, read,
view, etc. in the configured download directory (the
primary download directory) it will then look for the
appropriate FA<x>.TXT in the SPITFIRE Home directory.
The number of extended download directories can be
configured using FA<x>.TXT is unlimited. However, the
SFFILES.BBS in the primary download directory (or the
SFFILE.<x> for areas configured as CD Rom file areas)
should list all files available for downloading from
all download paths, including any extended download
directories.
The FA<x>.TXT, extended download directory feature,
provides additional CD Rom support. However, the Sysop
should be aware when using this feature that if the File
Area is not configured as a CD Rom File Area and the file
to be downloaded exists on a CD Rom disc, the file is
directly transferred to the caller from the CD Rom drive
rather than being copied to the disk drive. Secondly, if
the File Area is configured as a CD Rom File Area and the
ALT+T's Search CD Rom Area SFFILES.BBS is toggled to Yes,
SPITFIRE will search the SFFILES.<x>, rather than the
drive. Therefore, the file must be listed in the
SFFILES.<x> in order for SPITFIRE to find the file.
Command <S> - Area Security
This allows you to set the security level for this File
Area. You will notice that the default security level
is 5, which means that any caller with a security of 5
or greater will be able to access this File Area. If you
wish to set a different security level for the File Area,
then select <S> to change the security level of the area.
Command <@> - Area Access
Note that SPITFIRE defaults to the File Area Access of
"Equal To Or Greater Than". This means that callers with
a security level equal to or greater than the security
level of this File Area can access it. If you select
<@>, SPITFIRE will toggle this feature to "Equal To
Caller Security". Then only callers with a security
level equal to the security level of the File Area will
be able to access this area. Callers with a security
level greater than or less than the area security level
will be unable to access it, except those callers with
Sysop security or a security equal to a configured
privileged security.
Command <R> - Record Number
This option allows you to enter a specific File Area
record number. Upon entering the number, all current
information for the record number you specified is
displayed.
Command <A> - Add New Area
By selecting the <A> option, a Sysop can add a new
File Area Conference to the File Area System Records.
The new record will be added after the last existing
File Area System Record. For instance, if your system
has 25 File Areas and the <A> option is selected, a File
Area Record Number 26 will be added. SPITFIRE will
allow up to 65,535 File Areas.
Command <I> - Insert New Area
By selecting <I>, a Sysop can insert a new File Area
System Record between two existing file areas. Upon
selecting this option, you are prompted with "Insert
before which area?". A new File Area System Record
will be inserted preceding the File Area System Record
entered here.
*** IMPORTANT NOTE ***
SPITFIRE will rename any SFFILES.<x> or FA<x>.TXT file
area listings which are affected by inserting a new file
area record. For instance, let's assume that a BBS is
configured as having 25 file areas, and File Area #24 and
File Area #25 are CD-Rom file areas which use SFFILES.24
and SFFILES.25 to list files available in those areas.
Next assume a file area is inserted before File Area #24.
SPITFIRE will automatically rename SFFILES.25 to
SFFILES.26 and SFFILES.24 to SFFILES.25 when it inserts
the new file area. Similarly, if in the same scenario,
the BBS utilized a FA24.TXT and a FA25.TXT, FA25.TXT
would be renamed to FA26.TXT and FA24.TXT would be
renamed to FA25.TXT when the new file area is inserted.
SPITFIRE will also rename any SFIL<x>.BBS/CLR/RIP when a
new File Area is inserted. For example, let's assume
there are 25 File Areas on the BBS. If a new File Area
<I>nserted before File Area #23, SFIL25.BBS/CLR/RIP would
be renamed to SFIL26.BBS/CLR/RIP, SFFIL24.BBS/CLR/RIP
would be renamed to SFIL25.BBS/CLR/RIP, and
SFIL23.BBS/CLR/RIP would be renamed SFMSG24.BBS/CLR/RIP.
Command <P> - Purge Area
This option allows an existing File Area System Record
to be deleted. Upon selecting this option, you will be
prompted with "Delete which area?". The number that you
enter here will cause that File Area to be removed from
the File Area System Records. When a File Area is
purged, the subsequent File Area system records are
appropriately reset in sequential order. For instance,
if there are 15 File Areas on a system and File Area
12 is purged, File Area record 13 becomes 12, File Area
record 14 becomes 13 and File Area record 15 becomes 14.
*** IMPORTANT NOTE ***
SPITFIRE will rename any SFFILES.<x> or FA<x>.TXT file
area listings which are affected by deleting an existing
file area record. For instance, let's assume that a BBS
is configured as having 25 file areas, and File Area #24
and File Area #25 are CD-Rom file areas which use
SFFILES.24 and SFFILES.25 to list files available in those
areas. Next, assume that File Area #23 is deleted.
SPITFIRE will automatically rename SFFILES.24 to
SFFILES.23 and SFFILES.25 to SFFILES.24 when it deletes
the existing file area. Similarly, if in the same
scenario, the BBS utilized a FA24.TXT and a FA25.TXT,
FA24.TXT would be renamed to FA23.TXT and FA25.TXT would
be renamed to FA24.TXT when the file area is purged.
SPITFIRE will also rename any SFIL<x>.BBS/CLR/RIP when a
File Area is purged. For example, let's assume
there are 25 File Areas on the BBS. If File Area #23
is purged, SFIL24.BBS/CLR/RIP would be renamed to
SFIL23.BBS/CLR/RIP and SFFIL25.BBS/CLR/RIP would be
renamed to SFIL24.BBS/CLR/RIP.
Command <T> - Toggle Preview Area
The "T" option will toggle a File Area's Preview Area
option between Yes and No. If Preview Area is toggled
to Yes, a caller with a security less than the required
Area Security will be allowed limited access to preview
this file area. This means that the caller can access
this file area, list files, read text files, view file
archives, etc. but will not be allowed to download any
files from this area. In other words, the caller can do
everything except download from this file area. If this
is toggled to No, callers with a security less than the
specified Area Security will not be allowed access to
this File Area.
Command <+> - Next Area
This option is used to move forward from one File Area
System record to another. Pressing the <+> key will
progress forward from one record to the next in
numerical order. When reaching the last record and
the <+> key is pressed, SPITFIRE will cycle to the first
File Area System record.
Command <-> - Previous Area
This option cycles through the File Area System
records in reverse order. Pressing the <-> key
will display the preceding record number. From the
first File Area System record if the <-> key is pressed
SPITFIRE will cycle to the last File Area System record.
Command <C> - CD Rom Area
The option specifies the file area as a CD Rom Area.
If this is toggled on, then SPITFIRE searches the Display
File Path for a SFFILES.<x> for the file listing of this
CD Rom Area. The <x> should correspond with the number
of the file area. For instance, if File Area 15 is
configured as a CD Rom Area then the file listing would
need to be named SFFILES.15. If SPITFIRE finds any file
areas configured as CD Rom Areas it does not report
file statistics for the BBS when listing <N>ew Files
at log on or from the File Menu.
When a caller elects to download a file from a CD Rom
File Area, SPITFIRE copies the file from the CD Rom to
the disk drive. SPITFIRE creates a sub-directory off the
configured Work directory and names the sub-directory
it creates CDROM<node number>. For example, if the
configured Work directory of node 2 is C:\SF2\WORK,
then the sub-directory created by SPITFIRE would be
C:\SF2\WORK\CDROM2. The file which is copied to this
directory is erased, however, the sub-directory is not
removed.
Command <$> - Search File Area
Allows Sysops to configure whether the download path
for the File Area will be searched for duplicate files
when a caller attempts an upload. If this is toggled
to Yes, the download path will be searched and if this
is toggled to No, the download path will not be searched.
As an example, Sysops using a CD Rom file area may wish
to skip the search for these areas due to the time that
is required to scan these areas.
** NOTE ** For a File Area configured as a CD Rom File
Area, if the Search CD Rom Area SFFILES has been toggled
to Yes from the Toggle SPITFIRE Switches configuration
window and the File Area's record Search File Area option
is configured to Yes, then the SFFILES.<x> is searched
for duplicate files rather than the drive/directory
listing.
Command <N> - No Charge (FREE) Area
Allows the Sysop to configure whether a File Area will
be a free File Area. If this option is toggled to Yes,
a caller may download files from this area and the
caller's statistics (number of files downloaded and
kilobytes downloaded) will not be updated. When toggled
to No, files downloaded from this area will update the
caller's statistics, increasing the number of files and
the kilobytes downloaded for each file that is downloaded
from this area.
Files may be downloaded from a File Area configured as
a No Charge (FREE) Area even if the download would
cause the caller to exceed the daily file and/or daily
byte limit configured by the Sysop in DAILYLMT.DAT.
Command <&> - Privileged Securities
This feature allows the Sysop to configure up to five
privileged security levels per File Area. If a caller
logs on and has a security level equal to a security
assigned here, the caller will have access to this File
Area regardless of how the File Area Security and the
File Area Access options have been configured. In other
words, the privileged security will always override the
Security and the Access configuration for the File Area.
As an example, assume a File Area has been configured
only to allow callers with a security level greater than
or equal to 50. Also, assume that 30 is configured as a
privileged security. If a caller with a security level
of 30 logs onto the BBS, the caller will be granted
access to that particular File Area.
Command <Q> - Quit
Selecting this option will return you to the place in
SPITFIRE from where the File System Record Menu was
called. In other words, you will be returned either
to the Sysop Menu or the "Ready..." prompt. SPITFIRE
will automatically save your newly configured System
Record.