/=======================================\
< T.A.G. Version 2.6 Update Documentation >
\=======================================/
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
/\/\/\/ [>> Welcome to <<] \/\/\/\
| /\/ ______________ ______ ___________ \/\ |
| / / / /| / /| / /\ \ \ |
| / / TTTTTTTTTTTTTT/ AAAAAA /| GGGGGGGGGGG\/| \ \ |
|/\/ /\ TT | AA|___AA /| GG | GG/ /\ \/\|
|-< < > TT | AA/ AA /| GG | _____ < > >-|
|\/\ \/ TT | AAAAAAAAAAAA | GG | / /| \/ /\/|
| \ \ TT | AA | AA | GG |__GGGGGG | / / |
| \ \ TT | AA | AA | GG/ GG | / / |
| \/\ TT/ <> AA/ AA/ <> GGGGGGGGGGG/ <> /\/ |
\/\/\/\ /\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
_____________________________________________________________
/ \
( T.A.G. 2.6 - Copyright (C) 1986-1992 Robert Numerick, )
\________________ and Victor Capton. _________________/
\__________________________/
T.A.G. BBS Version 2.6 - Update Documentation - Page 1
*****************************
* A Word About This Release *
*****************************
This has been the longest period in our history without a release of
T.A.G. We have not gotten everything done or tested it as well as we
should. This release clearly demonstrates that T.A.G. is a hobby for
all those involved. Life is full of problems and they certainly have
effected T.A.G. directly this time around.
I'll be honest in stating that we expect to have a maintenance release
out within a month of this release. There are no serious problems that
we are aware of currently, but due to the extensive changes, there are
bound to be some minor problems. Hopefully no serious ones have made
it through testing.
Paul has promised a multi-user release within about a week of this
release. There still is a bit of work to be done cleaning it up and
you'll have plenty to do with this release as it is.
Thanks to everyone who has hung in there and put up with everything
that has been going on.
Best wishes to all for a safe and happy holiday season,
The T.A.G. Team
T.A.G. BBS Version 2.6 - Update Documentation - Page 2
******************************
* Documentation Organization *
******************************
This documentation update is divided into two sections. The sections
correspond to each of the original version 2.5g files.
The first section contains things that would appear in the main
documentation file, while the second contains updates to the menu
documentation file.
In trying to eliminate duplication, there are many new features
mentioned in the menu update documentation which are not mentioned in
the first section. It would be well advised to look over both
sections.
Because this is an update it is still necessary to have the older
T.A.G. 2.5g documentation files (TAGD25G.ZIP).
Completely updated documentation should be available with the next
maintenance release.
T.A.G. BBS Version 2.6 - Update Documentation - Page 3
/=============================================\
< T.A.G. Version 2.6 Main Update Documentation >
\=============================================/
*** T.A.G. now has completely internal ANSI drivers. ANSI.SYS or
other similar drivers are no longer required to run the system.
This eliminates the possible use of ANSI redefinition/mode/etc
codes from within T.A.G. itself (any external programs you run are
outside of T.A.G.'s control).
A notably improved speed difference exists from previous versions
of T.A.G.
In addition the SysOp window will no longer turn off and on during
ANSI screens (unlike previous versions).
NOTE: In order for the Sysop to see some ANSI screens
completely the SysOp window must be closed. The Sysops
screen may become garbled at the bottom of the display
if to top window is not closed. The users display is NOT
affected.
*** The message system now offers an interactive spelling checker
built internal to the editor. This feature is optional and need
not be used (because of the extra disk space it requires,
approximately 700k with the current dictionary).
If desired, place the dictionary files (MAIN.DIC and MAINIDX.DIC)
in the directory specified under "System Information" of your
configuration. A separate archive, TAGW26.ZIP (W=Words) contains
the required dictionary files.
Two modes of checking are supported, Interactive and non-
interactive. In non-interactive mode the system relists the
message and checks the spelling of each word. Words which were
not found in the dictionary are highlighted for visual
identification. In interactive mode, the user is prompted at each
unrecognized word, and given options, including "suggestions" for
words similar to the unrecognized word.
*** The original programmable string files have been eliminated and
replaced by a more flexible system. The strings are divided up
into two categories. Those that are "ok" for the SysOp change,
and "system" strings that should not be changed.
If you change the "system" strings, it is very likely that a
future release of T.A.G. will require you to make the changes
again.
T.A.G. BBS Version 2.6 - Update Documentation - Page 4
SDR Codes are completely supported in the programmable strings.
The structure of the string (*.TXT) files is as follows:
*[!]<Key Word>
<Text>
<Text>
..
..
<Text>[@@@]
*
Each string begins with a "*", optionally followed by a "!" if it
can be aborted, followed by a key word which identifies the
string. The next one or more lines contain the actual string
itself, with the last line ending with "@@@" if it is a prompt
(e.g. for input by the user, etc). The string is ended by a line
containing only a "*". Any text can appear before or after
strings as comments so long as the line does not begin with a "*".
The following files are used by the new system:
TAGSTR.EXE Compiler for the string files. When executed
the program searches the current directory for
all string files and compiles them. These
include MSTRMSG.TXT, MSTRCLR.TXT, TSTRMSG.TXT,
and TSTRCLR.TXT.
MSTRDEF.TXT User string default file - Contains the
default values for those strings which are
"ok" to override. NEVER EDIT!
MSTRMSG.TXT User string override file (NON-ANSI) -
Contains the user strings you which to
override the default values of. This file
should not contain ANSI codes. Internal color
codes are fine because they are filtered out
for non-ANSI users (control-C followed by a
number).
MSTRMSG.DAT Compiled version of MSTRMSG.TXT (strings not
found in MSTRMSG.TXT are read from
MSTRDEF.TXT).
T.A.G. BBS Version 2.6 - Update Documentation - Page 5
MSTRCLR.TXT User string override file (ANSI) - Contains
the user strings you wish to override the
default values of. These strings are
displayed to users who have ANSI. If the
string is not found in the compiled version of
this file, T.A.G. will read the MSTRMSG
version to get the string. Because of this
dual read requirement it may be wise to have
all strings defined in this file unless you
have a fairly fast machine (if you plan to use
it at all).
MSTRCLR.DAT Compiled version of MSTRCLR.TXT.
TSTRDEF.TXT System string default file - Contains the
default values for those strings we suggest
not be changed. NEVER EDIT!
TSTRMSG.TXT System string override file (NON-ANSI) -
Contains the system strings you wish to
override the default values of. This file
should not contain ANSI codes. Internal color
codes are fine because they are filtered out
for non-ANSI users (control-C followed by a
number).
TSTRMSG.DAT Compiled version of TSTRMSG.TXT (strings not
found in TSTRMSG.TXT are read from
TSTRDEF.TXT).
TSTRCLR.TXT System string override file (ANSI) - Contains
the system strings you wish to override the
default values of. These strings are
displayed to users who have ANSI. If the
string is not found in the compiled version of
this file, T.A.G. will read the TSTRMSG
version to get the string. Because of this
dual read requirement it may be wise to have
all strings defined in this file unless you
have a fairly fast machine (if you plan to use
it at all).
TSTRCLR.DAT Compiled version of TSTRCLR.TXT.
T.A.G. BBS Version 2.6 - Update Documentation - Page 6
*** T.A.G. now supports several command line parameters on boot up.
They may be proceeded by "/" or "-" but just the word is fine. It
is only necessary to include enough of the option to make it
unique (e.g. "A=100" is fine instead of "AFTERUSERERRLVL=100").
Multiple parameters are separated by a space. Supported
parameters are as follows:
AFTERUSERERRLVL=### After the next user logs off, exit
the system with the error level
specified.
BASEPORT=HHHH Change the communications port base
address to "HHHH" (in hexadecimal).
This option is not permanent.
COMPORT=# Change the communications port in
the system configuration to the
specified value permanently.
CONNECTRATE=######### Set the connect rate of the user to
the specified value and immediately
logon. This option and
AFTERUSERERRLVL can be used with a
front end mailer to boot T.A.G., log
the user on, and exit when they are
completed to reload the mailer.
CONTROLCODE=######### Immediately logon using the modem
result matching the control code
specified. This option and
AFTERUSERERRLVL can be used with a
front end mailer to boot T.A.G., log
the user on, and exit when they are
completed to reload the mailer.
ERRORCORRECTING Sets the immediate logon to an
"Error Correcting" connection.
EXITERRLVL=### Sets the "Standard" error level
T.A.G. exits with (normally 255).
FATALERRLVL=### Sets the "Fatal Error" error level
T.A.G. exits with (normally 0)
HALFDUPLEX Sets the immediate logon to a "Half
Duplex" connection.
IRQ=## Change the communications port IRQ
line to the value specified.
T.A.G. BBS Version 2.6 - Update Documentation - Page 7
LOCAL Disables all communication port
activity for the duration of the
session. This remains in effect
until exiting from T.A.G. The front
end mailer is temporarily disabled
and modem initialization is skipped.
LOGON Immediately logon locally. Use with
LOCAL to disable port activity for
multi-user systems.
REALRATE=######### Sets the immediate logon real baud
rate of the user to the value
specified.
STATUSPATH=<Path> Directory where the STATUS.DAT file
is located.
NOTE: You must specify CONNECTRATE, CONTROLCODE, or LOGON
first to initiate an immediate logon before including
AFTERUSERERRLVL, ERRORCORRECTING, HALFDUPLEX, or
REALRATE.
*** The upload archive testing system has been revised to be more
"generic" in nature. The single batch file FILETEST.BAT is now
used with the following parameters passed by T.A.G.:
%1 Path name of file to test (including trailing backslash)
%2 File name of file to test (no period/extension)
%3 Extension of file to test (no period)
To build the filename in the batch file "%1%2.%3" could be used.
All uploads now call this batch file, so it should check the
extension and only test those files which are of a known type.
See the default batch file included with the conversion package
for more information.
*** The (I)nterior list command in the file system now supports the
following new formats:
*.ARJ through version 2.2x
*.LZH through version 2.1x New compression types supported
*.ZIP through version 1.93a Hopefully this format will
remain constant for the 2.00
release.
Some work was done to better handle new types of compression for
the supported formats.
T.A.G. BBS Version 2.6 - Update Documentation - Page 8
*** The long unused field indicating the number of fatal errors on the
wait screen and in the usage log is now updated. Hopefully this
will still be zero! <grin>
*** A enhanced shell configuration system has been added.
<< Shell settings >>
1. Swap shell is normally active : No
2. Use expanded memory (EMS) if available: Yes
3. Use extended memory (XMS) if available: No
4. Memory usage priority setting : XMS over EMS
The shell swap system now supports XMS memory swap in addition to
the original EMS memory swap and disk swap. Options exist under
the "Shell settings" option in system configuration to enable the
swap, enable each type of memory types, and give priority to which
will be used first.
Show Log Swap
---- ---- -------
A. Front end mailer No Yes Default
B. External editor No Yes Default
C. External SysOp function key No Yes Default
D. Archive file testing No Yes Default
E. Logon No Yes Default
F. New logon No Yes Default
G. Post download No Yes Default
H. Post upload No Yes Default
I. Wait screen special function No Yes Default
J. TAGMail external reader No Yes Default
K. Wait screen terminal function No Yes Default
L. Welcome No Yes Default
Shell settings: (1-4,A-L,Q=Quit):
Each of the programs T.A.G. calls externally now has the following
configuration options:
Show - Allows the SysOp to set whether the system displays
a "loading external program" and "returning from
external program" message when the external file is
called.
Log - Allows the SysOp to set whether the system logs the
fact that the external program was called.
T.A.G. BBS Version 2.6 - Update Documentation - Page 9
Swap - Allows the SysOp to configure the swap setting for
each of the listed files. Options include:
- Follow the default setting when calling the
program
- Always swap when calling the program
- Never swap when calling the program
*** A new message/file section grouping system now exists. This
feature allows selective access/display of sections by the SysOp
or user. This is above and beyond the normal access settings.
The group system allows you to assign each message and file
section a "group number". Using the "Change Message or File
Section Group Mask" command (PKey="9") it is possible to isolate
the currently accessible sections to those matching the specified
group mask.
As an example, suppose you had a large selection of both "local"
and "echo mail" message sections. Often it is desirable to have
these sections separated from each other so that the local
sections will not be buried by the often high traffic in the echo
sections. To do this, we could leave each of the local sections
set to group 0 (the default group), and set each of the echo mail
sections to group 1. To start users off in the local sections,
you would go into system configuration, under general variables,
and set the default message group mask to "0". Then add two
commands to the message menu, one to change to echo mail sections
(PKey="9"; PData="M1") and one to change back to local sections
(PKey="9"; PData="M0"). Remember that the PData for the group
mask command is a "mask" of sections, so a PData of "M1-5,7,10-15"
is totally acceptable.
*** This version has an almost entirely rewritten FidoNet compatible
message system. It will fully support the Fido 1.MSG format for
messages AND will support *MULTIPLE* QuickBBS/RemoteAccess/Hudson
style message bases.
Major advantages:
1. Mail tossers will be able to toss directly into T.A.G.
message bases. No messy conversion program for proprietary
storage formats.
2. All the Fido/QBBS/RA/Hudson message base utilities will work
directly on T.A.G. message sections.
3. Doors like Silver Express, Blue Wave, etc. for off-line
reading of messages by your users will work on both local and
echo message sections (some extra setup required).
T.A.G. BBS Version 2.6 - Update Documentation - Page 10
4. Local message editors, like MsgEd or FrontDoor will be able
to read and write both local and echo mail messages directly.
5. Potential space saving by utilizing a QBBS/RA/Hudson format
message base (one large file/indexes) verses T.A.G.'s old
format or 1.MSG Fido format.
Description of new message editor fields:
Section : 26
A. Name : Net Mail
B. Path : E:\NETMAIL\
C. Format : Style = Net Type = Fido
D. Messages : Min = 0 Max = 999
E. Read menu : 0
F. Post file :
G. Start quote:
H. End quote:
I. Address : 1:120/120@FIDONET.ORG
J. EchoTag :
K. Origin :
1. Access : General SL=255/AR=@ Post SL=255/AR=@ Group number=0
2. Password : ""
3. SubOps : None
4. Handles : No
5. Anonymous : No
6. Allow ANSI : No
7. Mail Flags :
A. Name : Name of the message section to be displayed in
the areas list. Note that the name can be
longer than can be displayed.
B. Path : Directory in which the message files are
located. Fido 1.MSG format messages required
one directory per section, while
QBBS/RA/Hudson format messages all go in the
same directory.
C. Format : Message format is divided up into two parts,
style and type. Style indicates how the
messages should be used or processed. Type
indicates how the messages should be stored in
the directory.
T.A.G. BBS Version 2.6 - Update Documentation - Page 11
Style can take on the following values:
Local Local message area, no network
connection.
Echo Standard FidoNet public echo
mail.
Group Group mail public echo mail.
Netmail Standard FidoNet direct
public/private net mail.
Type can take on the following values:
Fido Fido 1.MSG format stores each
message in a separate file. A
separate directory is required
for each section.
RA QBBS/RA/Hudson format stores
all messages in one file with
indexes. Several sections can
be placed in the same
directory. A unique number
must be assigned to each
section to keep the messages
separated into different
sections.
D. Messages : Minimum and maximum number of messages to be
stored in the section. The minimum value
setting determines where messages will be
deleted in order to maintain the maximum.
Messages are deleted one after the minimum
setting, thus a minimum of 2 will delete at
message 3 when more than the maximum number of
messages exist in the section. Messages 1 and
2 will never be deleted. If the number of
messages in a section is much greater than the
maximum, T.A.G. will only delete a few
messages each time a message is posted in
order not to delay the user.
E. Read menu : Number of the read message menu to use for
this section. If this value is set to zero,
the default read message menu in the system
configuration will be used.
F. Post file : This field indicates a text file that should
be printed whenever a post is about to be made
in the section.
T.A.G. BBS Version 2.6 - Update Documentation - Page 12
G. Start quote : Override starting quote line for replies.
Quote strings may contain the following SDR
type codes:
@T Who the message was "to"
@F Who the message was "from"
@D Date original message posted
@N Time original message posted
@A Origin address of original message
@E EchoTag of original message
@@ "@" in string
H. End quote : Set ending quote line for replies. The
default ending quote is none. The same codes
listed above can be used in the ending quote
string.
I. Address : Alternate origin address to be used in this
section. If none is specified, the main
system default address is used.
J. EchoTag : This field contains the echo/group mail tag
which uniquely each network message section.
This field is written to the ECHOTOSS.LOG when
a post is made in the section.
K. Origin : Override the default origin line for echo mail
messages. The entire origin line can never be
longer than 79 characters.
1. Access : This field contains the general SL and AR flag
required for entry into the section, the post
SL and AR flag required to post in the
section, and the group number the section
belongs to.
2. Password : This defined the password required to enter
the section. SysOp's with a SL of 255 are not
required to enter the password.
3. SubOps : List of up to 10 user numbers who have SubOp
access to the section.
4. Handles : Indicates the status of handles in the
section. Values include allowing use of
handles, not allowing use of handles, or
forcing use of handles. Most local bases
should force the use of handles, while most
echo/group mail bases should not allow handles
at all (national policy).
T.A.G. BBS Version 2.6 - Update Documentation - Page 13
5. Anonymous : Indicates the status on anonymous messages in
the section. Values include allowing
anonymous messages, not allowing anonymous
messages, or forcing anonymous messages.
Echo/group mail sections normally should not
allow anonymous messages (national policy).
6. Allow ANSI : Indicates whether ANSI is allowed in the
section. Echo/group mail sections normally
should not allow ANSI codes (national policy).
7. Mail Flags : Default message flags for Netmail messages.
*** The "System Information" section of the system configuration now
contains a "Board address" field. If your system is hooked into a
FidoNet style network, you should specify your main default board
address.
*** The "System Information" section of the system configuration now
contains the "System Directories". Two new directories are now
present. The "Nodelist directory" indicates where T.A.G. can
locate the raw NODELIST.### file and the compiled NLINDEX.DAT file
generated by NLINDEX.EXE. See the TAGN26.ZIP for more
information.
*** The "Communication Configuration" section of the system
configuration has been re-written completely to provide better
support for advanced modems. The main screen below contains basic
general options from the original screen which are not specific to
the modem. The final option "E" indicates the currently selected
modem. There may be more than one modem defined in your
configuration.
<< Communications Configuration >>
A. No call reinit time: 30 minutes
B. Com-port number : 1
C. Carrier Detect Mask: 128 (Non-FOSSIL only)
D. Use FOSSIL driver : No
E. Modem configuration
Active modem: Courier HST Dual Standard (Variable/Fixed)
Communications: (A-E,Q=Quit): E
The main modem configuration screen contains specific information
about the modem configuration and the modem control strings.
T.A.G. BBS Version 2.6 - Update Documentation - Page 14
<< Modem Configuration >>
Record # : 1
S. Status : Active
A. Description: Courier HST Dual Standard (Variable/Fixed)
B. Character pacing delay : 10 milliseconds
C. Modem initialization speed : 38400 bps (Variable)
E. CTS/RTS hardware flow control: No
F. File transfer efficiency : Normal=95% ErrorCorrecting=115%
R. Result code configuration
<< Modem Control Strings >>
1. Pre-Init :"||`````"
2. Init :"ATZ|"
3. Answer :"ATA|"
4. Busy :"|``ATM0H1|"
5. Hangup 1st :"^-~^+"
6. Hangup 2nd :"~~~~^A^A^A~~~ATH0|"
7. After Hangup:"|``ATM0H1|"
8. Exit System :"^-"
Number of result codes: 22
Modem Edit: (1-8,A-F,I,Q,R,S,[,],?):
S. Status: Indicates whether the current modem has been
selected as the currently active modem. Pressing (S)elect
from this screen selects a modem.
A. Description: User entered text description of the modem and
setup type.
B. Character pacing delay: Number of milliseconds delay between
each character when sending modem control strings to the
modem.
C. Modem initialization speed: Speed at which the modem should
be initialized. An informational field also exists which
indicates whether the speed is locked or variable.
NOTE: This setting has NO EFFECT on any board operation!
The real baud rate in the result code configuration
controls what the port speed will be for any given
connect. For example, if you are locking your port
to 38400, the real baud rates should all be set to
38400.
E. CTS/RTS hardware flow control: Indicates whether RTS/CTS
hardware flow control should be active. In general this
should only be active if you are locking your communications
port. T.A.G. no longer requires use of a FOSSIL driver when
locking your communications port.
T.A.G. BBS Version 2.6 - Update Documentation - Page 15
F. File transfer efficiency: This field indicates the file
transfer efficiency of this modem for normal and error
correcting connects. In general 95% is a good value for
normal corrects, and 115% is good value for error correcting
data compression connects.
R. Result code configuration: Configuration of result codes for
this modem. See that section for more information.
The following special characters are used in modem control
strings:
Char. Name Action
----- --------------- ------------------------------
^ Carat Control code of next character
| Pipe, Split Bar Carriage return sent
` Accent Mark 1/20th second delay
~ Tilde 1/2 second delay
^- Carat & Minus Lower DTR line
^+ Carat & Plus Raise DTR line
1. Pre-Init: String sent the modem prior to normal
initialization string to clear modem buffer.
2. Init: Main initialization string sent to the modem to
prepare for a caller.
3. Answer: String sent to the modem in order to answer the
phone when a ring is detected.
4. Busy: String sent to the modem to busy the line (take the
phone off hook). This is used on the wait screen and during
events configuration to take the phone off the hook.
5. Hangup 1st: String sent to the modem as the primary attempt
to hangup on a caller. Normally this is set to just drop the
DTR line for a period and raise it again.
6. Hangup 2nd: String sent to the modem as the second attempt
to hangup on a caller if the primary string should fail.
Normally this string should attempt to exit to modem command
mode via the escape sequence and then hangup the caller.
7. After Hangup: String sent to the modem after a user logs off
the system.
8. Exit System: String sent to the modem when exiting T.A.G.
T.A.G. BBS Version 2.6 - Update Documentation - Page 16
The result configuration section contains a definition of each of
the result codes the modem may respond with during the process of
answering a call. In addition the result codes also define
various other actions based on a control code (errorlevel or boot
up parameter). Multiple results of the same type are defined in
most cases to take care of various responses.
Result number: 17
1. Type : Connect
2. Result string: "CONNECT 14400/ARQ"
3. Control code : 244
4. Connect rate : 14400 bps
5. Real rate : 38400 bps
6. Attributes : Full Duplex / Error Correction
Result Edit: (1-6,Q,[,],?):
1. Type: This field indicates the type of result code to be
defined. Valid values include:
Error Result normally means the modem did
not understand the command sent to
it (Normally "ERROR").
Ok Result indicates the modem accepted
the control string sent to it
(Normally "OK").
Ring Result indicates that a user is
calling the system (Normally
"RING").
No Carrier Result indicates that the connect
attempt has failed and no user is
on-line (Normally "NO CARRIER").
Connect Result indicates that a successful
connect with a user has been
established. The connect rate, real
rate, and attributes indicate the
characteristics of the connect.
Wait Screen Result indicates that the system
should remain at the waiting for
callers string. This is normally
used to define a front end mailer
error level to drop back to the wait
screen. BinkeyTerm uses error level
20 for this purpose; see the control
code field for information on
setting error levels.
T.A.G. BBS Version 2.6 - Update Documentation - Page 17
Local Logon Result indicates that the system
should immediately logon locally.
This is normally used to define a
front end mailer error level to
logon locally to the system.
BinkleyTerm uses error level 10 for
this purpose; see the control code
field for information on setting
error levels.
Shell Batch Result indicates that the system
should shell the batch file
specified in the "Result
String/Other" field. Upon returning
the system will prepare for another
caller.
Exit Error Level Result indicates that the system
should exit T.A.G. with the error
level indicated in the control code
field. This is used as a pass
through result from a front end
mailer to pass error levels outside
of the system.
Exit System Result indicates that the system
should exit T.A.G. normally just
like hitting (Q)uit from the wait
screen. This is normally used to
define a front end mailer error
level to shut down the system.
BinkleyTerm uses error level 1 for
this purpose; see the control code
field for information on setting
error levels.
2. Result string: This field indicates either the result string begin
sent from the modem or the name of a batch file for
"Shell Batch" type results. Every combination of
result string need not be defined. T.A.G. will
attempt to match the longest result code to each
string sent by the modem. For example
"CONNECT 9600/ARQ" would match
"CONNECT 9600/ARQ/HST" and "CONNECT 9600/ARQ/V32".
3. Control code : This field indicates either an error level to be
returned by an external mailer, or a boot up
command line number specified using the
"CONTROLCODE" parameter.
T.A.G. BBS Version 2.6 - Update Documentation - Page 18
4. Connect rate : This field indicates the connect rate of the user
on-line. This is actual speed the user is
transferring information from his/her modem to
yours. File transfer times are based off of this
value since it indicates what rate the user is
actually connected at.
5. Real rate : This field indicates the real rate of the user on-
line. This is the speed at which the computer
should send information from the serial port to the
modem. When locking your communications this value
should be the same for all "Connect" result codes.
Note that this field could be set to any value for
each result code. Setting this field correctly for
each result allows support of "Variable locking"
found on many new high speed modems (&B2 on newer
HST's).
6. Attributes : This field indicates the attributes of the
connection. The first attribute is an
informational value as to whether the connect is
"Full Duplex" or "Half Duplex". The second
attribute indicates whether we have a "Normal
Connect" or "Error Correction" connect. This value
determines which file transfer efficiency
percentage to use.
*** The "Single value security settings" section of the system
configuration now contains the following new fields:
3. SL-Add words to dictionary: SL security necessary for users
to (A)dd words to the dictionary. Note that words are
validated by the SysOp using the "Word Validation Command"
(PKey="R") so it is "OK" to let normal validated users add
words.
20. SL-Modify netmail msg flags: SL security necessary for users
to change netmail flags using the "/CHANGE" option in the
message editor. This level should be set fairly high since
random modification of these flags could cause a great deal
of trouble.
21. SL-Netmail file attach: SL security necessary for users to
attach a file to a netmail message. This level should be
fairly high as it is possible to send a large volume of files
using wild cards. Note that the (P)ost or (R)eply commands
must contain "A" in the PData to actually ask the user.
T.A.G. BBS Version 2.6 - Update Documentation - Page 19
22. SL-Netmail file request: SL security necessary for users to
request a file from another system. This level should be
fairly high as it is possible to request a large volume of
files using wild cards. Note that the (P)ost and (R)eply
commands must contains "R" in the PData to actually ask the
user.
D. KEY - Expired validation key: Validation key to use from the
"Access Validation Editor" to validate users with after their
accounts expire. Note that each time the user logs onto the
system with an expired date they will be validated.
*** The "General variables" section of the system configuration now
contains the following new fields:
8. Default read message menu: This field indicates the default
read message menu to be used by the system. This menu is
used from the wait screen, when the users is logging on and
has mail waiting, and for each message section that does not
have an override value set. This menu must have a location
of "Read Message System".
20. Auto message maximum lines: This field indicates the maximum
number of lines the auto message may contain. NOTE: A totally
blank line will end input.
21. Default user edit list mode: This field indicates the
default listing mode when entering the user editor. You may
choose Short, Normal, Extended, or Informational.
A. Default message group mask: This field indicates the default
message section group mask when logging on the system. See
the section on "Message/File Group Masks" for more
information.
B. Default file group mask: This field indicates the default
file section group mask when logging on the system. See the
section on "Message/File Group Masks" for more information.
C. Menu fast command keys: This field defines the valid two
character fast menu keys. For example, in older versions the
"/G" command was normally defined to exit immediately, the
"/" key in this case is a menu fast command key. You may
define up to 20 fast command keys.
T.A.G. BBS Version 2.6 - Update Documentation - Page 20
*** The "Optional flagged functions" section of the system
configuration now contains the following new fields:
5. Show files open (debug): This field indicates whether the
system should show information about the number open files in
the top window. The first value is the total number of open
files. The second is the number of files currently open by
T.A.G.
6. Log modem activity (debug): This field indicates whether
detailed modem information should be written to the SysOp
log. When active all modem activity is logged which can help
greatly in debugging modem problems.
7. Wait screen action disable: This field indicates whether the
T.A.G. copyright message and time should be updated
constantly. Users of speech systems and/or certain multi-
tasking program make find this activity very annoying.
8. Dynamic message numbering: This field indicates whether the
system should dynamically renumber message sections. In
general terms this option will renumber the available message
sections starting at section 1, leaving no gaps where
sections are not accessible. This option is very handy
whether group masks are being used or when you do not wish
users to know they are "missing" sections.
9. Dynamic file numbering: This field indicates whether the
system should dynamically renumber file sections. In general
terms this option will renumber the available file sections
starting at section 0, leaving no gaps where sections are not
accessible. This option is very handy whether group masks
are being used or when you do not wish users to know they are
"missing" sections.
0. Forced voting at logon: This field indicates whether users
should be forced to vote when they are logging on before
being allowed to do anything else. CoSysOp's and above are
allowed to (Q)uit out of the voting section.
!. Warning days for user expire: This field optionally
indicates the number of warning days before a user's account
expires. The programmable string
"USER_ACCOUNT_EXPIRE_WARNING" is displayed when they are
within the specified range.
T.A.G. BBS Version 2.6 - Update Documentation - Page 21
*** Several new user fields are now available. These fields include
the following:
First on The user's first logon date. Existing
users will have the date they first logon
after this version was put on-line.
Expires The user's access expiration date. After
the specified date, the user is validated
using the validation key specified in the
"General variables" section of the system
configuration.
CLS message read Allows the user to configure whether the
system will clear the screen before
displaying each message.
Do not disturb Multi-user option which indicates whether
the user would like to be bothered by
other "nodes".
The remaining fields are completely configuration by the
SysOp using the programmable string system in combination
with the configuration new user logon described else where in
this document.
Phone number 2 Standard phone number
Extra string 1 Standard 40 character string (*1)
Extra string 2 ""
Extra string 3 ""
Extra date 1 Standard date field
Extra date 2 ""
Extra number 1 Standard number from 0-65533
Extra number 2 ""
Extra number 3 ""
Extra number 4 ""
Extra character 1 Standard single character field (*2)
Extra character 2 ""
Extra character 3 ""
Extra character 4 ""
Extra phone number Standard phone number
(*1) If the programmable configuration string called
"USER_EXTRA_STRING_#_LISTING" begins with a "~" the
string will not be printed when a user does a
"(L)ist" of their information from the standard
personal data menu.
(*2) Extra character fields have an additional
programmable configuration string called
"USER_EXTRA_CHAR_#_VALID" which indicates what
characters are valid entries by the user.
T.A.G. BBS Version 2.6 - Update Documentation - Page 22
*** The entire new user logon sequence in T.A.G. is now configurable.
Which questions are asked, the text of each question, what order
the questions are asked in, and whether questions are optional or
required is now completely configurable.
When making use of the extra user fields, the text of these fields
needs to be configured in the programmable string files.
All user related field information in the programmable string
files begin with "USER_".
<< New user questions >>
## Question Status ## Question Status
-- ----------------- -------- -- ----------------- --------
1 A Real Name Required 16 @ Inactive Optional
2 B Address Required 17 @ Inactive Optional
3 C City State Required 18 @ Inactive Optional
4 D Zip Code Required 19 @ Inactive Optional
5 E Phone Number 1 Required 20 @ Inactive Optional
6 G Computer Type Required 21 @ Inactive Optional
7 H Gender Required 22 @ Inactive Optional
8 I Birthday Required 23 @ Inactive Optional
9 J Maximum Baud Required 24 @ Inactive Optional
10 Y Columns/Lines* Required 25 @ Inactive Optional
11 Z Pause* Required 26 @ Inactive Optional
12 1 ANSI/Color* Required 27 @ Inactive Optional
13 2 Tabs* Required 28 @ Inactive Optional
14 @ Inactive Optional 29 @ Inactive Optional
15 @ Inactive Optional
New user questions: (1-29,A=All,Q=Quit):
This screen configures the new user question order and
required/optional status. When reconfiguring all questions, it is
recommend that the "All" option be used, otherwise questions can
be configured individually by entering the question number.
A list of the user question codes can be obtained at any
"Question: [@]: " prompt by pressing "?".
T.A.G. BBS Version 2.6 - Update Documentation - Page 23
*** Upon posting of an echo mail or net mail message the following
files are created as an aid to batch files in scanning for
outbound messages. These files are created in the main data files
directory (normally C:\BBS\GFILES or C:\BBS\DFILES):
ECHOTOSS.LOG Created by an echo mail post. This file is in
ASCII format and contains EchoTag's of each
section a post was made in, one line per
section.
NETTOSS.LOG Created by a net mail post. This file is just
a dummy file and does not contain anything.
*** The "|" option in the user editor now edits the user's gender.
The location of this field in the user record structure has
changed as thus it is no longer a special flag.
*** The Control-U user look-up commands now work in the following
areas:
- Word validation
- Removing a file
- Moving a file
- Message editor
*** The message editor has been completely rewritten with the new
message system. ANSI screens should no longer be corrupted in any
manner. Note that the actual upload of the screen make look funny
due to the fact T.A.G. does not know what you are about to type,
but if you re-list the message it should look fine.
The ANSI music character (Control-N) is now acceptable as part of
a message. The imbedded backspace key has been changed to
Control-B.
NOTE: In order to see ANSI screens completely the SysOp window
must be closed, otherwise corruption of the screen may
occur toward the bottom.
*** The number of public posts is no longer reset for new users. This
will allow setting of a starting number of posts for new users for
system that user post/call ratios.
*** The Mini-DOS editor has been replaced by a call to the new message
system editor.
T.A.G. BBS Version 2.6 - Update Documentation - Page 24
*** What follows is a definition of all the currently supported SDR
codes (this will save the trouble of looking back at the 2.5g
documentation):
** User SDR Codes **
To obtain user information, place a control-U (for user) in the
text followed immediately by one of the following letter codes:
A : Address B : Highest Baud C : City & State
D : DSL E : Special Flags F : AR Flags
G : Birthday H : Help Level I : Last DL Section
J : User Name K : Sysop Note L : Last on Date/Time
M : Mailbox Status N : First On Date O : Expiration Date
P : Phone Q : Unused R : Real Name
S : Security Level T : Computer Type U : User's First Name
V : Phone number 2 W : Unused X : Screen (Rows x Cols)
Y : Extra info (*) Z : Zip Code
1 : # of Downloads 2 : DL K-Bytes 3 : # of Uploads
4 : UL K-Bytes 5 : Number of Calls 6 : Total Time On System
7 : Calls Today 8 : Time On Today 9 : Unused
# : User Number $ : Debit / Credit * : Time On (hh:mm:ss)
^ : Points @ : Time Bank % : Time Left (minutes)
! : Time left (hh:mm:ss)
(*) The "Y" should be followed by a single letter:
A: Extra String 1
B: Extra String 2
C: Extra String 3
D: Extra Date 1
E: Extra Date 2
F: Extra Number 1
G: Extra Number 2
H: Extra Number 3
I: Extra Number 4
J: Extra Character 1
K: Extra Character 2
L: Extra Character 3
M: Extra Character 4
N: Extra Phone Number
T.A.G. BBS Version 2.6 - Update Documentation - Page 25
** System SDR Codes **
To obtain system information, place a control-S (for system) in
the text followed immediately by one of the following letter
codes:
A : Alternate Path B : Board Name C : Last Caller
D : Current Date E : Errors Today F : Unused
G : Main Data Path H : New Users Today I : Mail Address
J : Unused K : Unused L : Unused
M : Dictionary Path N : Total Calls O : Unused
P : Board Phone Q : Unused R : Unused
S : Sysop Name T : Current Time U : Multi-User Path
V : T.A.G. Version W : Unused X : Users
Y : Unused Z : Chat Password
1 : Max # Batch DL 2 : Max # Batch UL 3 : UL K-Bytes Today
4 : DL K-Bytes Today 5 : Calls Today 6 : Public Posts Today
7 : Priv Posts Today 8 : FeedBack Today 9 : # UL's Today
0 : # DL's Today # : MU Node Number % : Percent Activity
! : Current Date/Time Extended Format
** TAB SDR Codes **
The TAB SDR code is used to move to a particular column number
when displaying a line of text. To use the TAB, place a control-T
(for tab) in the text followed immediately by a two digit number
indicated the column number desired. The system will
automatically add the required number of spaces to the current
line to move to the specified column number. In the case where
the line is already longer than the specified column, no
characters are added. Note that SDR code will work with non-ANSI
users also.
*** The bulletin system will now display to the user which bulletins
are new since their last call. This is done by comparing the date
on any "BULLET??.*" files with the date which the user last logged
onto the system.
*** A new file called "COMPUTER.*" is now supported which replaces the
new user generated computer types listing from the COMPUTER.TXT
file. Note that the COMPUTER.TXT file is still required by T.A.G.
so it can access the individual names, but the listing displayed
can now be configured by the SysOp. The first entry in the
COMPUTER.TXT should be option "1" on the menu, the second entry
should be option "2", etc. The two files must correspond
otherwise different computer types will be saved in the user
record.
T.A.G. BBS Version 2.6 - Update Documentation - Page 26
*** A note to developers, a field now exists in the STATUS.DAT record
which indicates the last version of T.A.G. running with this
status file.
*** Voting records are no longer removed upon deleting a user. Why
this was done in the first place is beyond me. This should make
writing external user deleters a little easier.
*** By placing "#ABORT OFF" on the first line of a text file, user's
will no longer be able to abort the file using the space bar.
*** Again some work has been done on removing system generated
[PAUSE]'s from ANSI screens. Hopefully they will no longer be a
problem.
*** When uploading files locally, the system will now prompt the SysOp
on whether to execute the POSTUL.BAT file or not for each file.
*** The maximum number of message and file sections is now
limited to 1024 areas (0-1023). Hopefully this will give
enough breathing room for everyone.
*** The long standing problem with users not being able to download
from "No Ratio" sections when their ratio is out of balance should
not be fixed.
*** Problems with batch uploads when using the security modifications
for version 2.5g should now be fixed. No more duplicate file
uploads.
*** Many improvements have been made in the general operation of the
waiting for callers screen. Modem activity is now displayed when
necessary. Minor changes have been made in executing commands and
in moving to and from the front end mailer (e.g. T.A.G. will no
longer initialize the modem when returning to the wait screen from
the front end mailer).
*** The unlisted download command now completely supports wildcards
(yes, about time, I know). The raw directory command has been
cleaned up a little also.
T.A.G. BBS Version 2.6 - Update Documentation - Page 27
*** In general file names should now accept most legal DOS characters.
*** "Dummy" menus are no longer printed when <ENTER> or the
<SPACE BAR> is hit.
*** It is now possible to change the top window size while a user is
paging the SysOp. It checks for characters between each call so
it may take a second or two to see your request.
*** A note is now placed in the log when a user is validated.
*** The shell to DOS command from a menu now asks if the swap shell
should be used as the SysOp function key command does.
*** Forward messages to another user now includes information about
who the message was originally to and who forwarded the message.
The user can now also enter a short comment about why the message
was forwarded.
*** When entering the Mini-DOS command, the system will now request
SysOp password #1.
*** A file called TAGQUOTE.* may now be created to produce an "Your
quote for the day is:" during the logon process just before the
bulletin section appears (if active).
T.A.G. BBS Version 2.6 - Update Documentation - Page 28
/=============================================\
< T.A.G. Version 2.6 Menu Update Documentation >
\=============================================/
**********************
*** General Changes **
**********************
Maximum Menus/Commands
The maximum number of menus has been expanded to 100. In addition the
maximum number of commands per menu has also been expanded to 100.
Section Masks
All references to "Section Masks" in the original documentation should
be ignored. They are no longer supported in that form. See the
section in this document concerning "Message/File Groups" for
information on the replacement system.
Old ";<PKey><PData>" Command Linking
All references to the older style of command linking where you would
add ";<PKey><PData>" to the PData to link a command should be ignored.
This method of command linking is no longer supported. See the
section "Command Flags - No Linking/Linked To Next" in this section
for more information on the replacement system.
Menu Name / Prompt Fields
The menu name and prompt fields may now contain SDR codes.
Menu Starting Help Level Field
The starting help level can contain either a zero or a value from one
to four. Zero means the user starts at the help level s/he has
defined as their default help level, while a number from one to four
indicates that the user is forced to a specific help level no matter
what their default setting is. Normally most menus will be set to
zero, however the read message menu, for example, is often set to "2"
or "1" to eliminate the large menus for new users between messages.
Menu Location Field
The menu location now has an additional value to indicate a "Read
Message System" menu. Read message system menus cannot GOTO or GOSUB
menus with any other location. The quit command (PKey="Q") must be
used to exit these menus.
T.A.G. BBS Version 2.6 - Update Documentation - Page 29
Command Key Field
A default command feature is now available which will be executed if
the user should simply press carriage return at a menu. Simply define
a command with the command key of "<CR>" (without quotes of course)
and that command will be executed when the users pressed carriage
return. The best example of a use of this feature would be the
reading messages menu, where it is often desirable to have a carriage
return take you to the next message.
Commands with a blank "Key" will no longer display on T.A.G. generated
menus. Blanking the "Key" on link command will save the trouble of
having to "Hide" each of the commands in a link chain.
Command Flags - No Linking/Linked To Next
The command linking system in T.A.G. has been completely rewritten.
There are now no limitations on the order or type of commands that may
be linked together. Each command now contains a flag which indicates
whether it is linked to the next command or not. If the flag is
active, the system will immediately execute the next command on the
menu without prompting the user. Up to 20 commands may be in the link
buffer at any one time. This means that a single command could have
20 linked commands attached to it.
Normally when creating a linked set of commands, only the first
command is executable by the user. T.A.G. will allow linking into
other real commands (which the user can press a "key" for), but unless
you have a specific reason for doing so, all other commands in a chain
should have a blank "key" field.
If a linked command should change system locations (e.g. go into the
file section), all commands in the chain from that point forward will
be executed using the PKey/PData definitions in that location. An
example of this would be creating a command on the main menu which
first does a "goto" to the file system, and then executes the download
command.
If the system encounters a command in the link chain which is not
accessible to the user, the link buffer is immediately cleared and the
user will be dropped at whatever menu is currently active.
T.A.G. BBS Version 2.6 - Update Documentation - Page 30
When creating a set of linked commands, the last command in the chain
should NOT have the link flag set. For example, to create a 3 command
link chain, they would be set up as follows:
Command 1: Key = Command user must type to execute
| PKey/PData = Program information of first command
| Flag = Linked to Next
|
Command 2: Key = Blank
| PKey/PData = Program information of second command
| Flag = Linked to Next
|
Command 3: Key = Blank
| PKey/PData = Program information of third command
LINK STOPS Flag = No Linking
The existence of the global command "Execute Command Key" (PKey="0";
PData=<KEY>) should be noted as it provides an easy way to limit the
duplication of access levels in multiple linked commands. See that
command for more information.
For those who prefer, here is a more procedural explanation of how
T.A.G. handles link commands:
When the user executes a command which has other commands linked
to it, T.A.G. first copies all of the linked commands into a link
buffer and then executes the first command in the chain.
Upon returning to any standard menu, the system will first check
to see if there are any commands in the link buffer. If so, the
first one will be pulled out of the buffer and executed. This
process is repeated until no commands exist in the link buffer.
In the case of the "Execute Command Key" command, if the command
executed contains linked commands itself, they are added to the
link buffer before any remaining commands from the original link.
Thus the commands in the executed command will be processed
before continuing with the link of the original command.
T.A.G. BBS Version 2.6 - Update Documentation - Page 31
==============================================
Standard Program Keys Available From All Menus
==============================================
Function : Describe current message or file section
PKey : "H"
PData : [N]
<BLANK> A simple error message is printed when a section
description file is missing.
"N" All error messages are suppressed when the section
description file is missing.
This command displays a text file containing a description of the
current message or file section. Whether or not an error message is
displayed when T.A.G. encounters a missing section description file is
determined by the PData. Linking this command to each change section
command would provide forced descriptions of each section as the user
changes into it.
** Message Sections **
The files which contain the description have the name "BOARD.*" for
Fido style messages or "BOARD###.*" for Hudson (RA/QBBS) style
messages (### is the unique board number assigned to each section).
In either case, these files are located in the directory where the
messages are actually stored (set in the configuration for each
message section).
** File Sections **
The files which contain the description have the same name as the
section file name with the extension of ".MSG" or ".CLR". These
files are located in the Alternate Text File Directory. For example:
Section #1 has the file name of "MISC". MISC.MSG should appear in the
Alternate Text File Directory with a description of the Miscellaneous
Files section.
T.A.G. BBS Version 2.6 - Update Documentation - Page 32
Function : Display a text file
PKey : "!"
PData : [@]<Filename>[.<Ext>]
[@] Indicates the file resides in the Alternate Text
File Directory instead of the Main Data File
Directory.
<Filename> MS-DOS filename of the file to be printed.
.<Ext> Optional MS-DOS extension, if not ".MSG" and/or
".CLR".
This command displays a text file located in the Main Data File
Directory unless otherwise specified by the PData. If an extension is
not included with the filename, T.A.G. will assume the standard
"*.MSG" and/or "*.CLR" system. That is, if a "*.CLR" version exists
and the user's ANSI graphics are active, then it is displayed,
otherwise the "*.MSG" is displayed.
If the multi-user option is active, the system will scan the multi-
user directory for the file if it cannot be found in the local
directories.
Function : Change message section, message number, or file section
Pkey : "#"
PData : None
This command allows user to change messages or sections in the current
system by entering a number. The command has the following action
depending on the menu location:
Location Action
------------------- ----------------------
Main System Change Message Section
Read Message System Change Message Number
File System Change File Section
NOTE: This command MUST be the first command on the menu, but may
be hidden if desirable.
Function : Search backward for next accessible message section,
message number, or file section
PKey : "["
PData : None
This command will search backward (lower numbered sections/messages)
from the current section/message for the next accessible
section/message. If none is found, the user will remain in the current
section/message.
T.A.G. BBS Version 2.6 - Update Documentation - Page 33
Function : Search forward for next accessible message section,
message number, or file section
PKey : "]"
PData : None
This command will search forward (higher numbered sections\messages)
from the current section/message for the next accessible
section/message. If none is found, the user will remain in the current
section/message.
Function : Change to a specific message/file section
PKey : "|"
Data : F or <Section #>
<Section #> The number of section which to change to.
This command changes to the message or file section specified in the
program data. The command has the following action depending on the
menu location:
Location Action
------------------- ----------------------
Main System Change Message Section
Read Message System Invalid
File System Change File Section
The section number specified MUST be the real section number, not the
dynamic one. Normal access checks are done by the system so that if
the user does not have access to the section, the change request will
fail.
T.A.G. BBS Version 2.6 - Update Documentation - Page 34
Function : Execute Command Key
PKey : "0"
PData : <Key>
This command searches the current menu for a command who's "Key"
matches the specified PData and executes it. One might think this is
pretty useless, but it comes in very handy for standardizing access on
linked commands. For example, if you were creating a command to
change to a specific message section and do a new scan on only that
section. You could just use the PKey to the change the message
section, and then the PKey to new scan only that section. Using this
command however, you could change to the message menu and actually
execute the "(V)iew" command on the menu (assuming standard T.A.G.
menus here). If you ever changed the access on the "(V)iew" command,
you would not have to change the linked command's access also since it
actually uses the real "(V)iew" command to do its work.
Calling linked commands from within a linked command is fully
supported.
Function : Generate random message
PKey : "8"
PData : <Filename>
<Filename> MS-DOS filename of the message file
This command chooses a random message from the specified file and
displays it to the user. The file is in standard ASCII format with
one blank line separating each message. If the first line of the file
begins with "~" it is used as the header instead of the standard quote
of the day header. Due to the algorithm used, longer quotes have a
better chance of being chosen than shorter ones.
T.A.G. BBS Version 2.6 - Update Documentation - Page 35
Function : Change message or file section group mask
PKey : "9"
PData : [M or F][$ or <Group Mask>]
"M" Change message section group mask
"F" Change file section group mask
"$" Ask user to enter desired group mask
<Group Mask> New value of the message/file group mask (may be
blank)
This command changes the current message or file section group mask.
All sections which do not fit the specified mask will no longer be
accessible. Users remain in the current message/file section even if
it becomes invalid after the change. See the "Change to a specific
message section, message number, or file section" (PKey="|") for
information on how to send the user to another section. If dynamic
numbering is active, the sections will be renumbered accordingly.
In the case where the user must specify the group mask, a group mask
file is displayed prior to requesting input.
For message sections this file can be:
MGRP.* Default file for message sections
MGRP-<SL>.* Override file for specific SL settings
For file sections this file can be:
FGRP.* Default file for file sections
FGRP-<DSL>.* Override file for specific DSL settings
T.A.G. BBS Version 2.6 - Update Documentation - Page 36
========================
Main System Program Keys
========================
Function : User information functions
PKey : "D"
PData : <1..13, 15..23>
CHNG "0" List user information that can be changed.
NEW "1" Change the user's real name.
"2" Change the user's address.
"3" Change the user's city & state.
"4" Change the user's zip code.
"5" Change the user's phone number.
"6" Change the user's computer type.
"7" Change the user's ANSI colors.
"8" Change the user's birthday.
"9" Change the user's highest baud.
"10" Change the user's screen size (columns and lines).
"11" Toggle the user's ANSI status.
"12" Toggle the user's color status.
"13" Change the user's logon password.
"14" Change the user's external editor status.
"15" Toggle the user's [PAUSE] status.
"16" Toggle the user's onekey status.
"17" Toggle the user's VT-100 type tab status.
"18" Toggle the user's CLS status.
"19" Change the user's mailbox configuration.
"20" Change which bases the user new scans.
"21" Change menu to logon at (NOT supported).
"22" Change the user's help level.
"23" Toggle the user's custom menu status.
NEW "24" Toggle the user's clear screen before message status.
NEW "25" Toggle the user's do not disturb status.
NEW "26" Change the user's phone number 2.
NEW "27" Change the user's extra string 1.
NEW "28" Change the user's extra string 2.
NEW "29" Change the user's extra string 3.
NEW "30" Change the user's extra date 1.
NEW "31" Change the user's extra date 2.
NEW "32" Change the user's extra number 1.
NEW "33" Change the user's extra number 2.
NEW "34" Change the user's extra number 3.
NEW "35" Change the user's extra number 4.
NEW "36" Change the user's extra character 1.
NEW "37" Change the user's extra character 2.
NEW "38" Change the user's extra character 3.
NEW "39" Change the user's extra character 4.
NEW "40" Change the user's extra phone number.
This command combines many commands which allow listing and changing
T.A.G. BBS Version 2.6 - Update Documentation - Page 37
most of the current user's variable information. In the default menu
system, many of these commands to change common user information are
found on the Personal Data Menu.
Function : Scan for messages sent by the current user
PKey : "K"
PData : [C]
<Blank> Scan private messages (in section 0)
"C" Scan messages in the current section
This command scans for messages which the current user has sent. If
"C" is specified in the PData, the current section is scanned,
otherwise the private mail board is scanned. If the delete command is
accessible, the user may delete any or all of his message. Normally
this command is setup to allow a user to (K)ill any private mail they
have previously sent.
Function : Scan for messages to the current user
PKey : "M"
PData : [C]
<Blank> Scan private messages (in section 0)
"C" Scan messages in the current section
This command scans for messages which are to the current user. If "C"
is specified in the PData, the current section is scanned, otherwise
the private mail board is scanned. Normally this command is setup to
allow a user to read any private mail they have waiting.
Function : Word validation and deletion
PKey : "R" @
PData : [D]
<Blank> Validate new words added to dictionary
"D" Delete word from dictionary
This command, based on the PData, allows validation of new words added
to the dictionary during a spell check or deletion of a specified word
from the dictionary.
T.A.G. BBS Version 2.6 - Update Documentation - Page 38
Function : Information on current message section
PKey : "7"
PData : None
This command displays various information about the current message
section. The command is access sensitive and will reduce the
information displayed depending on the access of the user executing
it.
T.A.G. BBS Version 2.6 - Update Documentation - Page 39
==============================
Read Message Menu Program Keys
==============================
Function : Default next message in current direction
PKey : "D"
PData : None
This command goes to the next message in the current reading
direction. For example, if they are reading forward in the messages,
it would produce the next higher numbered message available to them.
Function : Read current message again
PKey : "A"
PData : None
This command reads the current message (if any) again. If does not
change the users current message number.
Function : Continuous read of messages
PKey : "C"
PData : None
This command switches the message system into continuous read mode.
While in this mode, messages are read one at a time in the current
direction until either no ore messages exist or the user aborts a
message with the space bar. Pressing control-N will not abort the
continuous read process, but will skip the remaining text in the
current message.
Function : Delete current message
PKey : "D"
PData : [Z]
<Blank> Delete current message and send receipt
[Z] Do not send delete receipt (zap)
This command deletes the current message assuming the user has access
to do so. Normal users may only delete mail to or from them (this
includes both their handle and real name). If a "Z" is not present in
the program data, a delete receipt is sent to the author of the
message indicating you have read the message.
T.A.G. BBS Version 2.6 - Update Documentation - Page 40
Function : Ignore messages and go to next section
PKey : "I"
PData : None
This command ignores the remaining messages in the current section
(sets the user's new scan point to the last message) and goes to the
next section in the new scan. If the user is not doing a new scan,
then they are simply sent back to the menu from which they starting
reading messages.
Function : Kludge/technical information on current message
PKey : "K"
PData : None
This command displays the message flags, kludge lines, and other
technical information abort the current message.
Function : Next message section
PKey : "N"
PData : None
This command skips the remaining messages in the current section and
goes to the next section in the new scan. The user's new scan pointer
is left at the message they were currently reading.
Function : Post message in current section
PKey : "P"
PData : [A][R]
<Blank> Normal post (no file attaches/requests)
"A" Allow file attaches in net mail sections @
"R" Allow file requests in net mail sections @
This command posts a public message in the current section if the user
has the access required. It will also optionally allow file attaches
and requests in net mail sections assuming the user has met the
security requirements defined in the system configuration.
Function : Quit read message menu
PKey : "Q"
PData : None
This command exists from a menu located in the "Read Message System".
This is the only correct method of exiting from a menu of this type
aside from logging off the system. Read message menus cannot GOTO or
GOSUB menus in other locations.
T.A.G. BBS Version 2.6 - Update Documentation - Page 41
Function : Reply to current message
PKey : "R"
PData : [A][R][E or P]
<Blank> Normal reply (ask user if public/private - no file
attaches/requests)
"A" Allow file attaches in net mail sections @
"R" Allow file requests in net mail sections @
"E" Force the reply to be private
"P" Force the reply to be public
This command allows the user to sent a reply to the author of the
current message (if any). It will also optionally allow file attaches
and requests in net mail sections assuming the user has met the
security requirements defined in the system configuration. The
options to force the reply to be public or private can be used in the
case where separate commands for public and private replies are
desired.
Function : Subjects of next 15 messages
PKey : "S"
PData : None
This command displays a summary of subjects/from/to of the next 15
messages in the current section. The user's read point is set to the
last message listed.
Function : Toggle scan setting of current section
PKey : "T"
PData : None
This command toggles the scan flag for the current message section.
When scanning is disabled, the section will not be scanned on a "(N)ew
scan" type command.
Function : User information of current message author
PKey : "U" @
PData : None
This command shows the extended user listing of the author of the
current message if s/he can be found in the user log. This command
should only be available to SysOp's as it shows private information
which should not be available to the general public.
T.A.G. BBS Version 2.6 - Update Documentation - Page 42
Function : Validate author of current message
PKey : "V" @
PData : None
This command validates the author of the current message if s/he can
be found in the user log. This command should only be available to
SysOp's as it changes the access level of the users in question.
Function : Write current message to file
PKey : "W" @
PData : None
This command writes the current message to a text file. It allows the
user to optionally remove the message header to ANSI type messages
where a header would get in the way. This command should be
restricted to SysOp's as it allows users to place files on the hard
drive at will. Certain extensions are not permitted, including COM,
EXE, BAT, etc.
Function : Next message in thread
PKey : "+"
PData : None
This command reads the next message in the current reply thread.
Function : Previous message in thread
PKey : "-"
PData : None
This command reads the previous message in the current reply thread.
Function : Information on current message section
PKey : "7"
PData : None
This command displays various information about the current message
section. The command is access sensitive and will reduce the
information displayed depending on the access of the user executing
it.
T.A.G. BBS Version 2.6 - Update Documentation - Page 43
=============================
File System Menu Program Keys
=============================
Function : Execute a file door call
PKey : "H"
PData : [$[?][!]]<Filename>
"$" Ask user to enter a filename to be passed to the
door.
"?" Allow wild card characters in the filename entered
by the user (Must specify "$" also).
"!" One or more file must exist in the current file
section which match the filename/filemask entered.
<Filename> Name of the program to execute
This command is designed to allow much easier implementation of file
related door operations. Before execution both a standard
DORINFO1.DEF and DOOR.SYS file are created.
The filename specified in the PData is executed with the following
parameters:
%1 Real baud rate of the user (port speed)
%2 Communications port
%3 ID number of current user (user number)
%4 Download pathname of the current file section
%5 Download filename of the *.DIR file of the current section
%6 Upload pathname of the current file section
%7 Upload filename of the *.DIR file of the current section
%8 User specified filename without the extension (if entered)
%9 Extension of the user specified filename (if entered)
Note: The upload filename will be the same and the download
filename if the upload and download pathnames are the same.
Otherwise the upload filename uses the default "FILES.DIR".