/======================================\
< T.A.G. Version 2.6d Main 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. Bulletin Board System \
< Copyright (C) 1986-1993 >
\ The T.A.G. Team /
\============================/
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Purpose and Requirements . . . . . . . . . . . . . . . . . . . . . . 1
Updated Releases . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Commercial Releases . . . . . . . . . . . . . . . . . . . . . . . . 2
The Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Copyright and License . . . . . . . . . . . . . . . . . . . . . . . 3
Installation of a New T.A.G. System . . . . . . . . . . . . . . . . 3
T.A.G. Alpha Sites . . . . . . . . . . . . . . . . . . . . . . . . . 3
Additional Information or Help . . . . . . . . . . . . . . . . . . . 3
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SysOp Keyboard Functions . . . . . . . . . . . . . . . . . . . . . . . 5
F1 Modify SL . . . . . . . . . . . . . . . . . . . . . . . . 5
Shift-F1 Modify DSL . . . . . . . . . . . . . . . . . . . . . . . 5
Alt-F1 Validate User. . . . . . . . . . . . . . . . . . . . . . 5
F2 Modify SF Flags. . . . . . . . . . . . . . . . . . . . . 5
Shift-F2 Modify AR Flags. . . . . . . . . . . . . . . . . . . . . 5
Alt-F2 Modify File Points. . . . . . . . . . . . . . . . . . . . 5
F3 Disable com port. . . . . . . . . . . . . . . . . . . . . 5
Shift-F3 Shell to DOS w/o user. . . . . . . . . . . . . . . . . . 5
Alt-F3 ALERT off. . . . . . . . . . . . . . . . . . . . . . . . 5
Ctrl-F3 Shell to DOS with user. . . . . . . . . . . . . . . . . . 5
F4 Toggle SysOp window. . . . . . . . . . . . . . . . . . . 5
Shift-F4 Turn Off Sysop Window. . . . . . . . . . . . . . . . . . 6
F5 Hang Up. . . . . . . . . . . . . . . . . . . . . . . . . 6
Shift-F5 Hangup with Message. . . . . . . . . . . . . . . . . . . 6
F6 Update time and status. . . . . . . . . . . . . . . . . . 6
Shift-F6 Redraw SysOp window. . . . . . . . . . . . . . . . . . . 6
F7 Subtract 5 minutes. . . . . . . . . . . . . . . . . . . . 6
Alt-F7 Execute BAT file. . . . . . . . . . . . . . . . . . . . . 6
F8 Add 5 minutes. . . . . . . . . . . . . . . . . . . . . . 6
F9 Temporary SysOp access toggle. . . . . . . . . . . . . . 6
Shift-F9 Display a text file. . . . . . . . . . . . . . . . . . . 6
Alt-F9 Activate keyboard security. . . . . . . . . . . . . . . . 6
F10 Chat. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Shift-F10 SysOp Next. . . . . . . . . . . . . . . . . . . . . . . . 6
Alt-F10 Chat reason. . . . . . . . . . . . . . . . . . . . . . . 7
Scrl-Lock SysOp available. . . . . . . . . . . . . . . . . . . . . 7
Alt-Break SysOp available. . . . . . . . . . . . . . . . . . . . . 7
Home Chat capture. . . . . . . . . . . . . . . . . . . . . . . 7
Shift Express Logon. . . . . . . . . . . . . . . . . . . . . . 7
Ctrl-Q Sysop Menu. . . . . . . . . . . . . . . . . . . . . . . . 7
Ctrl-U User Editor . . . . . . . . . . . . . . . . . . . . . . . 7
===========================================================================
January, 1993 (Preliminary) Page i
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
System Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
*.DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
bprot.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
events.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
fboards.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
fzscan.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
laston.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
macros.lst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
main.dic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
maindic.bad . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
mainidx.dic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
mainlog.dic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
mboards.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
menus.lst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
modem.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
msgtmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
mzscan.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
names.lst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
nlindex.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
shortmsg.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
sprot.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
status.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
tagstr.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
users.lst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
validate.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
voting.dat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Other System Files . . . . . . . . . . . . . . . . . . . . . . . . . . 11
auto.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
badlogon.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
batchlst.tmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
bbslist.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
callers.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
chat.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
computer.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
dosmenu.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
mainadd.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
newqa.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
nlindex.cfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
nlindex.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
notest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
sysop.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
sysop###.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
sysopmnu.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
system.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
tag.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
tag.ovr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
tag[Node].$$$ . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
tagerror.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
tagstr.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
text#.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
trashcan.fil . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
trashcan.fon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
===========================================================================
January, 1993 (Preliminary) Page ii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
trashcan.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
usage.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
usage.zzz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
user###.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
System Batch Files . . . . . . . . . . . . . . . . . . . . . . . . . . 15
extedit.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
extern#.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
filetest.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
logoff.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
logon.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
mailer.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
mchat.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
newlogon.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
postdl.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
postul.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
protocol.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
shellloc.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
shellrem.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
welcome.bat . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Parameters passed to batch files . . . . . . . . . . . . . . . . . . 17
Fido Message Base Files . . . . . . . . . . . . . . . . . . . . . . . . 18
########.msg . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
lastread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
echotoss.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
nettoss.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Hudson Message Base Files . . . . . . . . . . . . . . . . . . . . . . . 19
echomail.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
lastread.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
msghdr.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
msgidx.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
msginfo.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
msgtoidx.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
msgtxt.bbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System Display Files . . . . . . . . . . . . . . . . . . . . . . . . . 20
<BoardName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
<HelpID># . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
arflags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
arlevel@ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
birthday . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
bdlprot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
bulprot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
bullet@@ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
bulletin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
bupload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
chatoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
chaton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
dsl### . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
===========================================================================
January, 1993 (Preliminary) Page iii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
getlost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
goaway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
guest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
hangup# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
logon# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
mgrp[-sl] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
newuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
newqq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
noaccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
noboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
nochat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
nonewusr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
novice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
nusermsg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
pastbday . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
postcall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
postdl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
postul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
prequest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
quotehlp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
sl### . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
sdlprot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
sulprot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
sysfull . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
tagquote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
welcome# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
T.A.G. Command Line Parameters . . . . . . . . . . . . . . . . . . . . 25
AFTERUSERERRLVL . . . . . . . . . . . . . . . . . . . . . . . . . . 25
BASEPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONNECTRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
CONTROLCODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
ERRORCORRECTING . . . . . . . . . . . . . . . . . . . . . . . . . . 25
EXITERRLVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
FATALERRLVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
HALFDUPLEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
LOCAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
LOGON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
REALRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
STATUSPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Sysop Functions Menu . . . . . . . . . . . . . . . . . . . . . . . . . 27
===========================================================================
January, 1993 (Preliminary) Page iv
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Access Validation Editor . . . . . . . . . . . . . . . . . . . . . . . 28
Access Validation Fields . . . . . . . . . . . . . . . . . . . . . . 28
Record Number . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Validation Key . . . . . . . . . . . . . . . . . . . . . . . . . 28
SL/DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
AR/SF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
File Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Time Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Auto Validation Command . . . . . . . . . . . . . . . . . . . . . . 29
Adding the Validation Manager to T.A.G. . . . . . . . . . . . . . . 29
Deleting Validation Records . . . . . . . . . . . . . . . . . . . . 29
Inserting Validation Records . . . . . . . . . . . . . . . . . . . . 29
Modifying Validation Records . . . . . . . . . . . . . . . . . . . . 30
Validation Edit Commands . . . . . . . . . . . . . . . . . . . . . . 30
Positioning Validation Records . . . . . . . . . . . . . . . . . . . 31
Shell System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 33
System Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
SysOp password #1 . . . . . . . . . . . . . . . . . . . . . . . . . 33
SysOp password #2 . . . . . . . . . . . . . . . . . . . . . . . . . 33
SysOp password #3 . . . . . . . . . . . . . . . . . . . . . . . . . 34
New User password . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chat password . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
System information and directories . . . . . . . . . . . . . . . . . . 34
System name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SysOp name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Board phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Board Address . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
System is (Open/Closed) . . . . . . . . . . . . . . . . . . . . . . 35
Main data file directory . . . . . . . . . . . . . . . . . . . . . . 35
Alternate text file directory . . . . . . . . . . . . . . . . . . . 35
Swap file directory . . . . . . . . . . . . . . . . . . . . . . . . 35
Nodelist directory . . . . . . . . . . . . . . . . . . . . . . . . . 35
Dictionary directory . . . . . . . . . . . . . . . . . . . . . . . . 35
Temp Download Directory . . . . . . . . . . . . . . . . . . . . . . 35
Communications Configuration . . . . . . . . . . . . . . . . . . . . . 36
No call reinit time . . . . . . . . . . . . . . . . . . . . . . . . 36
Com-port Number . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Carrier Detect Mask . . . . . . . . . . . . . . . . . . . . . . . . 36
Use FOSSIL driver . . . . . . . . . . . . . . . . . . . . . . . . . 36
===========================================================================
January, 1993 (Preliminary) Page v
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Modem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Modem Control Strings . . . . . . . . . . . . . . . . . . . . . . . 37
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Character pacing delay . . . . . . . . . . . . . . . . . . . . . 37
Modem initialization speed . . . . . . . . . . . . . . . . . . . 37
CTS/RTS hardware flow control . . . . . . . . . . . . . . . . . . 38
File transfer efficiency . . . . . . . . . . . . . . . . . . . . 38
Result code configuration . . . . . . . . . . . . . . . . . . . . . 38
Pre-Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Answer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hangup 1st . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Hangup 2nd . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
After Hangup . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Exit System . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Modem Result Code Configuration . . . . . . . . . . . . . . . . . . . . 39
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
RING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
NO CARRIER . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
WAIT SCREEN . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
LOCAL LOGON . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
SHELL BATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
EXIT ERROR LEVEL . . . . . . . . . . . . . . . . . . . . . . . . 40
EXIT SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Result string . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Control code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Connect rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Real rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
How an Incoming Call is Processed . . . . . . . . . . . . . . . . . . . 41
Single value security settings . . . . . . . . . . . . . . . . . . . . 42
Full SysOp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
CoSysOp of system . . . . . . . . . . . . . . . . . . . . . . . . . 42
SL-Add words to dictionary . . . . . . . . . . . . . . . . . . . . . 42
Download system CoSysOp . . . . . . . . . . . . . . . . . . . . . . 42
No download ratio check . . . . . . . . . . . . . . . . . . . . . . 42
Add a system to BBS list . . . . . . . . . . . . . . . . . . . . . . 42
Send normal private mail . . . . . . . . . . . . . . . . . . . . . . 43
See unvalidated files . . . . . . . . . . . . . . . . . . . . . . . 43
See who posted anonymous . . . . . . . . . . . . . . . . . . . . . . 43
Reply to anonymous mail . . . . . . . . . . . . . . . . . . . . . . 43
Post any pub anonymously . . . . . . . . . . . . . . . . . . . . . . 43
Send anonymous private . . . . . . . . . . . . . . . . . . . . . . . 43
See passwords remotely . . . . . . . . . . . . . . . . . . . . . . . 43
===========================================================================
January, 1993 (Preliminary) Page vi
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
No post/call ratio check . . . . . . . . . . . . . . . . . . . . . . 43
Privilege (SL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Privilege (DSL) . . . . . . . . . . . . . . . . . . . . . . . . . . 43
No download point check . . . . . . . . . . . . . . . . . . . . . . 43
SysOp password #1 logon . . . . . . . . . . . . . . . . . . . . . . 43
Read text file into msg . . . . . . . . . . . . . . . . . . . . . . 44
SL-Modify netmail msg flags . . . . . . . . . . . . . . . . . . . . 44
SL-Netmail file attach . . . . . . . . . . . . . . . . . . . . . . . 44
SL-Netmail file request . . . . . . . . . . . . . . . . . . . . . . 44
Post/call key flag . . . . . . . . . . . . . . . . . . . . . . . . . 44
SL/AR - Sysop menu . . . . . . . . . . . . . . . . . . . . . . . . . 44
SL/AR - User Edit/Password . . . . . . . . . . . . . . . . . . . . . 44
KEY - Expired validation key . . . . . . . . . . . . . . . . . . . . 44
General variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Maximum private sent per call . . . . . . . . . . . . . . . . . . . 45
Maximum feedback sent per call . . . . . . . . . . . . . . . . . . . 45
Max public posts per call . . . . . . . . . . . . . . . . . . . . . 45
Number back SysOp log days . . . . . . . . . . . . . . . . . . . . . 45
Number days keep Usage Log . . . . . . . . . . . . . . . . . . . . . 45
Max number of logon tries . . . . . . . . . . . . . . . . . . . . . 45
Percent upload time refund . . . . . . . . . . . . . . . . . . . . . 46
Default read message menu . . . . . . . . . . . . . . . . . . . . . 46
Maximum pages per call . . . . . . . . . . . . . . . . . . . . . . . 46
Starting logon menu number . . . . . . . . . . . . . . . . . . . . . 46
Minimum K-Bytes to post . . . . . . . . . . . . . . . . . . . . . . 46
Minimum K-Bytes to upload . . . . . . . . . . . . . . . . . . . . . 46
Maximum number of users . . . . . . . . . . . . . . . . . . . . . . 46
Maximum files batch download . . . . . . . . . . . . . . . . . . . . 46
Maximum files batch upload . . . . . . . . . . . . . . . . . . . . . 46
Number of novice msg days . . . . . . . . . . . . . . . . . . . . . 46
Maximum daily time bank deposit . . . . . . . . . . . . . . . . . . 46
Maximum daily time bank withdraw . . . . . . . . . . . . . . . . . . 47
Maximum time in time bank . . . . . . . . . . . . . . . . . . . . . 47
Auto message maximum lines . . . . . . . . . . . . . . . . . . . . . 47
Default message group mask . . . . . . . . . . . . . . . . . . . . . 47
Default file group mask . . . . . . . . . . . . . . . . . . . . . . 47
Menu fast command keys . . . . . . . . . . . . . . . . . . . . . . . 47
Chat colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
===========================================================================
January, 1993 (Preliminary) Page vii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Optional flagged functions . . . . . . . . . . . . . . . . . . . . . . 48
Title screen pause . . . . . . . . . . . . . . . . . . . . . . . . . 48
Blank off-line wait screen . . . . . . . . . . . . . . . . . . . . . 48
Logon to bulletin section . . . . . . . . . . . . . . . . . . . . . 48
Handles allowed on system . . . . . . . . . . . . . . . . . . . . . 48
Keyboard security protection . . . . . . . . . . . . . . . . . . . . 48
Front End Mailer . . . . . . . . . . . . . . . . . . . . . . . . . . 49
New user message sent to . . . . . . . . . . . . . . . . . . . . . . 49
SysOp mail forwarded to user . . . . . . . . . . . . . . . . . . . . 49
Minutes before time out . . . . . . . . . . . . . . . . . . . . . . 49
Minutes before time out bell . . . . . . . . . . . . . . . . . . . . 49
Guest user number . . . . . . . . . . . . . . . . . . . . . . . . . 49
The system operator is . . . . . . . . . . . . . . . . . . . . . . . 50
Store bad logon information . . . . . . . . . . . . . . . . . . . . 50
Logon uses Auto-Message . . . . . . . . . . . . . . . . . . . . . . 50
Logon takes phone off-hook . . . . . . . . . . . . . . . . . . . . . 50
Generic logon information . . . . . . . . . . . . . . . . . . . . . 50
Logon asks for phone number . . . . . . . . . . . . . . . . . . . . 50
Alert beeps only chat on . . . . . . . . . . . . . . . . . . . . . . 51
Auto chat buffer open . . . . . . . . . . . . . . . . . . . . . . . 51
Scan/File find in SysOp log . . . . . . . . . . . . . . . . . . . . 51
Direct screen writes . . . . . . . . . . . . . . . . . . . . . . . . 51
Screen snow checking . . . . . . . . . . . . . . . . . . . . . . . . 51
Try to use EMS for overlays . . . . . . . . . . . . . . . . . . . . 51
Instant logon key . . . . . . . . . . . . . . . . . . . . . . . . . 51
Local Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Show available upload space . . . . . . . . . . . . . . . . . . . . 52
Show GIF resolution . . . . . . . . . . . . . . . . . . . . . . . . 52
Force scan before upload . . . . . . . . . . . . . . . . . . . . . . 52
Local logon SysOp window . . . . . . . . . . . . . . . . . . . . . . 52
Show files open (debug) . . . . . . . . . . . . . . . . . . . . . . 52
Log modem activity (debug) . . . . . . . . . . . . . . . . . . . . . 52
Wait screen action disable . . . . . . . . . . . . . . . . . . . . . 52
Dynamic message numbering . . . . . . . . . . . . . . . . . . . . . 52
Dynamic file numbering . . . . . . . . . . . . . . . . . . . . . . . 53
Forced voting at logon . . . . . . . . . . . . . . . . . . . . . . . 53
Warning days for user expire . . . . . . . . . . . . . . . . . . . . 53
Failed logon message sent to . . . . . . . . . . . . . . . . . . . . 53
Wait screen messages waiting . . . . . . . . . . . . . . . . . . . . 53
Auto ANSI detection at logon . . . . . . . . . . . . . . . . . . . . 53
Range setting commands . . . . . . . . . . . . . . . . . . . . . . . . 54
Time limitations . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Calls allowed per day . . . . . . . . . . . . . . . . . . . . . . . 54
Upload/download number of files ratio . . . . . . . . . . . . . . . 54
Upload/download K-bytes ratio . . . . . . . . . . . . . . . . . . . 54
Post/call ratio . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Using Range Setting Commands . . . . . . . . . . . . . . . . . . . . 55
Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Toggle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
The User Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
===========================================================================
January, 1993 (Preliminary) Page viii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Table of Special Flags (SF) for Users . . . . . . . . . . . . . . . . . 56
A : Auto private mail delete . . . . . . . . . . . . . . . . . . . 56
B : No post/call ratio . . . . . . . . . . . . . . . . . . . . . . 56
C : Cannot abort upload scan . . . . . . . . . . . . . . . . . . . 56
D : Cannot post anonymous . . . . . . . . . . . . . . . . . . . . 56
E : Cannot add to BBS list . . . . . . . . . . . . . . . . . . . . 56
F : Cannot page sysop . . . . . . . . . . . . . . . . . . . . . . 57
G : No download limit . . . . . . . . . . . . . . . . . . . . . . 57
H : Cannot post public mail . . . . . . . . . . . . . . . . . . . 57
I : Cannot send private mail . . . . . . . . . . . . . . . . . . . 57
J : Not allowed to vote . . . . . . . . . . . . . . . . . . . . . 57
K : Allowed only one call per day . . . . . . . . . . . . . . . . 57
L : Public mail is marked not validated . . . . . . . . . . . . . 57
M : Protect from deletion . . . . . . . . . . . . . . . . . . . . 57
N : Ignore file points . . . . . . . . . . . . . . . . . . . . . . 57
O : Uploaded files not validated immediately . . . . . . . . . . . 57
P : [PAUSE] active . . . . . . . . . . . . . . . . . . . . . . . . 57
Q : ANSI active . . . . . . . . . . . . . . . . . . . . . . . . . 57
R : Color active . . . . . . . . . . . . . . . . . . . . . . . . . 57
S : Onekey input . . . . . . . . . . . . . . . . . . . . . . . . . 58
T : Alert active . . . . . . . . . . . . . . . . . . . . . . . . . 58
U : User is male . . . . . . . . . . . . . . . . . . . . . . . . . 58
V : Mailbox is closed . . . . . . . . . . . . . . . . . . . . . . 58
W : Tabs active . . . . . . . . . . . . . . . . . . . . . . . . . 58
X : CLS character used . . . . . . . . . . . . . . . . . . . . . . 58
Table of Configuration Flags (CF) for users . . . . . . . . . . . . . . 58
A : Uses custom menus . . . . . . . . . . . . . . . . . . . . . . 58
Adjusting Numeric Values . . . . . . . . . . . . . . . . . . . . . . . 58
Built in Security Features . . . . . . . . . . . . . . . . . . . . . . 59
===========================================================================
January, 1993 (Preliminary) Page ix
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Extended User Listing Description . . . . . . . . . . . . . . . . . . . 59
User# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Rec# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
SL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
<<TAGGED>> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
AR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
SF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
SysOp note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Call spread . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Mail waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
MSG base SubOp . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
TimeBank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Starting menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Last <MSG/DL> base . . . . . . . . . . . . . . . . . . . . . . . . . 61
Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
First on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Expires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
CLS message read . . . . . . . . . . . . . . . . . . . . . . . . . . 61
DND (Do not disturb) . . . . . . . . . . . . . . . . . . . . . . . . 61
Normal User Listing Description . . . . . . . . . . . . . . . . . . 62
Abbreviations used in user listing . . . . . . . . . . . . . . . . . . 62
Short User Listing Description . . . . . . . . . . . . . . . . . . . 63
Informational User Listing Description . . . . . . . . . . . . . . . 63
User Editor Main Command Descriptions . . . . . . . . . . . . . . . . . 65
(Space) Toggle tag status of this user . . . . . . . . . . . . . . . 65
(=) Oops (load old data) . . . . . . . . . . . . . . . . . . . . . . 65
([) Back one user . . . . . . . . . . . . . . . . . . . . . . . . . 65
(]) Forward one user . . . . . . . . . . . . . . . . . . . . . . . . 65
(/) Change all tagged . . . . . . . . . . . . . . . . . . . . . . . 65
({) Search backward . . . . . . . . . . . . . . . . . . . . . . . . 66
(}) Search forward . . . . . . . . . . . . . . . . . . . . . . . . . 66
(.) List all tagged . . . . . . . . . . . . . . . . . . . . . . . . 66
(;) Relist user . . . . . . . . . . . . . . . . . . . . . . . . . . 66
(-) Clear for reentry: . . . . . . . . . . . . . . . . . . . . . . . 66
(\) New user config . . . . . . . . . . . . . . . . . . . . . . . . 66
(E) Special flags . . . . . . . . . . . . . . . . . . . . . . . . . 66
(F) AR flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(I) Last boards . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(L) Laston date . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(M) Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(N) New default list . . . . . . . . . . . . . . . . . . . . . . . . 67
(O) Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(Q) Quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(U) Jump to user . . . . . . . . . . . . . . . . . . . . . . . . . . 67
(V) Validate user . . . . . . . . . . . . . . . . . . . . . . . . . 67
(W) Undelete user . . . . . . . . . . . . . . . . . . . . . . . . . 67
(0) Mail posts/waiting . . . . . . . . . . . . . . . . . . . . . . . 68
===========================================================================
January, 1993 (Preliminary) Page x
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
(!) Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
(#) User number . . . . . . . . . . . . . . . . . . . . . . . . . . 68
($) Money (credit,debit) . . . . . . . . . . . . . . . . . . . . . . 68
(*) Delete user . . . . . . . . . . . . . . . . . . . . . . . . . . 68
(') Change colors . . . . . . . . . . . . . . . . . . . . . . . . . 68
(@) Time bank . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
(%) User history . . . . . . . . . . . . . . . . . . . . . . . . . . 68
(+) Configuration flags . . . . . . . . . . . . . . . . . . . . . . 69
(|) Gender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Options Menu - User Editor . . . . . . . . . . . . . . . . . . . . . . 69
General text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Security level . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
D/L security level . . . . . . . . . . . . . . . . . . . . . . . . . 70
AR flags set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Special flags set . . . . . . . . . . . . . . . . . . . . . . . . . 70
User status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Days since last on . . . . . . . . . . . . . . . . . . . . . . . . . 70
Number of calls . . . . . . . . . . . . . . . . . . . . . . . . . . 70
User age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
User gender . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
# 1/10's call/post . . . . . . . . . . . . . . . . . . . . . . . . . 70
#K-DL/1K-UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
# DL's/1 UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Options Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . 72
SPACE: Toggle user tag status by number . . . . . . . . . . . . . . 72
C:hange an option's state . . . . . . . . . . . . . . . . . . . . . 72
E:mpty tag table . . . . . . . . . . . . . . . . . . . . . . . . . . 72
I:nvert tag table . . . . . . . . . . . . . . . . . . . . . . . . . 72
S:how tagged users . . . . . . . . . . . . . . . . . . . . . . . . . 72
T:ag operations . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Tagged user set operations . . . . . . . . . . . . . . . . . . . . . . 73
Union . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Intersection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Difference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Divergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
User SDR Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
System SDR Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
TAB SDR Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
New user questions . . . . . . . . . . . . . . . . . . . . . . . . . . 77
===========================================================================
January, 1993 (Preliminary) Page xi
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
The Message Board Editor . . . . . . . . . . . . . . . . . . . . . . . 78
Email Message Area . . . . . . . . . . . . . . . . . . . . . . . . . 78
RA Echo Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Netmail Message Area . . . . . . . . . . . . . . . . . . . . . . . . 79
Message Board Editor Fields . . . . . . . . . . . . . . . . . . . . 80
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Read menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Post file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Start quote . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
End quote . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
EchoTag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Origin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
SubOps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Anonymous . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Allow ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Mail Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Spell Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Message/File Groups . . . . . . . . . . . . . . . . . . . . . . . . 83
The File Board Editor . . . . . . . . . . . . . . . . . . . . . . . . . 84
Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
[@]File name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
DL Path Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
UL Path Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Group number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
See names DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
No ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
CD ROM drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
CD ROM DRIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
===========================================================================
January, 1993 (Preliminary) Page xii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
The Event Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Internal Events . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Scheduled day(s) . . . . . . . . . . . . . . . . . . . . . . . . 88
Time active . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Permission/restriction . . . . . . . . . . . . . . . . . . . . . 88
Logon/chat . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Affected message . . . . . . . . . . . . . . . . . . . . . . . . 89
Unaffected message . . . . . . . . . . . . . . . . . . . . . . . 89
Internal Logon Restriction Events . . . . . . . . . . . . . . . . . 89
Internal Logon Permission Events . . . . . . . . . . . . . . . . . . 89
Internal Chat Restriction Events . . . . . . . . . . . . . . . . . . 90
Internal Chat Permission Events . . . . . . . . . . . . . . . . . . 91
Quirks Associated with Internal Events . . . . . . . . . . . . . . . 91
External Events . . . . . . . . . . . . . . . . . . . . . . . . . . 92
External ErrorLevel Event . . . . . . . . . . . . . . . . . . . . . 92
External DOS Shell Event . . . . . . . . . . . . . . . . . . . . . . 94
Single File Transfer Protocol Editor . . . . . . . . . . . . . . . . . 95
Protocol Variable Strings . . . . . . . . . . . . . . . . . . . . . 96
[Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Current Dir] . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Directory] . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Filename] . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Main Data Dir] . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[Real Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
[UL Directory] . . . . . . . . . . . . . . . . . . . . . . . . . 96
Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Baud rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Temp log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
(U)Load log / (D)Load log . . . . . . . . . . . . . . . . . . . . . 97
(U)L string / (D)L string . . . . . . . . . . . . . . . . . . . . . 97
Creating an external protocol . . . . . . . . . . . . . . . . . . 97
Creating an Internal protocol . . . . . . . . . . . . . . . . . . 97
Return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Transfer Failed . . . . . . . . . . . . . . . . . . . . . . . . . 98
(U)Load codes / (D)Load codes . . . . . . . . . . . . . . . . . . . 98
===========================================================================
January, 1993 (Preliminary) Page xiii
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Batch File Transfer Protocol Editor . . . . . . . . . . . . . . . . . . 99
Batch Protocol Variable Strings . . . . . . . . . . . . . . . . . . 99
[Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Current Dir] . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Directory] . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Filename] . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Main Data Dir] . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Port] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[Real Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
[UL Directory] . . . . . . . . . . . . . . . . . . . . . . . . . 99
Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Baud rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Temp log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
(U)Load log / (D)Load log . . . . . . . . . . . . . . . . . . . . . 101
(U)L string / (D)L string . . . . . . . . . . . . . . . . . . . . . 101
Creating an external protocol . . . . . . . . . . . . . . . . . . 101
Creating an Internal protocol . . . . . . . . . . . . . . . . . . 102
Return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Transfer Failed . . . . . . . . . . . . . . . . . . . . . . . . . 102
(U)Load codes / (D)Load codes . . . . . . . . . . . . . . . . . . . 103
(U)L FileList / (D)L FileList . . . . . . . . . . . . . . . . . . . 103
Max cmd chars . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Log position . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
MINI-DOS System Security . . . . . . . . . . . . . . . . . . . . . . . 104
OVERRIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Programmable Text Strings . . . . . . . . . . . . . . . . . . . . . . . 105
Programmable text string files . . . . . . . . . . . . . . . . . . . 105
"Default" string files . . . . . . . . . . . . . . . . . . . . . 105
"Editable" string files . . . . . . . . . . . . . . . . . . . . . 105
"Compiled" string file . . . . . . . . . . . . . . . . . . . . . 106
Changing programmable text strings . . . . . . . . . . . . . . . . . 106
Structure of programmable text string files . . . . . . . . . . . . 106
Notes on programmable text strings . . . . . . . . . . . . . . . . . 107
Display Control Codes . . . . . . . . . . . . . . . . . . . . . . . 107
MULTINODE Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Theory of multinode . . . . . . . . . . . . . . . . . . . . . . . . 108
General MultiNode Directory Structure . . . . . . . . . . . . . . . 109
Multinode Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 110
PKEYS/PDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
"DIR" Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Caveats (warnings) . . . . . . . . . . . . . . . . . . . . . . . . . 111
Door Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Setting up an external full screen editor (QuickED) . . . . . . . . . . 112
External program example using the Door Master program . . . . . . . . 114
External program using the QuickDoor program . . . . . . . . . . . . . 115
===========================================================================
January, 1993 (Preliminary) Page xiv
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
>>> Table of Contents <<<
Setting up a DOS Shell . . . . . . . . . . . . . . . . . . . . . . . . 116
IBMAUX20.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
WATCHDOG.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
MARKRELE.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Setting Up SHELLLOC.BAT . . . . . . . . . . . . . . . . . . . . . . 117
Setting Up SHELLREM.BAT . . . . . . . . . . . . . . . . . . . . . . 117
Files= Information Line on the SysOp Window . . . . . . . . . . . . . . 117
Automatic Archive Checking of Uploads . . . . . . . . . . . . . . . . . 118
Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Questionnaire File Format . . . . . . . . . . . . . . . . . . . . . 119
Calling Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 120
System Hints and Other SysOp & CoSysOp Functions . . . . . . . . . . . 121
Special codes for formatting text . . . . . . . . . . . . . . . . . 121
Delete several public messages in a message section . . . . . . . . 121
Add a file quickly to a section listing . . . . . . . . . . . . . . 121
Adding large numbers of files to the system . . . . . . . . . . . . 122
Automatically reboot on an error . . . . . . . . . . . . . . . . . . 122
Chat mode with a user . . . . . . . . . . . . . . . . . . . . . . . 122
Password checking . . . . . . . . . . . . . . . . . . . . . . . . . 122
Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
===========================================================================
January, 1993 (Preliminary) Page xv
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===============\
< Acknowledgements >
\===============/
T.A.G. has been a team effort since its inception. The current T.A.G. Team
members are:
Victor Capton (1:120/120)
Randy Goebel (1:120/36)
Paul Williams (1:2410/116)
T.A.G. has also been built on the efforts of two former T.A.G. Team
members, who have moved on to other pursuits. We thank, and recognize the
contributions of:
Paul Loeber
Robert Numerick
We also acknowledge and appreciate the hard work, and testing done by our
Beta team. Their diligent efforts, bug reports, and suggestions help ensure
a high quality, high reliability BBS system.
Finally, the sysops who run T.A.G. BBS. Their comments, suggestions, and
ideas form the basis for each new revision.
*************************************************************************
Special thanks to Wayne Bell for his original ideas
for a user-friendly BBS interface
*************************************************************************
Also, our appreciation to Martin Pollard for converting the T.A.G. Pascal
structures to C for this release.
/========================\
< Purpose and Requirements >
\========================/
T.A.G. is founded in the belief in the Shareware marketing concept that
encourages low cost, high quality software.
T.A.G. was written on the premise of being used in the private BBS
environment. This product was designed to be used with the following
minimum system configuration:
- IBM Personal Computer (or true compatible)
- Hard Disk drive (10 Megabytes recommended minimum)
- Asynchronous communications (serial port) adapter
- Intelligent Modem (100% Hayes compatible recommended)
- 512K (minimum) RAM
- 80 column monochrome or color monitor
- Voice-grade telephone connection for the modem
- PC-DOS or MS-DOS, version 3.1 or later
===========================================================================
January, 1993 (Preliminary) Page 1
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/================\
< Updated Releases >
\================/
Alpha and Beta sites will have the latest standard release, and will
distribute it at no cost (other than the telephone call to download the
program). Updates will be released on a regular basis, approximately twice
a year, but we are unable to give a firm schedule.
/===================\
< Commercial Releases >
\===================/
No commercial release is generally available. Special requests will be
considered on an individual basis.
/===============\
< The Source Code >
\===============/
The source code for T.A.G., written in Borland Pascal 7.0, is not available
to the public.
/========\
< Warranty >
\========/
The T.A.G. Team hereby disclaims all warranties relating to this software,
whether express or implied, including without limitation any implied
warranties of merchantability or fitness for a particular purpose. The
T.A.G. Team will not be liable for any special, incidental, consequential,
indirect or similar damages due to loss of data or any other reason, even
if The T.A.G. Team or an agent of The T.A.G. Team has been advised of the
possibility of such damages. In no event shall The T.A.G. Team's liability
for any damages ever exceed the price paid for the license to use the
software, regardless of the form of the claim. The person using the
software bears all risk as to the quality and performance of the software.
===========================================================================
January, 1993 (Preliminary) Page 2
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================\
< Copyright and License >
\=====================/
T.A.G. is not public domain software; it is copyrighted by The T.A.G. Team.
However, we grant you the right to make and distribute as many copies of
the Standard released version as you wish, using any acceptable medium of
exchange, with the following provisions:
1. Only distribute Standard release versions.
2. Only distribute the program in its original form, with all of its
related files, addendum files, and documentation.
3. Do not alter the program in any manner.
4. The Standard Released versions may not be used in any commercial manner
without the express consent of The T.A.G. Team.
/===================================\
< Installation of a New T.A.G. System >
\===================================/
A start up package is distributed under the name of TAGG*.ZIP, where "*"
indicates the version number in question. This compressed file contains
complete documentation concerning the setup of a new system. It also
contains a complete menu driven setup program.
/==================\
< T.A.G. Alpha Sites >
\==================/
System Name Number Baud/Modem Node # SysOp
-------------- ------------ ----------- -------- ------------
*A*R*T*H*U*R* 313-879-2318 14.4 HST/DS 120/120 Victor Capton
The Black Hole 313-879-7387 14.4 HST 120/36 Randy Goebel
John Galt 313-582-2528 14.4 HST/DS 2410/144 Paul Williams
CRIMP 313-582-6671 16.8 HST/DS 2410/116 Paul Williams
/==============================\
< Additional Information or Help >
\==============================/
For information contact one of the Alpha or Beta sites or send mail to:
The T.A.G. Team
P.O. Box 4214
Troy, MI 48099-4214
If you do put up a T.A.G. system, please let us know. We would like to keep
an updated list of boards compiled and frankly, we are also interested in
what people have done with our system. Suggestions?? By all means. We are
always interested in new ideas. And, as always, we thank you for your
support.
The T.A.G. Team
===========================================================================
January, 1993 (Preliminary) Page 3
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===================\
< System Requirements >
\===================/
ANSI.SYS
T.A.G. has a complete internal ANSI driver. ANSI.SYS or other similar
ANSI drivers are no longer required to run T.A.G. This eliminates the
possible use of ANSI redefinition codes from within T.A.G. itself (any
external programs you run are outside of T.A.G.'s control).
If you run external programs (doors) which require ANSI, it is
recommended that you use an ANSI driver which prevents redefinition of
keys, or an add-in TSR (PKSFANSI.COM) which intercepts keyboard
redefinition.
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.
BUFFERS
The value for BUFFERS in your CONFIG.SYS is dependant on your hard disk,
disk caching programs, and software configuration. For systems without
disk caching, a value of BUFFERS=20 is generally sufficient. With disk
caching programs, the value for BUFFERS should generally be lowered.
Consult the documentation for your specific disk caching program.
FILES
The recommended value for FILES in your CONFIG.SYS is a MINIMUM of 20.
MEMORY MANAGERS
T.A.G. has been tested with QEMM386, EMM386, and 386MAX. No problems
have been noted. T.A.G. supports, but does not require, XMS. T.A.G.
supports, but does not require, EMS that meets the L.I.M. 4.0
specification.
DISK CACHING PROGRAMS
T.A.G. has been tested using Norton Disk Cache, Hyperdisk, and LanCache.
No problems have been noted. Use of a disk cache is highly recommended,
and can significantly increase the performance of T.A.G.
MULTI-TASKERS
T.A.G. has been tested under DesqView, DoubleDOS, OS/2, and Windows.
T.A.G. is DesqView, DoubleDOS, and OS/2 aware, meaning only that it will
give up time slices to the multi-tasker when appropriate. T.A.G.
currently is not Windows aware.
NETWORKS
T.A.G. has been tested under Lantastic, Novell, and PC-Net. No known
incompatibilities have been found.
FOSSILS
T.A.G. has been tested using X00, BNU, and SIO (under OS/2). No known
incompatibilities have been found.
===========================================================================
January, 1993 (Preliminary) Page 4
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/========================\
< SysOp Keyboard Functions >
\========================/
When a user is logged onto the system, several SysOp functions exist which
can only be executed by the person at the keyboard. These functions are
active in most areas of the system, the primary exception being during
external doors, including downloads or uploads.
F1 Modify SL.
Change the user's Security Level (SL). Changes and makes permanent the
user's current security level (SL).
Shift-F1 Modify DSL.
Change the user's Download Security Level (DSL). Changes and makes
permanent the user's current download security level (DSL).
Alt-F1 Validate User.
Validates the current user on-line according to the validation levels
created in the validation editor. The communications port is disabled
during the validation process, so the user cannot see the validation
levels defined.
F2 Modify SF Flags.
Change the user's Special Flags (SF).
Shift-F2 Modify AR Flags.
Change the user's Access Restriction (AR) flags. (Toggle one or all
flags on/off).
Alt-F2 Modify File Points.
Change the user's file points.
F3 Disable com port.
Disables the communications port so the SysOp may do something without
being observed by the user.
Shift-F3 Shell to DOS w/o user.
Shell to DOS while the user waits on the board. (See the DOS shell
section of this document for setup procedures.)
Alt-F3 ALERT off.
Turn off the ALERT (Without letting the user know.)
Ctrl-F3 Shell to DOS with user.
Shell to DOS while a user is on-line and take them with you.
Warning: Only take users you trust completely to DOS with this command.
(See the DOS shell section of this document for setup procedures.)
F4 Toggle SysOp window.
Toggles the Sysop window between normal and expanded modes. If the
window is off, this command will display it at the normal mode.
===========================================================================
January, 1993 (Preliminary) Page 5
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Shift-F4 Turn Off Sysop Window.
Turn off the top SysOp window (use F4 to turn it back on again).
F5 Hang Up.
Hang up on the user immediately.
Shift-F5 Hangup with Message.
Print a text file and then hang up on the user. You will be asked to
type a number from 1 to 9 corresponding to the "HANGUP#.MSG" file to
display (e.g. Pressing "1" would display "HANGUP1.MSG").
F6 Update time and status.
Updates the time and the status line in the SysOp window (if active).
Shift-F6 Redraw SysOp window.
Redraws the Sysop window at the current mode.
F7 Subtract 5 minutes.
Subtract 5 minutes from the user's time on-line.
Alt-F7 Execute BAT file.
Executes a set of commands while a user is on-line. You will be asked
to type a number from 1 to 9 corresponding to the "EXTERN#.BAT" file to
shell to DOS and execute (e.g. Pressing "1" would execute
"EXTERN1.BAT").
F8 Add 5 minutes.
Add 5 minutes to the user's time on-line.
F9 Temporary SysOp access toggle.
Toggles Temporary Sysop access for the user on-line. Temporary SysOp
access includes 255 SL, 255 DSL, and all AR flags. Normal Access is
restored when the user logs off or when F9 is pressed again.
Shift-F9 Display a text file.
You will be asked to type a number from 1 to 9 corresponding to the
"TEXT#.MSG" file to display (e.g. pressing "1" would display
"TEXT1.MSG"). The file is displayed both locally and remotely.
Alt-F9 Activate keyboard security.
Activates (only) the keyboard security without having to enter system
configuration (good for unexpected visits). Once keyboard security is
activated, it can be disabled only in the System Configuration Menu.
F10 Chat.
Toggles into and out of Chat mode with the user on-line.
Shift-F10 SysOp Next.
Toggles the Sysop Next option, letting the SysOp know when the system is
free. When active, an alarm will sound for 45 seconds when the user
logs off.
===========================================================================
January, 1993 (Preliminary) Page 6
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Alt-F10 Chat reason.
If the CHAT flag appears in the status line of the SysOp window, the
reason for chat can be printed by pressing this key. The reason is only
seen on the local side of the system.
Scrl-Lock SysOp available.
Performs the same function as the Alt-Break key.
Alt-Break SysOp available.
Toggles the Sysop available flag to indicate whether or not to page the
SysOp when requested. It may not update the top window immediately but
your keyboard light should tell you it has changed.
Home Chat capture.
Toggles the Chat session capture on/off while chatting with a user.
Exiting chat mode automatically closes the capture file.
Shift Express Logon.
Holding either shift key down when logging onto the system will skip all
logon messages (logon*.*, sl*.*, dsl*.*, user*.*, arlevel*.*, logon.bat,
auto-message, etc). The check for this is made immediately after the
caller number is printed. If the shift key is depressed before a
password is requested at logon, the entire password security system is
bypassed as well.
Ctrl-Q Sysop Menu.
Calls SysOp menu (This menu can also be called from any menu while the
user is logged on, provided the security requirements in the system
configuration are met.)
Ctrl-U User Editor
Directly calls the user editor, attempting to pull up the current user
"of interest". In the case of reading messages, it attempts to locate
the user that posted the message. In browsing the file area, it
attempts to locate the user that uploaded the file. Access to this
function is controlled by a separate configuration setting in the system
config.
===========================================================================
January, 1993 (Preliminary) Page 7
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=================\
< System Data Files >
\=================/
System data files are files that are used to store (usually binary)
information on a particular area of the BBS. These files are of primary
interest to T.A.G. utility authors, but the SysOp should be aware of them,
their function, and their location.
[Structure]
(Startup/Dfiles/Afiles/Mfiles/FileBrd/MsgBrd)
Filename Description
---------- -----------------------------------------------------------
*.DIR [ULFREC] (FileBrd/Dfiles/Afiles/Mfiles)
These files contain the actual filenames, descriptions,
uploader name, etc. for each file on the BBS. Usually
located in the directory with the actual downloadable files,
it can (optionally) be located in the DFILES, AFILES or
MFILES directory.
bprot.dat [BPROTOCOLREC] (Dfiles/Mfiles)
This file contains all the configuration information
concerning batch file transfer protocols.
events.dat [EVENTRECORDTYPE] (Dfiles/Mfiles)
This file contains the information for T.A.G. events.
fboards.dat [ULREC] (Dfiles/Mfiles)
This file contains the configuration information for each of
the file sections on the system.
fzscan.dat [BITSETTYPE] (Dfiles/Mfiles)
This file contains flags to determine which file bases are
scanned.
laston.dat [LASTONTYPE] (Dfiles/Mfiles)
This file contains a list of the last few callers to log
onto the system. The information is displayed when a user
logs on.
macros.lst [MACROREC] (Dfiles/Mfiles)
The file contains the macros that users have defined for
themselves. Space is NOT wasted for users who have not
defined macros.
main.dic [N/A] (Dictionary Directory)
This file is the main dictionary used for message
spellchecking (/SPELL). Dictionary maintenance should be
performed periodically (See Sysop Commands, Dictionary
Maintenance).
maindic.bad [N/A] (Dictionary Directory)
The main dictionary(main.dic) is renamed to this if any
corruption should occur.
===========================================================================
January, 1993 (Preliminary) Page 8
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
mainidx.dic [N/A] (Dictionary Directory)
This file contains the index information for main.dic.
mainlog.dic [N/A] (Dictionary Directory)
A datafile containing words that have not been validated.
mboards.dat [MBOARDTYPE] (Dfiles/Afiles)
This file contains the configuration information for each of
the message sections on the system.
menus.lst [MENUREC] (Dfiles/Mfiles)
This file contains the configuration information of the
menus on the system.
modem.dat [MODEMREC] (Dfiles/Mfiles)
This file contains the modem configuration information.
msgtmp [ASCII TEXT] (Startup)
Temporary file used to pass text that can be quoted during
calls to an external message editor.
mzscan.dat [BITSETTYPE] (Dfiles/Mfiles)
This file contains flags to determine which message base is
scanned.
names.lst [SMALREC] (Dfiles/Mfiles)
This file contains a sorted linked pointer list of the
current users on the system. It allows quick searching for
names and numbers.
nlindex.dat [N/A] (Nodelist Directory)
Index file for raw nodelist. Required to support netmail.
shortmsg.dat [SMALLMESSAGEREC] (Dfiles/Mfiles)
This file contains the short messages (system one-liners)
still waiting for users. Messages stored in this file
include notification of:
1. Mail read by recipient
2. Access change.
3. Validation.
sprot.dat [SPROTOCOLREC] (Dfiles/Mfiles)
This file contains all the configuration information
concerning single file transfer protocols.
status.dat [SYSTATREC] (Startup/Commandline)
This file contains all the system configuration information.
This file is expected to be the in Main BBS Directory, but
may be moved to another directory if a path is specified on
the command line when booting the system. (See Command Line
Parameters).
===========================================================================
January, 1993 (Preliminary) Page 9
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
tagstr.dat [N/A] (Afiles)
Data file for programmable strings used by T.A.G. (See
Programmable Strings)
users.lst [USERREC] (Dfiles/Mfiles)
This file contains the user information of all users
currently on the system.
validate.dat [VALIDATIONREC] (Dfiles/Mfiles)
Data file containing information for the validation editor.
voting.dat [VDATAR] (Dfiles/Mfiles)
This file contains the voting board questions and current
result statistics as defined in the voting board editor. If
no voting section exists this file need not be present.
Entering the voting board editor (//IVOTES) will create this
file automatically if it does not already exist.
$who.dat [WHORECTYPE] (Afiles/Mfiles)
This file contains the multinode information regarding who
is currently logged on the system.
===========================================================================
January, 1993 (Preliminary) Page 10
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==================\
< Other System Files >
\==================/
Filename [Location] / Purpose
------------ ------------------------------------------------------------
auto.msg This file contains the auto-message that may be displayed
when a user logs onto the system.
badlogon.msg Displayed in the event of a bad logon attempt.
batchlst.tmp Temporary file containing the names and paths of files in
the current users batch queue. While this list is (usually)
kept in memory, it is written to disk during changes from
the file area to the main or message area.
bbslist.msg This file contains a list of other bulletin boards generated
by the main system "Other BBS" command.
callers.log This file contains a list of all the current day's callers,
including local calls made by SysOps.
chat.msg This file is used to save the chat session when the capture
buffer is opened with the <HOME> key. If the file already
exists, any further session captures will be appended to the
end of the file.
computer.txt The file contains a list of computers users may choose from
when choosing their computer type. The format is one line
per computer, with names being no longer than 30 characters
(those longer will be truncated).
dosmenu.msg This file contains the menu displayed from the Mini-DOS
environment when the user asks for help by entering "?".
mainadd.log Log of words that have been added to the main dictionary.
newqa.txt This file contains the answers to the new user questionnaire
(see newqq.* also).
nlindex.cfg Configuration file for NLINDEX.EXE.
nlindex.exe External utility required to compile the raw nodelist(s)
into an index file (nlindex.dat).
notest This file appears in a file section directory and indicates
that no archive checking should be performed on files
uploaded into this directory. What the file contains is
meaningless, just so long as it exists. Please note that
the file does not have an extension. (See filetest.bat).
===========================================================================
January, 1993 (Preliminary) Page 11
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
sysop.log This file contains trace information for the current day's
callers. It should be reviewed regularly as non-fatal error
messages are store here.
sysop###.log These files contain trace information for "###" days ago
(e.g. sysop5.log is the sysop.log for 5 days ago). The
maximum number of back log days is defined in the system
configuration.
sysopmnu.msg This file is displayed by the standard main menu command
";". It contains a list of the special flags and their
meanings.
system.msg This file is displayed by the standard main menu command
"I". It contains software/hardware/SysOp information about
the current system.
tag.exe Main T.A.G. executable file.
tag.ovr Overlay file for TAG.EXE.
tag[Node].$$$ Swap file used by T.A.G. when swapping to disk. Marked as
hidden and read-only, it should never be modified, renamed,
deleted, or changed.In particular, never run disk
optimization programs while T.A.G. is swapped to disk. These
programs (can) move the swap file on the hard disk, usually
resulting in a runtime error.
tagerror.log This file is created when a runtime error (See Runtime
Errors) occurs while operating the system. It contains a
screen capture of the error, the user, the date and time,
node number, last file accessed, and the runtime error type
and location to assist in determining the problem.
tagstr.exe String compiler. MUST be run to compile programmable string
files into .DAT file.
text#.msg These files are displayed when the appropriate Shift-F9 key
sequence is given. "#" is a number from "1" to "9" (e.g.
text1.msg).
trashcan.fil This file contains a list of file names which are not
allowed to be uploaded. If the file is located in the
Alternate Text File directory, it acts as a global trashcan
file. If it is located in an individual file area, it's
contents are applied to the associated directory only. The
file is in standard ASCII format, one line per illegal file
type. Wild card characters "*" and "?" are completely
supported in the file mask. The following entry formats
can be used:
===========================================================================
January, 1993 (Preliminary) Page 12
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
<FileMask>
If the file mask alone is specified, the system will simply
print a message stating that a file of that type is not
allowed in this section, for matching file names. Sample
entries:
XXX*.GIF
*.ARC
<FileMask> <Text String>
If the file mask is followed by a space and a text string,
the text string is printed in the event that a matching file
name is entered. Sample entries:
XXX*.GIF Please, no X-Rated GIF files!
*.ARC Please use the ZIP archive format!
<Filemask> @[<Path>\]<Filename>
If the file mask is followed by a space, then a "@" and a
specific filename, the file specified is printed when a
matching file name is entered. Sample entries:
XXX*.GIF @c:\bbs\dfiles\xxxgif.msg
*.ARC @c:\bbs\dfiles\noarc.msg
trashcan.fon This file contains a list of illegal phone numbers that will
be used to compare against a user phone number. The file is
in standard ASCII format, one line per number. Numbers
should be specified in a "###-###-####" format. A "?" can
be used in place of any number for a wild card effect. Short
numbers (e.g. "900" on a line) are only checked for as many
characters as specified. So in the above example, if the
area code was "900" the number would be considered invalid.
All invalid numbers are saved to the SysOp log. A sample
trashcan.fon may contain:
800
900
???-555-1212
???-911-????
111
===========================================================================
January, 1993 (Preliminary) Page 13
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
trashcan.txt This file contains a list of illegal words and names, one
line per name.
Format: [*]<IllegalName> [;comment]
Examples: *JOHN JONES ;hacked system 9/3/90
SALLY SMITH ;ex-spouse
ZAPPER ;uploaded virus to Joe's BBS
At logon (or when a name is requested when logging in as the
guest user), the name entered will be searched against the
names in the list. Case differences are ignored.
Optionally, a comment, preceded by at least one space and a
semi-colon (;) may be included so the SysOp will remember
why a name was placed in the "trash can". Names proceeded
by the special character "*" will cause the system to print
the text file getlost.msg and immediately disconnect the
user who entered the illegal name or word. This "*"
character is only active when logging on normally or as a
guest user. If the name is not preceded by the "*"
character, the user will be told s/he cannot use that name,
but will not be immediately logged off.
Example: "BURP" or "*BURP" is placed in this file.
Illegal names: "BURP", "THE BURP", "THE BURP MASTER",
"BURP BURP", etc.
Legal names: "JIM EBURP", "BURPRAT SMITH", etc.
usage.log This file contains usage information for the programmed
number of days in the system configuration. T.A.G. will
create this file if it is not present.
usage.zzz Temporary file used by T.A.G. during midnight maintenance.
user###.msg These files contain private logon messages to the users
whose numbers are specified by "###" (e.g. user128.msg).
===========================================================================
January, 1993 (Preliminary) Page 14
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==================\
< System Batch Files >
\==================/
System batch files are files that are used to execute specific programs
(external) to T.A.G. for specific functions. These are called via a shell
to DOS (See shell settings). Be aware that T.A.G. does not have "control"
of the system while shelled to an external program. Batch files should be
located in the BBS startup directory. For additional security, batch files
can be marked Read-Only.
[Parameters]
Filename {Dropfiles} / Description
-------- ------------------------------------------------------------
binkley.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{None}
Front end mailer batch file. Equivalent to MAILER.BAT.
extedit.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{DorInfo#.Def} {Door.Sys}
This file is used to invoke an external full screen editor
from the message menu. (See "Setting up the external full
screen editor").
extern#.bat [Com] [Connect] [Time] [Ansi]
{None}
These files are executed when the appropriate Alt-F5 key
sequence is given. "#" is a number from "1" to "9" (e.g.
extern1.msg). For example, one of these files could be used
to execute an external full screen chat program.
filetest.bat [Udir] [JustName] [JustExt]
{None}
This batch file is executed after an upload to test the
integrity of the file. (See "Automatic Archive Checking")
logoff.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{DorInfo#.Def} {Door.Sys}
This batch file is executed at user logoff (only if there
has been a successful logon).
logon.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{DorInfo#.Def} {Door.Sys}
This file is executed during the user logon process.
===========================================================================
January, 1993 (Preliminary) Page 15
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
mailer.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{None}
Front end mailer batch file. When the mailer front end
option is active, T.A.G.'s initialization and answering
system is not used. Instead, when booting the system T.A.G.
will shell to this file which should contain mail processing
and caller interface instructions. The front end mail
processor should return an error level, or execute T.A.G.
with options corresponding to appropriate actions (which
must be coordinated with the T.A.G. programmable options in
modem setup. See the section on "Setting up a front end
mailer" for more information. The (historical) batch file
"BINKLEY.BAT" can be used instead of mailer.bat.
mchat.bat [Ansi] [Com] [Node] [Time] [Local]
{DorInfo#.Def} {Door.Sys}
Batch file for automatic entry to multinode chat (external
program) when a user is paged from another node.
newlogon.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{DorInfo#.Def} {Door.Sys}
This file contains special feature logon instructions for a
user logging on for the first time. It is ONLY executed for
new user logons.
postdl.bat [Conn] [Com] [User#]
{None}
This file is executed after all downloads (whether batch or
otherwise) as a post processing function.
postul.bat [Conn] [Com] [User#] [Udir] [FileName] [DirName] [DirDir]
{None}
This file is executed after each upload as a post processing
function.
protocol.bat [Parameters determined from protocol settings]
{None}
This file is used by the external protocol system to call
the various external protocols via the protocol editor.
This file is used because (historically) the shell did not
return error levels correctly from executables unless they
are called from a batch file. Additionally some protocols do
not return correctly on some errors and may leave the board
sitting in DOS. Using this file fixes those problems.
It simply contains a line of parameters as follows:
%1 %2 %3 %4 %5 %6 %7 %8 %9
shellloc.bat [No parameters]
{None}
This file contains the instructions that will be executed
when a local shell to DOS is executed (See Shell to DOS).
===========================================================================
January, 1993 (Preliminary) Page 16
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
shellrem.bat [No parameters]
{None}
This file contains the instructions that will be executed
when a remote shell to DOS is executed (See Shell to DOS).
welcome.bat [Conn] [Time] [User#] [Fn] [Ln] [Ansi] [Com] [Baud] [Node]
{DorInfo#.Def} {Door.Sys}
This file is executed prior to the user logging on. It can
be used to execute programs/files via a batch file. It is
similar to logon.bat
/================================\
< Parameters passed to batch files >
\================================/
In describing the [Parameters], the following abbreviations were used:
[Ansi] A flag indicating ANSI support. A "1" if it is, a "0" if not.
[Baud] The user connect rate (DCE/DCE rate). The rate at which the
BBS modem connects with the user modem.
[Com] The comport being used.
[Conn] The REAL connect rate, i.e. computer<-->modem rate. This is
(sometimes, erroneously) referred to as the locked baud rate.
[Dir] The filename, including the ".DIR" extension, of the .DIR file.
[DirDir] The directory, including trailing backslash, of the .DIR file.
[FileName] The full filename of a DOS file.
[Fn] The users FIRST name.
[JustExt] Just the extension portion of a DOS file.
[JustName] Just the filename portion of a DOS file.
[Ln] The users LAST name. If none, it is replaced with a period.
[Local] A flag indicating Local Logon. "1" if yes, "0" if no.
[Node] The node number defined in the system config.
[Time] The number of minutes the user has left online.
[Udir] Upload directory path (with trailing backslash).
[User#] The User number of the user online.
===========================================================================
January, 1993 (Preliminary) Page 17
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=======================\
< Fido Message Base Files >
\=======================/
"Fido" style message base implies that a separate directory is set up for
each different message area, and that individual messages (and the
associated header information) are kept in separate files.
The advantage to this style is that corruption of the message area is
virtually impossible. The disadvantage of Fido style tends to be disk
usage, (dependant on cluster size), and speed (depending on the number of
messages in a base, DOS can drag after 255 files in a directory).
Filename Description
------------ ------------------------------------------------------------
########.msg For a FIDO style message base, these files contain the
actual header and text for each message. Messages are
generally numbered consecutively, starting at 1. Fido
format is also referred to as "1.msg" format because of this
numbering system. As messages are deleted, and new ones
added, periodic renumbering is required.
lastread This file contains the last read pointers for fido style
message systems. For each Fido message area defined, a
lastread file resides in that directory. It consists of one
record per user, each record containing one integer
indicating the last message number read in that area.
echotoss.log The log file created/appended by T.A.G. when a message is
posted in an area that is defined as "Echomail". The EchoTag
for the area is written to this flat ASCII text file for
processing by an echomail scanner.
nettoss.log File created whenever Netmail is posted within T.A.G. (Some)
Mailers or batch files can use this file to determine the
need to rescan the netmail directory.
===========================================================================
January, 1993 (Preliminary) Page 18
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=========================\
< Hudson Message Base Files >
\=========================/
"Hudson" style message base implies a "database" that combines a maximum of
200 separate message areas into two separate files (MSGHDR.BBS for header
information, and MSGTXT.BBS for the actual message text), and several index
files for faster access.
The advantage to this style is space savings (dependant on disk cluster
size) and speed (dependant on number of messages per area). The general
disadvantage is the risk of corruption, where losing the single MSGHDR.BBS
file can wipe out *all* message areas.
Filename Description
------------ ------------------------------------------------------------
echomail.bbs This is a binary file containing the number of messages the
user posted while online.
lastread.bbs This file contains the last read pointers for Hudson/RA
format message bases. For each Hudson/RA message file
defined (which can contain up to 200 individual message
areas) there is one lastread.bbs file. It consists of one
record per user, each record containing 200 integers, one
for each Hudson/RA message board.
msghdr.bbs This file contains message header information for remote
access style message systems.
msgidx.bbs This file indicates which base each message is in, for
remote access style message bases.
msginfo.bbs This file contains the low and high pointers of each message
base. It also contains the total number of messages. This
file is only present in remote access style message systems.
msgtoidx.bbs This file contains the index of the message system for
remote access systems.
msgtxt.bbs This file contains the message text for remote access style
systems.
===========================================================================
January, 1993 (Preliminary) Page 19
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/====================\
< System Display Files >
\====================/
System Display Files are files which, during the course of using the BBS,
are displayed to the user during certain functions.
Display files can have two extensions: MSG and CLR.
The general rules for display files:
*.MSG files are displayed to non-ANSI users.
*.CLR (or) *.MSG files are displayed to ANSI users.
If a *.CLR file does not exist, the corresponding *.MSG file will be
displayed.
Display Files are kept in the Afiles (Alternate Text File) directory,
unless otherwise noted.
Filename Description
----------- ------------------------------------------------------------
<BoardName> These files contain descriptions of file sections
corresponding to the board name defined in the file section
manager.
<HelpID>#[-SL] These files are customized menu files for the help level
represented by "#" (may be from 2 to 4). The HelpID is
defined in the menu system for each menu. See the menu
documentation for more information.
access This file is displayed to users when they successfully
validate themselves with the auto-validation command
(PKey="5").
arflags If present, this file is displayed when the command to
toggle a user's AR flags is executed. This allows the SysOp
to define a reminder of the meaning for each AR flag.
arlevel@ This file is displayed at logon to each user with the
corresponding AR flag '@' set in their user record. "@" is a
letter from "A" to "Z" (e.g. arlevelb.msg or arlevelg.msg).
birthday This file is displayed whenever a user calls on their
birthday. If it does not exist, a default congratulations
is used (see postbday).
bdlprot This file is used to create a customized batch download
protocol menu instead of using the standard system generated
menu.
===========================================================================
January, 1993 (Preliminary) Page 20
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
bulprot This file is used to create a customized batch upload
protocol menu instead of using the standard system generated
menu.
bullet@@ These files are the actual bulletins used by the bulletin
system. "@@" are the ID characters typed by the user and
may be any two valid file name characters.
EXAMPLES:
bullet1.msg The user types "1" to read this file
bulletab.msg The user types "ab" to read this file
bulletb6.msg The user types "b6" to read this file
bulletin This file contains the list of main bulletins available on
the system and their corresponding ID characters. ID
characters are explained below in the "bullet@@" file
description.
bupload This file is displayed prior to requesting the protocol to
use for batch uploading a set of files. It normally contains
additional notes concerning batch uploads specifically (e.g.
don't upload something unless you've specified it in the
queue).
chatoff This file can be user for an alternate response to the SysOp
available command when the chat call is off (see chaton.*
also).
chaton This file can be used for an alternate response to the SysOp
available command when the chat call is on (see chatoff.*
also).
computer This file is displayed in place of the automatically
generated computer type listing taken from computer.txt.
dsl### These files contain a message that is displayed at logon to
all users with the DSL specified by "###". "###" is a
number from 0 to 255 (e.g. dsl10.clr).
fgrp[-sl] This file is displayed when the user is prompted to enter a
file group. Individual files can be set up by security
level.
getlost This file is displayed when a user enters a name or word in
the trashcan.txt file that is proceeded by a "*". See the
description of the trashcan.txt for more information. This
is normally used for terms such as "FUCK", since it should
not be used as part of a user name.
goaway This file is displayed when the user has paged the SysOp
more than the maximum number of times defined in the system
configuration.
===========================================================================
January, 1993 (Preliminary) Page 21
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
guest This file is displayed to a guest user just prior to requesting
a unique name or handle from them. It is normally used to
describe how to become a registered user and other such things
guest users need to know.
hangup# These files are displayed when the appropriate Shift-F5 key
sequence is given before disconnecting the user. "#" is a
number from "1" to "9" (e.g. hangup1.msg)
lockout This file is displayed when a locked out user attempts to log
onto the system. Locked out users have a user number different
from their record number, but not zero. After displaying the
file, T.A.G. hangs up and returns to the wait screen.
logoff This file is displayed when a user logs off the system in the
normal method.
logon This file is displayed right after the last few callers and
caller number when a user logs onto the system. An option
appears on the default menu system to reprint this file in case
the user missed it.
logon# These files are displayed after the logon.msg file when a user
logs onto the system in increasing order. "#" is a number from
"1" to "9".
mgrp[-sl] This file is displayed when the user is prompted to enter a
message group. Individual files can be set up by security
level.
newuser This file is displayed to all new users after they are given
their user number. It is normally used to describe the rules
of the system and other things new users should be aware of.
newqq This file is the new user questionnaire. Both it and the
questionnaire system must exist before it will be used. See
the questionnaire documentation for more information (see
newqa.txt also).
noaccess Displayed when users choose menu options which are inaccessible
(the privilege SL can cause inaccessible commands to display).
noboard This file, if present, is displayed when a user with a DSL
lower than the "privilege" level defined in the system
configuration tries to access a file board that is only
available to validated users.
nochat This file is displayed when a user attempts to page the SysOp
and either the chat flag is off, or the SysOp fails to answer
the chat call.
===========================================================================
January, 1993 (Preliminary) Page 22
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
nonewusr This file is displayed in two different cases. The first being
when a new user attempts to logon to a closed T.A.G. system
(one which is not allowing new users). Or secondly, when a new
user trying to logon to a T.A.G. system fails to enter the
correct new user password defined in the system configuration.
In both cases the user is disconnected after the file is
displayed.
novice This file is displayed to a new user for NNN number of logons
(0-255). The actual number of times the file is displayed is
specified in the system config.
nusermsg This file is displayed prior to allowing a new user to enter a
new user message to the specified user defined in the system
configuration. It is generally used to explain what the letter
is and what is should contain.
other This file contains help and information which is displayed when
a user is adding a number to the other BBS listing.
pastbday This file is displayed when a user has had a birthday within 30
days of their last call. If it does not exist, a default
congratulations is displayed (see birthday.* also).
postcall This file is displayed anytime a user fails the post/call ratio
check.
postdl This file, if present, is displayed after each download.
Generally it will be used to inform the user of the number and
size of his/her total uploads and downloads.
postul This file, if present, is displayed after each upload.
Generally it will be used to inform the user of the number and
size of his/her total uploads and downloads.
prequest This file is displayed prior to requesting the required new
user information from a user. If is normally used to explain
that the information they are about to enter is confidential.
quotehlp This file contains help text to the user explaining the /QUOTE
feature in the message base.
sl### These files contain a message for all users with the SL
specified by "###". "###" is a number from 0 to 255 (e.g.
sl10.msg).
sdlprot This file is used to create a customized single file download
protocol menu instead of using the standard system generated
menu.
sulprot This file is used to create a customized single file upload
protocol menu instead of using the standard system generated
menu.
===========================================================================
January, 1993 (Preliminary) Page 23
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
sysfull This file is displayed to any new users who try to logon after
the system has reached the maximum number of users.
taglines This file is used when a user uses the /TAGLINE feature in the
message editor to add tagline and save. The taglines in the
file can be multiline, but must be separated from each other by
a blank line.
tagquote The system has the ability to automatically display quotes when
a user logs on, provided you have a quote file. There are many
available, or you can create your own. There is also a
Pkey/Pdata available to display a random quote from a tagquote
file. The quotes in the file can be multiline, but each must be
separated from each other by a blank line. To use a message to
the user other than the system standard "You quote of the day
is:", the first line of the file must be ~ followed by the
prompt. i.e. "~The joke of the day is:".
upload This file is displayed just prior to requesting the file name
of the file the user wishes to upload. It normally contains
rules and procedures user should follow before uploading a
file.
welcome This file is displayed when the user first connects with the
system. It normally welcomes the user to the system and may
contains a brief system description and/or information on
becoming a user of the system.
welcome# These files are displayed after the welcome.msg file in
increasing order. "#" is a number from "1" to "9" (e.g.
welcome1.msg).
===========================================================================
January, 1993 (Preliminary) Page 24
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============================\
< T.A.G. Command Line Parameters >
\==============================/
T.A.G. supports several command line parameters on boot up. They may
(optionally) be preceded by "/" or "-". It is only necessary to include
enough of the option to make it unique (e.g. "A=100" is synonymous with
"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. This option
(permanently) changes the setting in the system
configuration.
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.
===========================================================================
January, 1993 (Preliminary) Page 25
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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. This
parameter is used when the status.dat file is not
located in the Main BBS Directory. For example, if
you should have enough space on your RAM disk to run
the system, it would be advised to move the status.dat
file off to a permanent storage device since it
changes constantly.
NOTES: You must specify CONNECTRATE, CONTROLCODE, or LOGON first to
initiate an immediate logon before including AFTERUSERERRLVL,
ERRORCORRECTING, HALFDUPLEX, or REALRATE.
===========================================================================
January, 1993 (Preliminary) Page 26
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/====================\
< Sysop Functions Menu >
\====================/
The SysOp Functions Menu is accessed via the ^Q (Control-Q) Hotkey by users
with authorized access (see System Configuration, Single value security
settings, SL/AR - Sysop Menu). The basic SysOp Functions Menu is:
<< SysOp Functions Menu >>
(A) Access validation editor (B) Message section editor
(D) Mini-DOS system (E) Event editor
(F) File section editor (L) System logs
(M) Menu editor (P) Protocol editors
(S) System configuration (U) User editor
(V) Voting board editor (W) Word validation
SysOp (A,B,D,E,F,L,M,P,S,U,V,W,Q=Quit):
Access to the individual commands under the SysOp Functions Menu is also
secured by system passwords #1, #2, or #3 (See System Configuration, System
Passwords), depending on the particular command.
Each area on the SysOp Functions Menu also has a corresponding Pkey, and
Pdata, allowing direct access from the normal T.A.G. menu system (see the
Menu documentation on exact Pkeys/Pdata for each function).
Additionally, most areas of the SysOp Functions Menu are also available
directly from the Wait Screen.
When accessing "System Configuration", the following prompt will be
displayed.
FA? Yes
: XXXXXXXXXXXXXXXX
"FA?" asks if the user wishes Full Access to the functions in the system
configuration. If full access is requested, the user must enter SysOp
password #3 to gain access, otherwise they must enter SysOp password #2.
Limited access only allows a user to change functions "K" through "O". All
other functions have a "Look but don't touch" status.
When accessing the system configuration function on-line, the system
passwords cannot be viewed or changed by anyone unless they have a SL of
255. SysOp password #3 is NOT displayed on-line and cannot be changed;
this password can only be viewed or changed locally for obvious security
reasons.
Each area of the SysOp Functions Menu is detailed in the following pages.
===========================================================================
January, 1993 (Preliminary) Page 27
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/========================\
< Access Validation Editor >
\========================/
The Access Validation Editor allows the sysop to easily set up "Standard"
settings for users, with respect to security levels, Access Restriction and
Special Flags, and allows for initializing the user "Banking" functions:
File Points, Time Bank, and Mail Credits.
A "New" users access is determined at logon by the settings in the default
user record (See User Editor, Default User Settings). "Validation" is the
process of setting their SL and DSL to other than the defaults.
Validation can be accomplished in a number of ways, including manually or
automatic in the User Editor, from reading mail from a user, or from the
Auto-Validation command. All depend heavily on the settings in the Access
Validation Editor.
The Access Validation Editor main screen (SysOp password #3 required):
## Key SL DSL AR flags SF flags Fpoint TmBank Credit
-- --- --- --- -------------------------- --------------- ------ ------ ------
You have been ***VALIDATED***. Thanks for calling!
1 N 50 50 ----E--------N------------ ------G-------- 0 60 0
You have been ***VALIDATED*** as a REGISTERED user. Thanks for calling!
2 R 75 75 ----E--------N---R-------- ------G-----M-- 0 120 0
You have been ***VALIDATED*** as a VISITING SYSOP. Thanks for calling!
3 S 100 100 ----E--------N----S------- ------G-----M-- 0 360 0
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit):
Access Validation Fields:
## Record Number - Used to reference the Validation Record you want
to change for all functions.
Desc Description - A short message that is sent to the user when they
are validated with a particular validation key.
Key Validation Key - The single key which is associated with a
validation level. This is the key that will be entered for
"Validation Level" when you validate a user. The letter to use
does not matter, and is left to the sysop. Almost all the
"standard" keys are available. However, logic dictates that the
key should be mnemonic, such as "R" for regular user or "S" for
Sysop.
SL/DSL Security Level/Download Security Level - The Security Level and
Download Security Level to be associated with a particular
Validation Key.
AR/SF Access Restriction/Special Flags - The Access Restriction and
Special flags to be associated with a particular Validation Key.
===========================================================================
January, 1993 (Preliminary) Page 28
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Fpoint File Points - The initial File points to be give a user validated
with a particular Validation Key.
TmBank Time Bank - The initial amount of time in the users time bank when
validated with a particular Validation Key.
Credit Credits - The initial number of credits (Used for Netmail) to give
to a user validated with a particular Validation Key.
/=======================\
< Auto Validation Command >
\=======================/
If you use an auto validation command (See the Menu Documentation on
configuring an Auto Validation Command), then you must also set up a
special validation level using the "~" (tilde) key. This level is assigned
to the user upon entering the correct password.
/=======================================\
< Adding the Validation Manager to T.A.G. >
\=======================================/
A new access validation manager (which is available from the SysOp
Control-<Q> Menu) can be added to your a menu using:
Function: Access validation manager (requires 3rd password)
Pkey : 1
Pdata : A
See the Menu Documentation for further information.
/===========================\
< Deleting Validation Records >
\===========================/
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit): D
Validation record number to delete (1-2):
The specified Validation Record is deleted, and the records are renumbered.
/============================\
< Inserting Validation Records >
\============================/
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit): I
Validation record number to insert before (1-3):
A new (Default) Validation Record is added at the position specified, and
the records are renumbered.
===========================================================================
January, 1993 (Preliminary) Page 29
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/============================\
< Modifying Validation Records >
\============================/
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit): M
Validation record number to start editing (1-3): 1
Validation Rec: 1
1. Key : N
2. Description:
You have been ***VALIDATED***. Thanks for calling!
3. SL : 50
4. DSL : 50
5. AR flags : ----E--------N------------
6. SF flags : ------G--------
7. Time bank : 60 minutes
8. File points: 0 points
9. Mail credit: 0 cents
Validation edit: (1-9,[,],B,J,T,Q,?): Q
/========================\
< Validation Edit Commands >
\========================/
Validation edit: (1-9,[,],B,J,T,Q,?): ?
1-9:Change item number specified
[:Back one record [:Forward one record
B:ottom - Last record J:ump to record number
T:op - First record Q:uit and save
Command Function
======= ===============================================================
1-9 Entering a number from 1-9 permits editing of the selected field
[ Move to the prior (Backwards) Validation Record.
] Move to the next (Forwards) Validation Record.
T Move to the first (Top) Validation Record
B Move to the last (Bottom) Validation Record.
J Prompts for a Validation Record number to Move (Jump) to.
Q Quits the Validation Record Editor.
===========================================================================
January, 1993 (Preliminary) Page 30
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============================\
< Positioning Validation Records >
\==============================/
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit): P
Enter number of validation record to move (1-2): 2
According to the current numbering system.
Enter number of validation record to move this before (1-4): 1
[> Moving validation record entry.
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit): Q
Moves the specified Validation Record according to the specified new
position.
/============\
< Shell System >
\============/
The shell swap system 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.
1. Swap shell is normally active : Yes
2. Use expanded memory (EMS) if available: Yes
3. Use extended memory (XMS) if available: Yes
4. Memory usage priority setting : EMS over XMS
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
M. Logoff No Yes Default
Shell settings: (1-4,A-M,Q=Quit):
===========================================================================
January, 1993 (Preliminary) Page 31
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Each of the programs T.A.G. calls externally 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 (to SYSOP.LOG)
the fact that the external program was called.
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
===========================================================================
January, 1993 (Preliminary) Page 32
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/====================\
< System Configuration >
\====================/
The System Configuration Main Screen (Password #2, or #3 required):
A. System passwords.
B. System information and directories.
C. Communications configuration.
D. Single value security settings.
E. General variables.
F. Optional flagged functions.
G. Shell settings.
H. New user question configuration.
I. Time limitations ......................\\ Complete
J. Calls allowed per day ..................\\ range
K. Upload/download number of files ratio... >>
L. Upload/download K-bytes ratio...........// security
M. Post/call ratio .......................// settings.
N. Multi-user configuration.
System configuration: (A-N,Q=Quit):
/================\
< System Passwords >
\================/
A. System Passwords Main Screen:
1. SysOp password #1: "LITTLEPASS"
2. SysOp password #2: "MEDIUMPASS"
3. SysOp password #3: "BIGPASS"
4. New User password: "LEMMEIN"
5. Chat password : "HELP!"
System passwords: (1-5,Q):
This allows you set any of the master system passwords, the new user
password, and the Chat password. The third SysOp password can only
be changed by calling the system configuration locally.
1. SysOp password #1:
This password is used for remote logon of users at or above the SysOp
level (See System Configuration, General Security Levels), reading
any private mail not belonging to the user and entering the user log
editor.
2. SysOp password #2:
This password is used for the message section manager, file section
manager, events editor, limited system configuration access on-line,
and the protocol editors (Single and Batch).
===========================================================================
January, 1993 (Preliminary) Page 33
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
3. SysOp password #3:
This password is used for the menu editor, full system configuration
access, shell to DOS command, the default shut down system password,
and the OVERRIDE command in the Mini-DOS environment.
4. New User password:
This password, if set, is required before any new user is allowed to
logon the system. New users logging on locally will not be required
to enter this password.
5. Chat password:
This password, if set, will permit a user to activate the chat call
by typing the password as the first word in his/her chat reason even
though the chat call has been turned off.
/==================================\
< System information and directories >
\==================================/
1. System name : Great T.A.G. BBS!
2. SysOp name : Joe SysOp
3. Board phone : 999-999-9999
4. Board address: 1:9999/999@FIDONET.ORG
5. System is : Open
6. Time limits : Represent the total time allowed for use each day
<< System Directories >>
A. Main data file directory :"C:\BBS\DFILES\"
B. Alternate text file directory :"C:\BBS\AFILES\"
C. Swap file directory :"C:\BBS\SWAP\"
D. Nodelist directory :"C:\BINKLEY\NODELIST\"
E. Dictionary directory :"C:\BBS\DICT\"
F. Temp download directory :"C:\BBS\TEMPDL\"
System information: (1-6,A-F,Q):
1. System name:
This string specifies the name of the system currently running. T.A.G.
displays this field on the wait screen, to the caller, and uses it for
the RBBS (tm) door file.
2. SysOp name:
This string specifies the name of the system operator. T.A.G. uses this
field for the RBBS (tm) door file.
3. Board phone:
This string specifies the telephone number of the system. This is used
as a sample whenever a telephone number is requested by the system.
Users are not allowed to enter the BBS number for their voice phone
number.
4. Board Address:
This is a full FidoNet (tm) compatible address for the system. It is
only used when message areas are marked as "Echo" or "Netmail".
===========================================================================
January, 1993 (Preliminary) Page 34
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
5. System is (Open/Closed):
This defines whether or not a system allows new users. Most systems,
called "Open" systems, allow new users. If you wish to have a private
system where new users are NOT allowed this option should be set to
"Closed".
A. Main data file directory:
This string is the complete path name of the Main Data File Directory,
which contains most of the files which change as the system is begin
used (user log, message section header files, etc).
B. Alternate text file directory:
This string is the complete path name of the Alternate Text File
Directory, which contains most of the read-only system files (text
files, programmable text strings, etc).
C. Swap file directory:
When a DOS shell or door program is executed, T.A.G. may optionally
remove itself from RAM (except for approximately 7K of overhead) in
order to provide the maximum possible memory to the shell program.
T.A.G. can optionally swap to disk, EMS or XMS memory (See System
Configuration, Optionally Flagged Functions). This string contains the
pathname where T.A.G. will swap to until the shell program is complete.
T.A.G. will swap to disk if disk is chosen, or if EMS/XMS is selected
and not enough available EMS/XMS exists.
D. Nodelist directory:
This is the path where T.A.G. can find the raw nodelists, and the index
file NLINDEX.DAT. This directory is required only if your system is
running Netmail with T.A.G.
E. Dictionary directory:
This is the directory path where T.A.G. can find the dictionary files.
This directory is required only if you install the dictionary files to
allow use of the spelling checker during message posting.
F. Temp Download Directory
This is the directory where files are copied if file areas are marked as
"CD ROM". See the section "Setting up a CD ROM" in the file section.
===========================================================================
January, 1993 (Preliminary) Page 35
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/============================\
< 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)
A. No call reinit time:
This value defines the number of minutes of inactivity between calls
before T.A.G. will re-initialize the modem.
B. Com-port Number:
This value defines the communication port to which the modem is
connected. Communication ports COM1 through COM4 are supported
internally at this time. Other COM ports require setting the command
line startup parameters IRQ and BASEADDRESS (See T.A.G. Startup
Parameters), or the use of an external fossil driver.
C. Carrier Detect Mask:
This number is the mask value used to determine if a carrier is present
on the system from the port hardware. I have yet to see a system where
this setting is not "128".
D. Use FOSSIL driver:
This setting defines whether the communication between the hardware and
the modem will be controlled directly by T.A.G. or indirectly through an
independent FOSSIL (Fido/Opus/SEAdog Standard Interface Layer) driver
such as OpusCom or X00.
E. Modem configuration:
Entering Modem Configuration brings up the current (Active) modem
configuration, and allows editing of values.
===========================================================================
January, 1993 (Preliminary) Page 36
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===================\
< 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 (Fixed)
E. CTS/RTS hardware flow control: Yes
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.
===========================================================================
January, 1993 (Preliminary) Page 37
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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.
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 (Special Characters):
Configuration of result codes for this modem. See the section below
(Modem Result Code Configuration) 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 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 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 exit modem
command mode via the escape sequence and hangup the caller.
7. After Hangup:
String sent to the modem after a user logs off the system.
===========================================================================
January, 1993 (Preliminary) Page 38
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
8. Exit System:
String sent to the modem when exiting T.A.G.
/===============================\
< Modem Result Code Configuration >
\===============================/
The Modem Configuration, Result Code 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.
Example:
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.
===========================================================================
January, 1993 (Preliminary) Page 39
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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. BinkleyTerm uses error
level 20 for this purpose; see the control code field for information
on setting error levels.
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.
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.
===========================================================================
January, 1993 (Preliminary) Page 40
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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.
/=================================\
< How an Incoming Call is Processed >
\=================================/
The following is a brief description of how an incoming call is processed
by T.A.G.: To prepare the modem, T.A.G. sends the initialization string and
waits. When an incoming call occurs, the modem sends the RING result code
to the computer. T.A.G. responds by sending the modem answer string to take
the modem off hook and waits for a legal result code (indicating connect
baud rate and error correction factor, if any) from the modem. If one is
received the board takes the proper course of action by sending a welcome
message and prompt to the user logging on; if not, after 45 seconds of
waiting, T.A.G. will assume the call has failed and disconnect by dropping
the terminal ready line and/or sending the modem hangup string, then start
this process over again.
Note: A modem with a 100% compatible Hayes command set is HIGHLY recommend,
although it may be possible to apply this configuration to other
command systems.
AT : Attention Modem
H0 : Put the phone on-hook (hangup)
Q0 : Modem result codes on
V0 : Digit result codes
E0 : Command echo off
M0 : Speaker always off
&D2 : Configure the modem to disconnect from the communication
lines and return to the command state upon detecting an ON
to OFF transition of the DTR interface signal
S0=0 : Disables auto-answering on the modem
S2=1 : Sets the escape code value to Control-A (1 DEC)
S10=10 : Disconnect wait time value (1 second)
===========================================================================
January, 1993 (Preliminary) Page 41
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============================\
< Single value security settings >
\==============================/
1. SL-Full SysOp :250 2. SL-CoSysOp of system :200
3. SL-Add words to dictionary :10 4. DSL-Download system CoSysOp :200
5. DSL-No download ratio check :200 6. SL-Add a system to BBS list:10
7. SL-Send normal private mail:10 8. DSL-See unvalidated files :100
9. SL-See who posted anonymous:200 10. SL-Reply to anonymous mail :200
11. SL-Post any pub anonymously:240 12. SL-Send anonymous private :240
13. RSL-See passwords remotely :255 14. SL-No post/call ratio check:200
15. SL-Privilege :10 16. DSL-Privilege :10
17. DSL-No download point check :200 18. SL-SysOp password #1 logon :255
19. SL-Read text file into msg :200 20. SL-Modify message flags :250
21. SL-Netmail file attach :250 22. SL-Netmail file request :250
23. DSL-Browse menu UL/DL :50 24. SL-Message tag line :240
A. AR - Post/call key flag :@
B. SL/AR - Sysop menu :240/@
C. SL/AR - User Edit :250/Z (Password:Off)
D. KEY - Expired validation key:None
Single value security: (1-24,A-D,Q=Quit):
1. Full SysOp:
The minimum SL required before a user is considered to have full SysOp
access.
2. CoSysOp of system:
The minimum SL required before a user is considered to have CoSysOp
access.
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.
4. Download system CoSysOp:
The minimum DSL required before a user is considered to have download
CoSysOp access.
5. No download ratio check:
The minimum DSL required before a user's download ratio is no longer
checked.
6. Add a system to BBS list:
The minimum SL required before a user may add a BBS to the other BBS
listing command. (Of course they must first have access to the command
for this to mean anything.)
===========================================================================
January, 1993 (Preliminary) Page 42
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
7. Send normal private mail:
The minimum SL required before users are allowed to send private message
to users below CoSysOp access level.
8. See unvalidated files:
The minimum DSL required before users are allowed to see unvalidated
files in section list.
9. See who posted anonymous:
The minimum SL required before a user can see who really posted an
anonymous message (Public, Private, or Auto-Message).
10. Reply to anonymous mail:
The minimum SL required before a user can reply to anonymous messages
(Public, Private, or Auto-Message).
11. Post any pub anonymously:
The minimum SL required before a user is allowed to post anonymous mail
on any public message section.
12. Send anonymous private:
The minimum SL required before a user can send anonymous private
messages to other users.
13. See passwords remotely:
The minimum SL required before the system will display passwords of
users to a remote caller. Note that this SL is the real SL that the
user has, temporary sysop access will not allow users to see passwords.
14. No post/call ratio check:
The minimum SL required before a user's post/call ratio is no longer
checked.
15. Privilege (SL):
The highest SL at which items users do not have access to are displayed.
This includes commands and message sections. The main use of this
feature is to show users what they "will" have access to if they
continue to call the system.
16. Privilege (DSL):
The highest DSL at which items users do not have access to are
displayed. This includes commands and file sections. The main use of
this feature is to show users what they "will" have access to if they
continue to call the system.
17. No download point check:
The minimum DSL required before a user's file points are no longer
checked.
18. SysOp password #1 logon:
The minimum SL required before a user must enter SysOp password #1 to
log onto the system remotely.
===========================================================================
January, 1993 (Preliminary) Page 43
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
19. Read text file into msg:
The minimum SL required before a user is allowed to read a text file
into a message with the "/read <[Path]\Filename.Ext>" command.
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.
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.
23. DSL-Browse menu UL/DL:
DSL necessary for the "Upload" and "Download" commands to appear on the
browse files menu
24. SL-Message tag line:
SL necessary to use the /TAGLINE command (append tagline) in the message
editor.
A. Post/call key flag:
The floating AR flag which the system will use to indicate whether the
user is within the post call ratio specified. When the user is within
their post/call ratio, the flag is set by the system, otherwise it is
reset. Any system functions requiring this flag for access would only
be available when the user is with their post/call ratio. A setting of
"@" indicates that no post call ratio flag exists.
B. SL/AR - Sysop menu:
These settings define the minimum SL and AR flag required to access the
SysOp menu on-line. Users must meet the required SL AND have the
designated flag in order to access the SysOp menu.
C. SL/AR - User Edit/Password:
These settings define the minimum SL and AR flag required to access the
User editor jump (Control-U). Users must meet the required SL AND have
the designated flag in order to access the command. If password is On,
user will be prompted for system password #1.
D. KEY - Expired validation key:
Validation key to use from the "Access Validation Editor" to validate
users with after their accounts expire.
===========================================================================
January, 1993 (Preliminary) Page 44
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=================\
< General variables >
\=================/
1. Max private sent per call :20 2. Max feedback sent per call :10
3. Max public posts per call :25 4. Number back SysOp log days :14
5. Number days keep Usage Log :365 6. Max number of logon tries :5
7. Percent upload time refund :150% 8. Default read message menu :11
9. Maximum pages per call :3 10. Starting logon menu number :1
11. Minimum K-Bytes to post :100 12. Minimum K-Bytes to upload
:500
13. Maximum number of users :2000 14. Maximum files batch download:30
15. Maximum files batch upload :20 16. Number of novice msg days :30
17. Max daily time bank deposit :120 18. Max daily time bank
withdraw:120
19. Maximum time in time bank :1440 20. Auto message maximum lines :10
21. Default user edit list mode :1
A. Default message group mask:""
B. Default file group mask :""
C. Menu fast command keys :"/"
D. Chat colors
General variables: (1-21,A-D,Q=Quit):
1. Maximum private sent per call:
The maximum number of private messages that a user can send per call.
2. Maximum feedback sent per call:
The maximum number of messages a user can send to the SysOp per call.
3. Max public posts per call:
The maximum number of public posts allowed per call.
4. Number back SysOp log days:
The number of days the system keeps old sysop.log files. These files
are renamed to sysop1.log, sysop2.log, sysop3.log, etc to indicate how
many days old the log is for (e.g. sysop5.log is the sysop.log from 5
days ago).
5. Number days keep Usage Log:
The number of days the system keeps line entries in the usage.log for.
Each line represents the system statistics for the date listed.
6. Max number of logon tries:
The number of tries a user has to logon the system before they will be
disconnected. Systems having trouble with callers trying to logon as
other users should set this to a very low value, thus requiring the
caller to call back more often.
===========================================================================
January, 1993 (Preliminary) Page 45
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
7. Percent upload time refund:
The percent of time spent uploading a file that is refunded to users
after the upload has completed. For example: A user spends 20 minutes
uploading a file. A 50% refund means the user gets 10 extra minutes
on-line so they only lost 10 actual minutes (20-10) of on-line time
uploading the file.
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".
9. Maximum pages per call:
The maximum number of times a user can page the SysOp per call. Pages
after this value is reached will be ignored and a firm message will be
displayed asking the user to try again later (see goaway.msg also).
10. Starting logon menu number:
The menu at which users logging onto the system are first sent to.
11. Minimum K-Bytes to post:
The minimum number of K-Bytes required on the drive containing the
Message Text File Directory before a user is allowed to post a public or
private message.
12. Minimum K-Bytes to upload:
The minimum number of K-Bytes required on the drive containing the
upload directory of the section in question before the user is allowed
to upload file.
13. Maximum number of users:
The maximum number of users the system will allow before sending the
next new user the SYSFULL.MSG file and preventing them from logging on.
14. Maximum files batch download:
The maximum number of files a user is allowed to place in the download
queue for batch transfer. This value may be from 1 to 30.
15. Maximum files batch upload:
The maximum number of files a user is allowed to place in the upload
queue for batch transfer. This value may be from 1 to 20.
16. Number of novice msg days:
The number of times that the file novice.* is displayed to a new user.
17. Maximum daily time bank deposit:
The maximum amount of time, per day, that a user is allowed to deposit
in the time bank.
===========================================================================
January, 1993 (Preliminary) Page 46
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
18. Maximum daily time bank withdraw:
The maximum amount of time, per day, that a user can withdraw from the
time bank.
19. Maximum time in time bank:
The highest amount of accumulated time which can exist in a user's time
bank.
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 during Automessage
entry.
21. Default user edit list mode:
This setting determines the list mode when using the user editor, or
invoking the Ctrl-U (jump user editor) command.
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.
D. Chat colors:
This allows a user to change the defined ANSI colors used in chat.
===========================================================================
January, 1993 (Preliminary) Page 47
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==========================\
< Optional flagged functions >
\==========================/
A. Title screen pause :No B. Blank off-line wait screen :Yes
C. Logon to bulletin section :On D. Handles allowed on system :Yes
E. Keyboard security protection:Off F. Front end mailer :On
G. New user message sent to :Off H. SysOp mail forwarded to user:1
I. Minutes before time out :4 J. Minutes before time out bell:3
K. Guest user number :Off L. The system operator is :Male
M. Store bad logon information :Yes N. Logon uses Auto-Message :Yes
O. Logon takes phone off-hook :No P. Generic logon information :No
R. Logon asks for phone number :Yes S. Alert beeps if chat on :Yes
T. Auto chat buffer open :On U. Scan/FileFind in SysOp Log :On
V. Direct screen writes :Off W. Screen snow checking :Yes
X. Try to use EMS for overlays :Yes Y. Instant logon key :Yes
Z. Local security :No 1. Show available upload space :On
2. Show GIF resolution :No 3. Force scan before upload :On
4. Local logon SysOp window :Off 5. Show files open (debug) :On
6. Log modem activity (debug) :On 7. Wait screen action disable :On
8. Dynamic message numbering :On 9. Dynamic file numbering :On
0. Forced voting at logon :Off !. Warning days for user expire:Off
@. Failed logon message sent to:1 #. Wait screen messages waiting:Off
Flagged functions: (A-P,R-Z,0-9,!,@,#,Q=Quit):
A. Title screen pause:
This setting determines whether the [PAUSE] function is active during
the logon process, before entering user name or user ID number.
B. Blank off-line wait screen:
This setting determines whether T.A.G. will blank out the wait screen
after 3 minutes of inactivity. Using this feature prevents burn-in on
some monitors if they should be accidentally left on.
C. Logon to bulletin section:
This setting determines whether users are sent to the bulletin section
as they are logging on. When deactivated, a menu command is the only
means to access the bulletin system.
D. Handles allowed on system:
This setting determines whether users are allowed to use handles (pseudo
names) when logging onto the system. User prompts are changed to
indicate the "no handle" restrictions if this switch is turned off.
E. Keyboard security protection:
This setting determines whether special features are used to provide a
limited local mode security. When this option is active, passwords are
not displayed in the top window when users logon. Additionally, whenever
passwords are entered, "X"'s are echoed both locally and remotely.
===========================================================================
January, 1993 (Preliminary) Page 48
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
F. Front End Mailer:
This setting controls whether a Front End Mailer is active as a front
end system for T.A.G. This feature is used in conjunction with the
TAGMail system to provide full Net/Matrix/Echo mail service. T.A.G. will
shell to the file binkley.bat or mailer.bat and process incoming result
codes when it is active.
G. New user message sent to:
This setting controls whether new users are forced into entering a
private message (usually a validation request) when logging on. When
setting this feature active, you will be prompted for the user number to
whom these messages will be sent (usually the SysOp or a Co-SysOp). If
this feature is enabled, the new user message cannot be aborted by the
user, even through the /ABT editing command providing enough disk space
is available. (See nusermsg.msg also.)
H. SysOp mail forwarded to user:
If enabled, this defines the user number to which private messages
addressed to "SYSOP" are forwarded. It is used when the SysOp goes by
another name since users often do not notice and try to send mail to the
"SYSOP" anyhow.
I. Minutes before time out:
This defines the number of minutes the system waits for a key press
before disconnecting a user for inactivity. Although this feature may be
disabled, it is NOT recommended that you do so (see the feature below
also).
J. Minutes before time out bell:
This defines the number of minutes the system waits for a key press
before a bell character is sent to the user warning that the system is
getting impatient. Selecting a number greater than that defined in the
above feature will render it useless.
K. Guest user number:
This allows the SysOp to specify a guest user account on the system. The
Guest account can then be used by users who know they will never call
back, or those who wish to look the system over before deciding whether
to get an account.
The following steps must be taken in order to create a guest user
account:
1. Logon as a new user to create an account that will be used for the
guest users.
. The user name and real name make little difference but it is
advisable to use something like "GUEST USER" for both. Whenever a
guest user logs off, the real name is copied over the user name.
. It is probably best to use "Any Street", "Any City, Any State"
type things for the location user information.
. You MUST use "HELLO" as the account password.
===========================================================================
January, 1993 (Preliminary) Page 49
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
2. Using the user log editor, edit the account you just created. Change
the guest user telephone number to the system's number as defined in
the system configuration. The guest user will be given whatever
access this account is configured for. Adjust it in any manner you
wish.
3. Enable the guest user function and entering the user ID number of the
account you just created in this field.
4. You may optionally create a text file called guest.msg inside your
DFILES directory stating any information guest users should know (see
the description of this file for more information).
L. The system operator is:
This setting causes adjustments in certain messages on the system to
correspond to the gender of the system operator.
M. Store bad logon information:
This setting defines whether specific bad logon information is stored in
the sysop.log file. When active, the incorrect password and/or telephone
number is stored whenever a user fails to enter valid information when
logging on.
N. Logon uses Auto-Message:
This setting defines whether T.A.G. will display the Auto-Message while
a user is logging onto the system.
O. Logon takes phone off-hook:
This setting determines whether T.A.G. will automatically take the phone
off-hook when a user logs onto the system locally.
P. Generic logon information:
This setting defines whether T.A.G. should present itself in a generic
format non-specific to any country. Normally when this mode is active,
the following option should also be disabled. When in generic mode the
following changes occur:
1. Telephone numbers are no longer checked for format.
2. Postal codes are no longer checked for format.
3. In the user list command (Pkey="L"), the search for telephone area
codes is not available.
R. Logon asks for phone number:
This setting determines whether users are asked to enter the last 4
digits of their telephone number when logging onto the system. Using
this option provides an additional level of security and often will
cause users who enter bad information to have a great deal of trouble
logging back onto the system.
===========================================================================
January, 1993 (Preliminary) Page 50
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
S. Alert beeps only chat on:
This setting determines whether the alert signal on the local system
will only sound when the sysop is available to chat. When disabled, the
alert signal will sound is all cases, even if the effected user logs
onto the system at five in the morning!
T. Auto chat buffer open:
This setting determines whether the chat buffer will automatically open
whether entering the chat mode.
U. Scan/File find in SysOp log:
This setting determines whether a user's file scans and file text
searches are reported in the SysOp log. Enabling this feature makes it
possible to determine whether a user made a reasonable effort to avoid
uploading a duplicate file.
V. Direct screen writes:
This setting determines whether T.A.G. will write directly to the screen
rather than using DOS BIOS calls. Enabling this feature causes much
faster screen output. However, certain environments, such as DoubleDOS,
insist that direct screen writes be turned off.
W. Screen snow checking:
This setting is only meaningful when direct screen writes (discussed in
the previous paragraph) are enabled. When this setting is enabled,
direct writes are synchronized to eliminate snow at the cost of a
marginal loss of speed.
X. Try to use EMS for overlays:
This setting determines whether T.A.G. will attempt to store overlay
files in EMS memory, thereby considerably enhancing system performance.
If you are using an EMS-based RAM disk, make sure that the command in
the CONFIG.SYS file that loads the RAM disk driver leaves some
unallocated EMS memory for T.A.G.'s overlay module which requires
approximately 380K.
Y. Instant logon key:
This setting determines whether a user at the keyboard can bypass
password security for a faster logon. When enabled, the user can
instantly log on by holding down either Shift key after entering his/her
user name or ID number at the appropriate prompt.
Z. Local Security:
This setting disables or enables most of the function keys available to
the Sysop. The only function keys that are active when Local Security is
enabled are:
F4 - Toggle Sysop Window
Shift-F4 - Turn Off Sysop Window
F5 - Hang up
Shift-F5 - Hang up with message
F10 - Chat
Shift-F10 - Sysop Next
===========================================================================
January, 1993 (Preliminary) Page 51
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
1. Show available upload space:
This setting determines whether the Free Space available on the upload
drive should be displayed to the user prior to uploading.
2. Show GIF resolution:
This setting determines whether the resolution, as read from the actual
GIF file, is appended to the front of the files description in all
listings. Note: The resolution does not become "part of" the
description, it is only appended upon display of the description.
3. Force scan before upload:
This setting defines whether the option to scan for duplicates as part
of the upload process is enabled or disabled. If enabled, the upload
filename will be converted to a more general filemask by an
"intelligent" routine and be used to scan all file sections to which the
user has access for possible duplicate filenames. Unless otherwise
restricted (by the "C" special flag), the user has the option of
aborting the scan or allowing it to continue. If duplicates are found,
the duplicate filename, size, description and file section are displayed
and the user is given the choice to proceed anyway or to cancel the
upload. If disabled, only the current section is scanned for an exact
filename match.
4. Local logon SysOp window:
If this setting is enabled, the SysOp window is displayed during a local
logon session; if disabled, the window is turned off during local logon
sessions. (Disabling this feature does not preclude the SysOp from
pressing the F4 key to display the window, if desired.)
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.
===========================================================================
January, 1993 (Preliminary) Page 52
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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.
@. Failed logon message sent to:
This field indicates the user number that a user who has failed a logon
is allowed to send a message to. If this number is zero, this feature
is disabled, and users are not asked if they want to send a message at
the end of a failed logon.
#. Wait screen messages waiting:
This field indicates the user number that the wait screen "messages
waiting" uses to count the actual number of messages waiting. If this
number is zero, the feature is disabled.
$. Auto ANSI detection at logon:
This field enables or disables T.A.G.'s auto ANSI detect at logon.
===========================================================================
January, 1993 (Preliminary) Page 53
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/======================\
< Range setting commands >
\======================/
/================\
< Time limitations >
\================/
This defines user time limitation settings. A value representing the number
of minutes allowed on-line may be defined for each security level (SL).
This time represents either time per call or the total time per day
depending on the setting of the "F" option on the main system configuration
screen. See "Using Range Setting Commands" for basic usage of range
commands.
/=====================\
< Calls allowed per day >
\=====================/
This defines, for each SL, the number of calls that are allowed per day.
See "Using Range Setting Commands" for basic usage of range commands.
/=====================================\
< Upload/download number of files ratio >
\=====================================/
This defines, for each download security level (DSL), the number of files
that can be downloaded per one file uploaded to the system. For example, a
setting of 10 will give users with that DSL a 1 to 10 file upload ratio.
This means, for each file uploaded, ten files may be downloaded. See "Using
Range Setting Commands" for basic usage of range commands.
/=============================\
< Upload/download K-bytes ratio >
\=============================/
This defines, for each DSL, the number of K-bytes (1,024 bytes) that can be
downloaded per one K-byte uploaded to the system. For example, a setting of
15 will give users with that DSL a 1 to 15 K-byte upload ratio. This means
for every 1k uploaded, 15k may be downloaded. See "Using Range Setting
Commands" for basic usage of range commands.
/===============\
< Post/call ratio >
\===============/
This defines, for each SL, the number of tenths of calls a user may make to
the system per public messages posted by that user. For example, a setting
of 30 will give users with that SL a 1 post to 30 tenths (30/10) of a call
ratio. This means for every public message posted, they are allowed 3 calls
before the post/call AR flag is again removed from their account. See
"Using Range Setting Commands" for basic usage of range commands.
===========================================================================
January, 1993 (Preliminary) Page 54
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/============================\
< Using Range Setting Commands >
\============================/
"Range Sets" establish limitations/ratios for each security level. For each
range setting command, every Security Level has an associated value.
Since 255 values are difficult to display at once, 0-127 are displayed on
one page, and 128-255 are displayed on another page. The "Toggle" command
is used to switch between the two pages, while the "Set" command allows the
setting of individual values.
The following is an example of a typical range setting display screen.
Editing: Post/call ratio (# 1/10's of calls per post to have AR flag)
0 :100 19 :100 38 :100 57 :100 76 :100 95 :100 114:100
1 :100 20 :100 39 :100 58 :100 77 :100 96 :100 115:100
2 :100 21 :100 40 :100 59 :100 78 :100 97 :100 116:100
3 :100 22 :100 41 :100 60 :100 79 :100 98 :100 117:100
4 :100 23 :100 42 :100 61 :100 80 :100 99 :100 118:100
5 :100 24 :100 43 :100 62 :100 81 :100 100:100 119:100
6 :100 25 :100 44 :100 63 :100 82 :100 101:100 120:100
7 :100 26 :100 45 :100 64 :100 83 :100 102:100 121:100
8 :100 27 :100 46 :100 65 :100 84 :100 103:100 122:100
9 :100 28 :100 47 :100 66 :100 85 :100 104:100 123:100
10 :100 29 :100 48 :100 67 :100 86 :100 105:100 124:100
11 :100 30 :100 49 :100 68 :100 87 :100 106:100 125:100
12 :100 31 :100 50 :100 69 :100 88 :100 107:100 126:100
13 :100 32 :100 51 :100 70 :100 89 :100 108:100 127:100
14 :100 33 :100 52 :100 71 :100 90 :100 109:100 128:100
15 :100 34 :100 53 :100 72 :100 91 :100 110:100 129:100
16 :100 35 :100 54 :100 73 :100 92 :100 111:100 130:100
17 :100 36 :100 55 :100 74 :100 93 :100 112:100 131:100
18 :100 37 :100 56 :100 75 :100 94 :100 113:100 132:100
Range setting: (S:et,T:oggle,Q:uit):
Set
This command allows you to change one or more values on the table. You
will be prompted for a starting and ending range, and then the value to
set the specified entry(s) to. To set a single entry, simply enter the
same value for both the starting and ending range.
Toggle
This command switches the display between the table displaying values
for entries 0-132 or values for entries 133-255.
===========================================================================
January, 1993 (Preliminary) Page 55
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===============\
< The User Editor >
\===============/
The User Editor is provided to allow the SysOp or his/her designates to
modify a user's record on the system. This command can be accessed through
a menu command (//UEDIT - see the menu documentation for further details on
setting up this command), from the wait screen or from any menu within the
BBS through the Control-Q HotKey.
Another method of accessing the user editor is through the use of the
Control-U command. Control-U is available from any menu the following
limited places:
1. When reading a public or private mail message, you will be placed at
the user record of the author of that message, if found.
2. When editing a file, browsing a file or validating a file in the file
system, you will be placed at the user record of the owner (uploader)
of that file.
The SL and AR flags necessary to gain access to the Control-U command and
whether password protection exists are set in the System configuration,
single value security settings section. If you set the Control-U feature
in the SysOp configuration to function without password protection, access
to the user editor can be VERY fast. If you elect to have this command
password protected, password #1 is used.
/=====================================\
< Table of Special Flags (SF) for Users >
\=====================================/
A : Auto private mail delete:
This flag forces a user to delete or reply (thereby causing an
automatic delete) any private mail messages as they read them.
B : No post/call ratio:
This flag overrides and inhibits system checking of any post/call
ratios.
* C : Cannot abort upload scan:
This flag prevents a user from aborting the automatic, forced scan
for possible duplicate filenames prior to uploading.
D : Cannot post anonymous:
This flag prevents a user from posting any public or private
anonymous messages.
* E : Cannot add to BBS list:
This flag prevents a user from adding a system to the "Other BBS
listing".
===========================================================================
January, 1993 (Preliminary) Page 56
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
F : Cannot page sysop:
This flag prevents a user from paging the SysOp; it simply reports
that the SysOp is not around regardless of the setting of the
"SysOp available" status.
G : No download limit:
This flag overrides and inhibits system checking of any download
ratios.
H : Cannot post public mail:
This flag prevents a user from posting any public messages.
I : Cannot send private mail:
This flag prevents a user from sending private mail to any user
below CoSysOp level.
* J : Not allowed to vote:
This flag prevents a user from voting on any of the questions.
Users be allowed to look, but not participate.
K : Allowed only one call per day:
This flag limits a user to only one call per day.
* L : Public mail is marked not validated:
This flag causes any public messages posted by the user to be
marked <not-validated> until a user with SubOp access to the
section reads and validates the message.
M : Protect from deletion:
This flag prevents a user from being deleted from the user log.
N : Ignore file points:
This flag overrides and inhibits system checking of any file point
restrictions.
O : Uploaded files not validated immediately:
This flag indicates when credit is given to a user for an upload.
When set, upload credit is delayed until after the file has been
validated; when not set, upload credit is given immediately.
P : [PAUSE] active:
This flag indicates whether the [PAUSE] string is displayed after
each page of data is displayed.
Q : ANSI active:
This flag indicates whether ANSI graphics are active.
R : Color active:
This flag indicates whether color ANSI graphics are active. If
ANSI graphics are disabled, this flag has no effect.
===========================================================================
January, 1993 (Preliminary) Page 57
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
S : Onekey input:
This flag indicates whether the onekey (immediate execution of
commands) input mode is active. When disabled, users must hit
return to accept commands.
T : Alert active:
This flag indicates whether the system should alert you when this
user logs on.
U : User is male:
This flag indicates whether the user is of the male gender.
V : Mailbox is closed:
This flag indicates whether the user's mail box is closed to all
mail from other users below CoSysOp access level.
W : Tabs active:
This flag indicates whether VT-100 type tabs should be used
whenever possible to increase display speed.
X : CLS character used:
This flag indicates whether clear screen codes are used on the
system.
* = New users start with these restrictions in the standard start up
system.
/===========================================\
< Table of Configuration Flags (CF) for users >
\===========================================/
At the present time only one configuration flag is present, the A flag.
A : Uses custom menus:
This flag determines if a user who has ANSI enabled will have
custom (*.MSG/.CLR) menus or T.A.G. generated menus. If enabled,
the user will see custom menus, if present; if disabled, the user
will see T.A.G.'s menus even if custom menus are present.
/========================\
< Adjusting Numeric Values >
\========================/
When changing numeric values in the user editor, a special feature is
available to ease modification of existing values. A "++" preceding a
number causes it to be added it to the existing value; a "--" preceding a
number causes subtraction from the existing value.
For example: If the user has download 250k. Entering "--50" for download
K-byte modification would subtract 50k from the 250k leaving 200k in the
user record. These numeric modifications may be used in mass changes with
the (/)Change all tagged option. You could, for example, give a list of
users a download bonus all at once or add 10 to the SL of all tagged users.
===========================================================================
January, 1993 (Preliminary) Page 58
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==========================\
< Built in Security Features >
\==========================/
Users with access to the user editor are not permitted to change any other
user with a SL equal to or greater than their own (with the exception of SL
255, which has no restrictions whatsoever).
Therefore, the following protections exist:
1. A user may not increase the SL or DSL of another user to a setting equal
to or greater than his/her own.
2. A user may not change an AR flag of another user unless if s/he has that
AR flag.
Attempts to violate these rules are noted in the SysOp log to keep the
SysOp informed as to what their remote SysOps are doing.
When a user's record is changed, the user number of the user responsible
for making the change is stored in the changed user's record. This makes
it possible for the SysOp to track changes to users' records.
/=================================\
< Extended User Listing Description >
\=================================/
Which list mode:
(S)hort, (N)ormal, (I)nformational, (E)xtended, <CR>Default: E
User#4 Rec#4 Status:Normal SL:100 DSL:100
User name:JOE USER AR:-BC-E--------N-P--S-------
Real name:JOHN DOE SF:------G-----M--P--S-U--X
Address :999 Somewhere Street Sex / B-Day:M 41 (09/17/51)
City / State :SOMEPLACE, MI Postal code:48000
Computer type:IBM AT Phone # (1):313-123-4567
Last called :04:34:18 pm Sat Jan 23, 1993 Phone # (2):
SysOp note : Password :"TAG!"
Call spread :254,58,1,14,114,48,38,3,37,0,46,33,4,17,6
Screen size :80x23 Forward mail :Disabled Highest baud :2400 bps
Total calls :25 Total time on :407 Time on today :48 mins
Calls today :1 Illegal logons:0 Adjusted time :0 mins
Public posts :0 Private posts :3 Feedback to SysOp:6
Help level :3 PostCall ratio:1 post / 10.0 calls Points :0
External edit:Ask Downloads :23 files - 2506k Debits :0
First logon :03/25/92 Uploads :5 files - 157k Credits:0
Date expires :12/31/94 UL/DL ratio :None (special flag) TimeBnk:120
Flags: CLS:On ANSI:Off Color:Off Pause:On Custom :On MailBox:Open
DND:Off Tabs:Off Alert:Off Input:OneKey Msg CLS:Off
===========================================================================
January, 1993 (Preliminary) Page 59
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
User#:
This field is the user's ID number. If it is zero, the user has been
deleted. If it is different than the record number, the user is locked
out of the system.
Rec#:
This field is the user's actual record number in the user log.
Status:
This field indicates the user's status on the system. Possible values
are "Normal", "Deleted", and "Locked out".
SL:
This field indicates the user's security level on the system.
DSL:
This field indicates the user's download security level on the system.
<<TAGGED>>:
This flag indicates whether the user is tagged for mass user options. A
user can be tagged with the <SPACE BAR> on the main user menu or through
various commands at the options menu.
AR:
This field contains the user's AR flag settings. Letters that appear
indicate the AR flag is set; dashes indicate they are not set.
SF:
This field contains the user's special flag settings. See the special
restrictions table near the beginning of this section for more
information.
SysOp note:
This field is a place to keep comments about users. Uses may include
noting what system a user is running, problems you have warned them
about, etc.
Call spread:
This field displays a list of the number of days between the last 15
calls the user has made (listed from most recent call to oldest call). A
zero entry means the user called again on the same day. Values over 254
days are set to 254.
Example:
Call spread: 2,3,0,2,1,3,0,1,3,2,10,13,7,2,1
Last called on: 4:55:14 am Fri Aug 28, 1987
This user's last few calls were (most recent first):
August 28 -(2)-> August 26 -(3)-> August 23 -(0)-> August 23 etc.
===========================================================================
January, 1993 (Preliminary) Page 60
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Mail waiting:
This field indicates the number of private messages a user has waiting.
MSG base SubOp:
This field indicates message section number(s) where this user has SubOp
access. SubOps may move or delete any messages in the sections listed.
Points:
This field indicates the number of file points the user has accumulated.
TimeBank:
This field indicates how many minutes the user has in the Time Bank. It
is of no value unless you are actually using the Time Bank feature.
Starting menu:
<NOT SUPPORTED>
Last <MSG/DL> base:
These fields indicate the last message and file sections accessed by the
user during the previous call. When the user logs back on, s/he will
start in these sections. The system verifies that the user still has
access to the message and file sections and resets to section "1" if the
access check fails. Since a security failure forces a user into section
#1, you are advised to insure it does not contain messages or files that
should be not be available to normal users.
Alert:
This field indicates whether the system will alert the local SysOp when
this user logs onto the system again.
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.
DND (Do not disturb):
Multi-user option which indicates whether the user would like to be
bothered by other "nodes".
===========================================================================
January, 1993 (Preliminary) Page 61
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===============================\
< Normal User Listing Description >
\===============================/
Which list mode:
(S)hort, (N)ormal, (I)nformational, (E)xtended, <CR>Default: N
User#1 Rec#1 Status:Normal SL:255 DSL:255 <<TAGGED>>
User name:JOE SYSOP AR:ABCDEFGHIJKLMNOPQRSTUVWXYZ
Real name:JOSEPH SYSOP SF:------G-----M--P----U--X
Address :123 AnyStreet Sex / B-Day:Male - 01/01/54
City / State :YourTown, US Postal Code:54321
Computer type:IBM AT Phone # :111-555-1212
SysOp note : Last on :06/05/90 23:36:30
Call records : TC=20 TT=14756 CT=0 IL=0
Mail records : Pub=155 Priv=788 Fback=1 Wait=2
File records : DL=4-108k UL=1-200k Pts=0
User edit (?=Help):
See the extended user list for a detailed description of the unusual
fields.
/==================================\
< Abbreviations used in user listing >
\==================================/
SF The user's special flags.
B-Day The user's birthday.
TC The user's total calls.
TT The total time the user has been on the system.
CT The number of calls the user made on the last call date.
IL The number of illegal logons that have been made to this account
since the last time the user logged on.
Pub The number of public posts the user has made.
Priv The number of private messages the user has sent.
Fback The number of messages the user has sent to any SysOp.
Wait The number of private messages the user has waiting.
Pts The number of file points the user currently has.
===========================================================================
January, 1993 (Preliminary) Page 62
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============================\
< Short User Listing Description >
\==============================/
Which list mode:
(S)hort, (N)ormal, (I)nformational, (E)xtended, <CR>Default: S
User#1 Rec#1 Status:Normal SL:255 DSL:255 <<TAGGED>>
User name:JOE SYSOP AR:ABCDEFGHIJKLMNOPQRSTUVWXYZ
Real name:JOSEPH SYSOP SF:------G-----M--P----U--X
See the extended user listing for a description of the usual fields.
/======================================\
< Informational User Listing Description >
\======================================/
The informational user listing lists the extra fields provided to maintain
information for each user, along with standard fields. These can be
optional or required at logon, or changed through the use of the user
editor, or by defining the appropriate Pkey and Pdata to create menu
commands (See the Menu documentation, Pkey "D").
Which list mode:
(S)hort, (N)ormal, (I)nformational, (E)xtended, <CR>Default: I
User name:JOE SYSOP User number :1
Real name:JOHN SYSOP Sex/Age:M 38 (07/17/54)
Address :9876 Anystreet Highest baud :9600 bps
City / State :Someplace, MI Postal code :48000
Computer type:IBM AT Phone # (1) :313-555-0000
Screen size :80x24 Extern edit :Ask Phone # (2) :313-777-0000
Help level :Expert Forward mail :Disabled Extra phone :
Extra char 1 :~ Extra num 1 :65535 Time bank :600 mins
Extra char 2 :~ Extra num 2 :65535 Colors :Disabled
Extra char 3 :~ Extra num 3 :65535 Extra date 1 :01/01/97
Extra char 4 :~ Extra num 4 :65535 Extra date 2 :01/01/97
BBS Name :Great T.A.G. BBS
BBS Software :T.A.G.!
Extra str 3 :
Flags: CLS:On ANSI:Off Color:Off Pause:On Custom :Off MailBox:Open
DND:On Tabs:Off Alert:Off Input:OneKey Msg CLS:On
The fields are completely configurable by the SysOp using the programmable
string system in combination with the configuration new user logon
described else where in this document.
Note:
On some date files, there may be a superscript number 2 displayed. It
indicates the field has not been set.
===========================================================================
January, 1993 (Preliminary) Page 63
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Field Descriptions:
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.
===========================================================================
January, 1993 (Preliminary) Page 64
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================================\
< User Editor Main Command Descriptions >
\=====================================/
(Space)Toggle tag status of this user (=)Oops (load old data)
([)Back one user (])Forward one user (/)Change all tagged
({)Search backward (})Search forward (.)List all tagged
(;)Relist user (-)Clear for reentry (\)New user config
(A)ddress (B)aud rate (maximum) (C)ity & State
(D)ownload SL (E)Special flags (F)AR flags
(G)Birthday (H)elp level (I)Last boards
(J)Change user name (K)SysOp note (L)aston date
(M)ailbox (N)ew default list (O)ptions menu
(P)hone number (Q)uit editor (R)eal name
(S)ecurity level (T)ype of computer (U)Jump to user
(V)alidate user (W)Undelete user (X)Screen size
(Y)Message base SubOp (Z)ip code (0)Mail posts/waiting
(1)Number of downloads (2)K-bytes downloaded (3)Number of uploads
(4)K-bytes uploaded (5)Number of calls (6)Total Time on system
(7)Calls today (8)Time on today (9)Misc options
(!)Password (#)User number ($)Money (credit,debit)
(*)Delete user (')Change colors (^)File points
(@)Time bank (%)User history (+)Configuration flags
(Space) Toggle tag status of this user:
This command tags or untags the current user.
(=) Oops (load old data):
This command reloads the original user data if you should make a mistake
editing a user. Once you leave the user in question, the changes are
written to the disk and cannot be recovered.
([) Back one user:
This command moves back one record number in the user log.
(]) Forward one user:
This command moves forward one record number in the user log.
(/) Change all tagged:
This command changes an item on all tagged users. You can mass-delete
users with this also. Please be careful when using this option. The
following commands may be used on a group of users (see the appropriate
user editor main command description for information on the unusual
commands):
===========================================================================
January, 1993 (Preliminary) Page 65
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
(A)ddress (B)aud rate (maximum) (C)ity & State
(D)ownload SL (E)Special flags (F)AR flags
(G)Birthday (H)elp level (I)Last boards
(K)Sysop note (L)aston date (M)ailbox
(P)hone number (Q)uit (S)ecurity level
(T)ype of computer (V)alidate user (W)Undelete user
(X)Screen size (Z)ip code (0)Mail posts/waiting
(1)Number of downloads (2)K-bytes downloaded (3)Number of uploads
(4)K-bytes uploaded (5)Number of calls (6)Total Time on system
(7)Calls today (8)Time on today (9)Illegal logons
(#)User number ($)Money (credit,debit) (*)Delete user
(-)Clear for reentry (^)File points (@)Time bank
({) Search backward:
This command searches backward in the user log (lower user record
numbers) for the next user matching the defined (O)ptions.
(}) Search forward:
This command searches forward in the user log (higher user record
numbers) for the next user matching the defined (O)ptions.
(.) List all tagged:
This command lists all tagged users using the current default listing
level.
(;) Relist user:
This command will relist the current user prompting you whether for
short, normal, extended, or informational mode.
(-) Clear for reentry:
This command clears a user field for reentry when the user logs onto the
system again. For example: If their real name is obviously fake, clear
it and the system will ask them for their real name again when they
logon. If the telephone number is cleared, the user will not have to
enter in order to logon. The following fields may be cleared for
reentry:
(A)ddress (B)aud rate (maximum) (C)ity & State
(G)Birthday (P)hone number
(R)eal name (T)ype of computer (Z)ip code
(\) New user config:
This command jumps to the new user configuration record. The following
fields are copied from this record to the new user when they logon: SL,
DSL, AR, Help level, Sysop note, Special flags, MSG base SubOp, Starting
menu, Last MSG base, Last DL base, Downloads & Uploads (both number and
k-bytes), CLS, Tabs, Pause, Mail box closed (forwarding NOT copied),
File validation delay, Input, Color settings, MSG & DL scan settings,
Defined colors, and File points.
(E) Special flags:
This command allows modification of the special flags defined on the
user. See the table to special flags at the beginning of this section
for more information.
===========================================================================
January, 1993 (Preliminary) Page 66
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
(F) AR flags:
This command allows modification of the AR flags on the current user.
The (*)Toggle all option of this command will flip all AR flags to their
opposite setting.
(I) Last boards:
This command allows modification to the last message and download
section accessed by the user. NOTE: If you wish new users to start at a
specific message or file section, use this command to change the new
user configuration record.
(L) Laston date:
This command allows modification of the date and time of the user's last
call.
(M) Mailbox:
This command allows modification of the status of a user's mailbox.
Possible settings include "Open", "Closed", and "Forwarded".
(N) New default list:
This command changes the default listing mode for users. Autolist mode
is the normal setting, where a users record is (re)displayed after each
change. An option exists to disable the auto-list mode in case you have
a great number of changes.
Which list mode:
(S)hort, (N)ormal, (E)xtended, (I)nformational, <CR>Default: N
Autolist mode (Y/N)? No
(O) Options Menu
See the section "User Editor - Options Menu"
(Q) Quit:
This command exits the user editor. Note that any tags on users will be
lost when you exit the editor.
(U) Jump to user:
This command allows you to jump immediately to any user (except the new
user configuration record). Using this command you may enter a user ID
number, a complete user name, or a partial user name. In the case of a
partial name, T.A.G. will search for a user containing the entered
string in their user name. When one is found, you will be given the
option to jump to that user, continue searching for the next user, or
abort the search all together.
(V) Validate user:
This command validates the current user according to the access levels
defined in the validation configuration. (See Access Validation Editor)
(W) Undelete user:
This command will undelete an originally deleted user. Please note that
this command will NOT recover lost private mail, macros, or voting
records.
===========================================================================
January, 1993 (Preliminary) Page 67
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
(0) Mail posts/waiting:
This command allows you to change the following mail statistics:
(1) Private posts
(2) Public Posts
(3) Feedback
(4) Mail waiting
(!) Password:
This command allows you change the password needed to log onto the
system. This option is NOT available unless the user attempting to make
the change has a SL greater than or equal to the "See Passwords" level
specified in the system configuration.
(#) User number:
This option allows the SysOp to change the user number of the current
user record. When a user number is the same as the record number, the
user has the status of "NORMAL". When a user number is a non-zero
number different from the record number, the user number has the status
of "LOCKED OUT" (see lockout.msg). When a user number is zero, the user
has the status of "DELETED".
WARNING:
Do NOT delete users by changing their user number to zero. Doing so
will leave all other items that were controlled by that user on the
system (wasting space). The information will also probably conflict
with the next user who uses that record.
($) Money (credit,debit):
This command sets the credit and debit a user has with respect to
Netmail costs. Credit represents the number of cents the user has paid
to the system for Netmail transfer. Debit represents the number of cents
the user has actually used.
(*) Delete user:
This command deletes a user and all their associated information. This
includes: Name list pointer reference, Small messages, Private mail to
or from the user, and Voting records. Public mail posted by the user is
NOT effected. Note that the system will not allow anyone to delete a
user who is not at least CoSysOp SL or a user with the "M" special flag
set.
(') Change colors:
This command allows you to change the colors defined for the current
user. The only practical use of this command is to change the default
colors in the new user configuration record.
(@) Time bank:
This command changes the number of minutes the user has in their time
bank, provided you are using the time bank on your system.
(%) User history:
This command searches through the current and previous SysOp Logs,
reporting on the user's activity.
===========================================================================
January, 1993 (Preliminary) Page 68
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
(+) Configuration flags:
This command allows modification of the configuration flags defined on
the user. See the table of configuration flags at the beginning of this
section for more information.
(|) Gender:
This option in the user editor 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.
/==========================\
< Options Menu - User Editor >
\==========================/
This section details the use of the (O) Options Menu in the User Editor.
The command is used to create tagged groups of users based on the settings
of specific fields. These groups of users can be merged with other groups
in a variety of methods with the tag options.
-=[ Search limiting options ]=-
0. General text: <<Inactive>>
1. Security level: <<Inactive>>
2. D/L security level: <<Inactive>>
3. AR flags set: <<Inactive>>
4. Special flags set: <<Inactive>>
5. User status: <<Inactive>>
6. Days since last on: <<Inactive>>
7. Number of calls: <<Inactive>>
8. User age: <<Inactive>>
9. User gender: <<Inactive>>
P. # 1/10's call/post: <<Inactive>>
K. #K-DL/1K-UL: <<Inactive>>
N. # DL's/1 UL: <<Inactive>>
<<Inactive>> fields do not effect the search in any way.
0. General text:
This option is used for matching a general text string against several
fields in the user records. Case is ignored when this field is used.
The following user fields are compared with this string for a possible
match:
User name Real name Address City/State
Zip code Computer type Phone # SysOp note
This command is very handy when you forget a user's handle but remember
some other piece information about them.
===========================================================================
January, 1993 (Preliminary) Page 69
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
1. Security level:
This option matches a range of security levels (SL's).
2. D/L security level:
This option matches a range of download security levels (DSL's).
3. AR flags set:
This option matches a user when they have the same AR flags set in their
user record as in this field. Flags which are not set in this field do
not effect the search. For example: If AR flag "A" is the only flag set
in this field, all users with AR flag "A" will match this option even if
they have other AR flags set also.
4. Special flags set:
This option matches a user when they have the same special flags set in
their user record as in this field. Flags which are not in this field
do not effect the search.
Example: "A------------" matches
"A------------",
"A-----------M", and
"ABCDEFGHIJKLM".
5. User status:
This option matches a user when they have the specified status. Normally
you only care about users with a "Normal" status.
6. Days since last on:
This option matches a range of number of days since a user's last call.
It is usually used to find users who haven't called within a given time
period (perhaps 60 days). In this case, search for users with 60 to
32000 days since their last call. No one is going to be in the user log
who has not called in 32000 days, it is just a simple upper limit.
7. Number of calls:
This option matches a range of total calls a user has made to the
system.
8. User age:
This option matches a range of user ages based on the current date and
the user's birthday.
9. User gender:
This option matches a user when they have the specified gender.
P. # 1/10's call/post:
This option matches a range of tenths of a call a user had made for
every public post. For example:
To match all users who have posted at least one message for every 2
calls they have made, you would set this to search for the range 0
though 20 (0 tenths of a call per post, to 20 tenths of a call (20
divided by 10 = 2 calls) per post).
===========================================================================
January, 1993 (Preliminary) Page 70
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
K. #K-DL/1K-UL:
This option matches a range of number of K-Bytes downloaded a user has
made for every K-Byte uploaded. For example:
To match all users who have uploaded at least as many K-Bytes as they
have download, if not more, you would set this to search for the range 0
though 1 (0 K-Bytes downloaded per K-Byte uploaded (infinity) to 1
K-Byte downloaded per K-byte uploaded (even-steven)).
N. # DL's/1 UL:
This option matches a range of number of downloads a user has made for
every upload. For example:
To match all users who have uploaded at least as many files as they have
downloaded, if not more, you would set this to search for the range 0
though 1 (0 downloads per upload (infinity) to 1 download per upload
(even-steven)).
===========================================================================
January, 1993 (Preliminary) Page 71
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================\
< Options Menu Commands >
\=====================/
Options Menu (?=Help): ?
0-9,P,K,N: Alter option specifications (auto activation)
SPACE: Toggle user tag status by number
C:hange an option's state E:mpty tag table
I:nvert tag table L:ist current options
Q:uit to previous menu S:how tagged users
T:ag operations U:sers matching options
0-9,P,K,N: Alter option specifications (auto activation):
These commands allow you to modify the existing search options. If a
chosen item is currently <<Inactive>>, it will be activated
automatically.
SPACE: Toggle user tag status by number:
This command allows you to toggle the <<TAGGED>> status of any user
by simply entering their user record number.
C:hange an option's state:
This command allows you to toggle a search option between active and
<<Inactive>> state.
E:mpty tag table:
This command clears the current tag table. No users will be tagged
after using this command.
I:nvert tag table:
This command reverses the tag status of all users. All tagged users
become untagged, all previously untagged users become tagged.
S:how tagged users:
This command displays the names and user numbers of all current
tagged users.
T:ag operations:
This command performs several comparison operations on the user
matching the current options and the users currently tagged. The
following commands are available:
Options Menu (?=Help):
===========================================================================
January, 1993 (Preliminary) Page 72
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==========================\
< Tagged user set operations >
\==========================/
Set A: Currently tagged users
Set B: Users match current options
Logical operator:
1. Union Combined set of users from set A and set B.
2. Intersection Set of common users found in set A and set B.
3. Difference Set of users found in set A that are not also found
in set B.
4. Divergence Set of users in set A that do not appear in set B,
and also those users that appear in set B but not
in set A.
1. Union:
This option tags all users who are not already tagged and now
match the options defined. More specifically:
1. If a user is tagged and matches the options they remain tagged.
2. If a user is tagged but does not match the options then they
remain tagged.
3. If a user is untagged but matches the options, then they become
tagged.
4. If a user is untagged and does not match the options, then they
remain untagged.
2. Intersection:
This option tags all users who users are currently tagged and
match the current options. Those users which were not tagged or
do not match the options become untagged. More specifically:
1. If a user is tagged and matches the options they remain tagged.
2. If a user is tagged but does not match the options then they
become untagged.
3. If a user is untagged but matches the options, then they remain
untagged.
4. If a user is untagged and does not match the options, then they
remain untagged.
===========================================================================
January, 1993 (Preliminary) Page 73
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
3. Difference:
This option tags all users who are currently tagged and do not
match the current options. Those users which were not tagged or
now match the options become untagged. More specifically:
1. If a user is tagged and matches the options they become
untagged.
2. If a user is tagged but does not match the options then they
remain tagged.
3. If a user is untagged but matches the options, then they remain
untagged.
4. If a user is untagged and does not match the options, then they
remain untagged.
4. Divergence:
This option tags all users who are not currently tagged and do not
match the current options. Those users which were tagged or now
match the options become untagged. More specifically:
1. If a user is tagged and matches the options they become
untagged.
2. If a user is tagged but does not match the options then they
remain tagged.
3. If a user is untagged but matches the options, then they become
tagged.
4. If a user is untagged and does not match the options, then they
remain untagged.
===========================================================================
January, 1993 (Preliminary) Page 74
T.A.G. BBS Version 2.6d Main 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 Base
J : User Name K : Sysop Note L : Laston 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
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
===========================================================================
January, 1993 (Preliminary) Page 75
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/================\
< 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 : AltPath B : BoardName C : LastCaller
D : Current date E : ErrorsToday F : Unused
G : DfilesPath H : NusersToday I : MailAddress
J : Unused K : Unused L : Unused
M : DictPath N : CallerNum O : Unused
P : BoardPhone Q : Unused R : Unused
S : SysopName T : Current Time U : multiuserpath
V : TAGVersion W : Unused X : Users
Y : Unused Z : ChatPW
1 : MaxBdNum 2 : MaxBuNum 3 : UlKtoday
4 : DlKtoday 5 : CallsToday 6 : MsgPostToday
7 : EmailToday 8 : FbackToday 9 : UlToday
0 : DlToday # : MU Node Number % : PercentActive
! : 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.
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_".
===========================================================================
January, 1993 (Preliminary) Page 76
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==================\
< 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 configure 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 "?".
===========================================================================
January, 1993 (Preliminary) Page 77
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/========================\
< The Message Board Editor >
\========================/
Acc Post Messages
### Style Type Description SL/AR SL/AR Grp Min Max ANSI Anon Hand
--- ----- ------ ---------------------- ----- ----- --- --- ---- ---- ---- ----
0 Local Fido EMAIL 1/@ 1/@ 0 1 255 Yes No Forc
1 Local Fido System Notices 100/@ 10/@ 0 1 50 Yes No Forc
2 Local Fido General Messages 10/@ 10/@ 0 1 75 Yes No Forc
3 Echo RA 149 [Echo] T.A.G. 10/@ 10/E 0 1 5000 No No No
4 Echo RA 38 [Echo] T.A.G. Multi-No 10/@ 10/E 0 1 5000 No No No
5 Echo RA 121 [Echo] T.A.G. Doors 10/@ 10/E 0 1 5000 No No No
6 Net Fido [MAIL] Netmail 255/Z 255/Z 0 1 5000 No No No
MSG Boards: (D:elete,I:nsert,M:odify,P:osition,Q:uit) [Q]:
Section number to start editing (0-37):
/==================\
< Email Message Area >
\==================/
Section : 0
A. Name : EMAIL
B. Path : L:\MSGS\EMAIL\
C. Format : Style = Local Type = Fido
D. Messages : Min = 1 Max = 255
E. Read menu : 0
F. Post file : EMAIL
G. Start quote:
H. End quote:
1. Access : General SL=1/AR=@ Post SL=1/AR=@ Group number=0
2. Password : ""
3. SubOps : None
4. PrivateMsgs: Unrestricted
5. Handles : Force
6. Anonymous : No
7. Allow ANSI : Yes
8. Mail Flags :
===========================================================================
January, 1993 (Preliminary) Page 78
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/============\
< RA Echo Area >
\============/
Section : 20
A. Name : [Echo] T.A.G.
B. Path : T:\ECHOS\
C. Format : Style = Echo Type = RA (Board #149)
D. Messages : Min = 1 Max = 5000
E. Read menu : 0
F. Post file :
G. Start quote:
H. End quote:
I. Address : 1:2410/116@FIDONET.ORG
J. EchoTag : TAG
K. Origin :
1. Access : General SL=10/AR=@ Post SL=10/AR=E Group number=0
2. Password : ""
3. SubOps : None
4. PrivateMsgs: Unrestricted
5. Handles : No
6. Anonymous : No
7. Allow ANSI : No
8. Mail Flags :
/====================\
< Netmail Message Area >
\====================/
Section : 36
A. Name : [MAIL] Netmail
B. Path : L:\MSGS\NETMAIL\
C. Format : Style = Net Type = Fido
D. Messages : Min = 1 Max = 5000
E. Read menu : 0
F. Post file :
G. Start quote: ** Quoting @F to @T on @D **
H. End quote:
I. Address : 1:2410/116@FIDONET.ORG
K. Origin :
1. Access : General SL=255/AR=Z Post SL=255/AR=Z Group number=0
2. Password : ""
3. SubOps : None
4. PrivateMsgs: Unrestricted
5. Handles : No
6. Anonymous : No
7. Allow ANSI : No
8. Mail Flags : Private Local
===========================================================================
January, 1993 (Preliminary) Page 79
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===========================\
< Message Board Editor Fields >
\===========================/
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.
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.
===========================================================================
January, 1993 (Preliminary) Page 80
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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 (after T.A.G. appends the full address) 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).
===========================================================================
January, 1993 (Preliminary) Page 81
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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 messages.
/==============\
< Spell Checking >
\==============/
The message system 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, TAGW????.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.
===========================================================================
January, 1993 (Preliminary) Page 82
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===================\
< Message/File Groups >
\===================/
A message/file section grouping system 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.
===========================================================================
January, 1993 (Preliminary) Page 83
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================\
< The File Board Editor >
\=====================/
NN Section Name DSL AR Password Download path name
== ========================== === == ======== ===================================
0 Sysop 255 @ C:\BBS\SYSOP\
1 Miscellaneous Files 10 @ C:\BBS\MISC\
2 Communication Files 30 @ C:\BBS\COMMUN\
3 Games 30 @ C:\BBS\GAMES\
4 Utilities 30 @ C:\BBS\UTIL\
..
..
9 PC Board Online Games 30 @ C:\BBS\PCBOARDS\
DL Boards: (D:elete,I:nsert,M:odify,P:osition,T:oggle,Q:uit): M
Section number to start editing (1-9): 1
Section : 1
1. Name : Miscellaneous Files
2. File name : [@]MISC
3. DL Path Name : C:\BBS\MISC\
4. UL Path Name : C:\BBS\MISC\
5. Access : DSL=10/AR=@
6. Password : ""
7. Group number : 1
8. See names DSL : 240
9. No ratio : Off
A. CD ROM drive : No
DL Board Edit: (1-9,A,[,],B,J,T,Q,?): Q
Section:
This field holds the number of the file section being edited.
1. Name:
This field contains the section name for the file section that
appears in the menu prompt. Color codes [Ctrl-P #] are allowed.
2. [@]File name:
This field contains the file name where the files available for
download are stored. These files normally appear in the download
directory of the section and have an extension of ".DIR". If the
File name is preceded by the @ sign, the ".DIR" file will be placed
in the DFILES directory. This effectively supports CD-ROM drives.
3. DL Path Name:
This field contains the download path name for the section. The file
list and files for download go in this directory.
===========================================================================
January, 1993 (Preliminary) Page 84
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
4. UL Path Name:
This field contain the upload path name for the section. If the
upload path name is different from the download path name, the file
list file name of the upload directory is "FILES.DIR".
5. Access:
This field indicates the DSL and AR required to access the file
section.
6. Password:
This field indicates the password needed to download file from a
section. Scanning for a file mask, searching for a description, and
listing new files will list files in a section with a password
without having to enter it.
7. Group number:
This field indicates which group the file board belongs to.
8. See names DSL:
This field indicates the DSL needed to see the name of the users who
upload each file in the section.
9. No ratio:
This flag determines whether files downloaded from the section are
charged to the user's upload/download ratio or not.
A. CD ROM drive:
This flag indicates if the directory is on a CD ROM drive. T.A.G.
uses this field, in conjunction with the "Temporary Download
Directory" in the system config to copy files from the CD ROM to the
local directory prior to download. This allows for better throughput
on downloads, and provides the support for jukebox style CD ROM's.
For more detailed explanation, see the following section "CD ROM
drives".
===========================================================================
January, 1993 (Preliminary) Page 85
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=============\
< CD ROM DRIVES >
\=============/
If the "CD ROM drive" flag is set for a particular directory, it indicates
that the files are located on a CD ROM drive. If the flag is ON, several
things (don't) happen.
(1) The file is not checked for existence.
During a normal file transfer the real DOS directory is searched to
determine that the file really exists. This check is not done for a CD
Rom area. Advice: Build your CD Rom .DIR files correctly.
(2) The file size is taken from the .DIR file, not the real file.
Again, to speed up the download process, the real size of the file is
not obtained, rather the block size in the .DIR file is used to
determine the file size. Advice: Build your CD Rom .DIR files correctly.
(3) The file is copied to a temporary download directory.
If the Temp Download Path is defined in the system config, and it's
valid, the file is COPIED from the CD Rom to the Temp Download Path
prior to download. Most of the time, it is erased after the download.
The file is erased when the batch download queue is cleared. If the user
adds files to the batch download queue, and logs off without downloading
the files they are *not* erased. A good thing to do during midnight
maintenance would be to erase any leftover files in the Temp Download
Path.
T.A.G. ".DIR" files can be placed in the DFILES (Main data file) directory
by preceding the filename with the "@" sign. They can be placed in the
MFILES (multinode directory) by preceding the filename with the "`"
(backquote) character.
===========================================================================
January, 1993 (Preliminary) Page 86
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/================\
< The Event Editor >
\================/
The Event Editor is provided to allow the Sysop or his/her designates to
create, modify, or delete an event on the system. This command can be
accessed through a menu command (//EVENTEDIT - see the menu documentation
for further details on setting up this command).
Alternately, the User Editor can be accessed at the wait screen or from any
menu on the board through the Control-Q HotKey, and selection (E)vent
Editor which requires password #2.
An event is an action that will occur at a predetermined time. The T.A.G.
bulletin board system allows two types of events, Internal and External.
There is no limit to the number of events which may be defined. Events
defined by the SysOp are stored in the file EVENTS.DAT, located in the main
data directory.
/===============\
< Internal Events >
\===============/
An internal event is a defined condition that exists for a defined period
of time. This period may be as short as one minute per month or as long as
24 hours per day, everyday (continuous). When a user logs on, T.A.G will
determine the active event(s), if any, and whether the user meets the
conditions specified in the event(s). If so, the user's access will be
modified as prescribed by the event. Internal events may be classified as
either logon events or chat events.
A logon event may be used to restrict certain users' access to your system
or the availability of some commands within your system during the event
period. A chat event may be used to modify the status of the SysOp
Available flag. Both logon events and chat events can be classified as
restriction events or permission events.
Below is an example of the menu for an internal event:
1. Event type :Internal
2. Description :Restrict out of balance weekdays
3. Status :Active
4. Scheduled day(s) :Weekly - Days = MTWTF--
5. Time active :20:00 to 24:00
6. Permission/restriction :Restriction
7. Logon/chat :Logon
8. Affected message :"@BADRATIO"
9. Unaffected message :"@GOODUSER"
===========================================================================
January, 1993 (Preliminary) Page 87
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
<<< Qualifiers >>>
A. Baud rate range :<<Inactive>>
B. SL range :0 to 30
C. DSL range :<<Inactive>>
E. AR flag required :<<Inactive>>
H. UL/DL ratio check:Active
1. Event Type:
This field may be toggled between Internal and External.
2. Description:
This field hold a string of 32 or fewer character which describes
the purpose and/or activity of the event.
3. Status:
This field may be toggled between Active (turned on) and Inactive
(turned off).
4. Scheduled day(s):
An event may be scheduled to run either on a given day of the
month (eg. the 15th) or on certain days of the week (eg. Monday,
Tuesday and Saturday). If you want an event to occur on two
different days of the month (eg. 15th and 30th), two events would
have to be defined.
5. Time active:
An internal event is in existence for a given period of time
during the day. This field defines the starting and ending time of
the event, in military time. 12:00 midnight is the demarkation
line. No event may begin before or end after midnight. If it is
necessary to define an event which runs through midnight (eg.
10:00pm through 2:00am the next morning), two events must be
defined. One from 22:00 to 24:00 and the other from 00:00 to
02:00.
6. Permission/restriction:
This field may be toggled between Permission and Restriction
depending on the type of internal event desired.
7. Logon/chat:
This field may be toggled between logon and chat depending on the
type of internal event desired.
===========================================================================
January, 1993 (Preliminary) Page 88
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
8. Affected message:
When a user matching the conditions specified in the "qualifiers"
section of the event editor logs onto the system during the event
period, s/he will be affected by the event. If present, the
message present in this field will be sent (after the last few
callers list is displayed). If the first character of the message
is the "@" character, T.A.G. will assume the field contains the
pathname of a text file to be displayed. If it is not a full
pathname, T.A.G. will search for the file in the alternate data
files directory. If an extension is not present, T.A.G. will
assume the standard *.MSG/.CLR files. If the first character is
NOT the "@" character, the string in the field will be displayed.
9. Unaffected message:
When a user logs onto the system during an event, but does not
meet the criteria specified in the "qualifiers" section of the
event editor, s/he will be unaffected by the event's activity. If
this field is used, a message will be sent to the unaffected user.
The rules for the string are the same as described in the
"Affected message" section above.
Internal Logon Restriction Events:
An internal logon restriction event has one purpose - to prevent a user
matching certain criteria from logging onto the system during the event
period.
The example on the previous page defines an event which occurs at 8:00pm
through midnight, Monday through Friday. It is designed to lock out
callers with an SL of 30 or lower whose file ratio is out of balance.
Notice it is defined as an (1) Internal (7) Logon (6) Restriction event,
and turned on (3). If the user is affected by the event (and therefore
prevented from logging on), s/he will receive the message
BADRATIO.MSG/.CLR from the alternate data files directory. Users who are
not affected by the event see the file GOODUSER.MSG/.CLR in the same
directory.
Internal Logon Permission Events:
An internal permission event causes an affected user's permissions to be
modified at logon by clearing/setting an AR flag and/or reducing the
allocated time for this logon session.
Assuming you want to prevent callers from accessing the on-line games
between the hours of 10:00 and 2:00 on the fifteenth of the month, an
internal logon permission event is required. In order to accomplish
this, the menu commands which allow access to the games would have to be
modified to require an AR flag. For purposes of this example, we will
use the "G" AR flag. The SysOp would have to give the "G" AR flag to all
users s/he wanted to have access to the games through the user editor.
(Since we'll assume that all users will be allowed to access the games
at some time, all users should be given this flag. Additionally, the
validation records should be modified to give the "G" AR flag at
validation.) The event should then be defined as follows:
===========================================================================
January, 1993 (Preliminary) Page 89
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
1. Event type :Internal
2. Description :Prevent games on the 15th
3. Status :Active
4. Scheduled day(s) :Monthly - Day = 15
5. Time active :10:00 to 14:00
6. Permission/restriction:Permission
7. Logon/chat :Logon
8. User affected message :"Games are temporarily down."
9. User unaffected msg. :""
<<< Qualifiers >>>
A. Baud rate range :<<Inactive>>
B. SL range :0 to 255
C. DSL range :<<Inactive>>
D. Maximum time :<<Inactive>>
E. AR flag required :<<Inactive>>
F. Set AR flag :<<Inactive>>
G. Clear AR flag :G
H. UL/DL ratio check:Active
This event is defined as an (1) Internal (7) Logon (6) Permission event
and turned on (3). To include all users, the SL range (B) is defined
from 0 to 255. Since this type of event allows the SysOp to temporarily
modify the user's AR flag settings and/or reduce (but not increase) the
user's on-line time, the additional qualifier fields appear on this
menu, maximum time, set AR flag and clear AR flag. Since the G flag
controls access to the games, and since we want to prevent access during
the event, the "G" flag is placed in the field "clear AR flag". (Any
changes made to the AR flags exist for this logon session only; no
permanent changes are made to the user record.)
Internal Chat Restriction Events:
The purpose of an internal chat event is to turn the SysOp Available
flag on or off for certain classes of users. A restriction event turns
off the flag; a permission event turns it on.
By way of example, assume you wish to turn the SysOp Available flag off
to all callers with a DSL between 30 and 50 inclusive everyday between
the hours of 6:00pm and 7:00pm. The event would be defined as follows:
1. Event type :Internal event
2. Description :Restrict chat - 30-50
3. Status :Active
4. Scheduled day(s) :Weekly - Days = MTWTFSS
5. Time active :18:00 to 19:00
6. Permission/restriction:Restriction
7. Logon/chat :Chat
8. Affected message :"SysOp is NOT available."
9. Unaffected message :"SysOp is available for you."
===========================================================================
January, 1993 (Preliminary) Page 90
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
<<< Qualifiers >>>
A. Baud rate range :<<Inactive>>
B. SL range :<<Inactive>>
C. DSL range :30 to 50
E. AR flag required :<<Inactive>>
H. UL/DL ratio check:<<Inactive>>
Internal Chat Permission Events:
A chat permission event turns the SysOp Available on for a qualifying
user. By way of example, assume you wish to turn the SysOp Available
flag on to all callers with the "S" AR flag and a baud rate of 9600 or
greater during the hours of 12:00 midnight through 7:00am on each
Tuesday and Saturday. The event would be defined as described on the
following page:
1. Event type :Internal event
2. Description :Allow chat - high baud w/ S AR
3. Status :Active
4. Scheduled day(s) :Weekly - Days = -T---S-
5. Time active :00:00 to 07:00
6. Permission/restriction:Permission
7. Logon/chat :Chat
8. Affected message :"@C:\BBS\TEXT\SYSOPIN"
9. Unaffected message :"@C:\BBS\TEXT\SYSOPOUT"
<<< Qualifiers >>>
A. Baud rate range :9600 to 19200
B. SL range :<<Inactive>>
C. DSL range :<<Inactive>>
E. AR flag required :S
H. UL/DL ratio check:<<Inactive>>
Quirks Associated with Internal Events:
The internal event system was defined to be as flexible as possible. With
flexibility comes the responsibility of wise use to prevent conflicts
and/or confusion. The following should be considered when constructing
internal events:
It is possible to define a logon restriction event that will reject all
users of your system, including the SysOp and/or local logons. It is also
possible to curtail anyone's access, including the SysOp, with an poorly
conceived logon permission event. It is possible to unintentionally give a
user access to restricted and sensitive commands with a poorly defined
logon permission event. Be careful and think about what you are doing when
defining events.
===========================================================================
January, 1993 (Preliminary) Page 91
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Since logon permission events alter a user's time and/or available menu
commands during a session, T.A.G. assumes you are allowing any user meeting
the criterion for the logon permission event access to your system during
the event. If you have defined one or more conflicting logon restriction
events that would have rejected the user at logon, the fact that one
qualifying logon permission event exists is enough to allow him/her access
to the system, even if the logon permission event exists solely to curtail
some of his/her permissions. In other words, logon permission events
override any and all logon restriction events. Similarly, chat permission
events override chat restriction events.
In the case of conflicting permission events such as above, T.A.G. will err
on the side of the SysOp and restrict the activity, however it still prints
all messages you tell it to. Finally, consider that conflicting logon
permission and logon restriction events will probably print the ultimate in
confusing messages:
Sorry, your ratio is out of balance. You are being logged off.
Welcome to the system. The SysOp is NOT available.
/===============\
< External Events >
\===============/
An external event is an activity that will be executed from T.A.G. at a
scheduled time from the wait screen. There are two types of external
events, hard and soft events. A hard event is an activity which is
scheduled to occur at a given time and, if necessary, T.A.G. will reduce a
user's on-line time so that s/he is forced off of the system so that the
event will occur at exactly the time specified. Soft events execute at the
first available opportunity at, or after, the scheduled time. Therefore,
restricting a user's time is unnecessary.
External events are executed in one of two ways, 1) by halting T.A.G.
completely and allowing the controlling batch program to run a program(s)
based on the error code set by T.A.G. upon exit (ErrorLevel Events) and, 2)
through a DOS shell (Shell Events).
/=========================\
< External ErrorLevel Event >
\=========================/
In an external errorlevel event, T.A.G. actually halts executing and is
dropped out of memory with an errorlevel defined by the SysOp in the
external event editor. In order for this method to be effective, it is
absolutely necessary for T.A.G. to be running under the control of a
batch file so that T.A.G. can be restarted after the event has ended. It
is necessary that the batch file be constructed in such a manner that it
(the batch file) recognizes the errorlevel passed by T.A.G., processes
the event and restarts T.A.G.
===========================================================================
January, 1993 (Preliminary) Page 92
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
By way of example, assume that you wish to drop out of T.A.G. every day
at midnight to do nightly maintenance. Assume further your batch file is
written to perform the maintenance if errorlevel is 25. Below is an
example of the settings that would exist after the event was defined.
1. Event type :External
2. Description :Do midnight games maintenance
3. Status :Active
4. Execution hard/soft :Hard
5. Error level/shell file:Error level = 25
6. Scheduled day(s) :Weekly - Days = MTWTFSS
7. Start time :00:00
8. Phone status :Remain on-hook
9. Executed today :Yes (Next scheduled date:09/24/90 - in 84 minutes)
The (highly simplified) corresponding batch file might be:
:START
rem MAKE SURE WE'RE IN PROPER DRIVE/DIRECTORY
C:
CD \BBS
rem START UP BBS
TAG
rem T.A.G. HAS HALTED - IS IT AN EVENT?
IF ERRORLEVEL 25 GOTO MAINT
rem NO. DROPPED FOR OTHER REASON. RESTART T.A.G.
GOTO START
rem MAINTENANCE EVENT - RUN THE MAINTENANCE PROGRAMS
:MAINT
TWMAINT
TODAYBBS
rem EVENTS PROCESSED - RESTART T.A.G.
GOTO START
===========================================================================
January, 1993 (Preliminary) Page 93
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/========================\
< External DOS Shell Event >
\========================/
In an external DOS shell event, T.A.G. executes the event by shelling
out to DOS from the wait screen, executing the defined program and
returning to the board.
Let's assume that you wish to shell out at 3:00am to run the T.A.G. Top
20 programs by shelling out. Below is an example of the settings that
would exist after the event was defined.
1. Event type :External
2. Description :Top 20 bulletins
3. Status :Active
4. Execution hard/soft :Soft
5. Error level/shell file:Shell file = "TOP20"
6. Scheduled day(s) :Weekly - Days = MTWTFSS
7. Start time :03:00
8. Phone status :Off-hook (1 minute before event)
9. Executed today :Yes (Next scheduled date:09/24/90 - in 12 minutes)
===========================================================================
January, 1993 (Preliminary) Page 94
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/====================================\
< Single File Transfer Protocol Editor >
\====================================/
NN Key Description
-- ======== ========================================================
0 Q (Q) Abort transfer
1 N (N) Next matching file (skip)
2 B (B) Batch transfer
3 A (A) ASCII
4 C (C) Xmodem-Checksum
..
..
9 Z (Z) Zmodem
10 R (R) Zmodem Recovery/Resume
11 M (M) Mega-Link
12 J (J) Jmodem
Single Protocols: (D:elete,I:nsert,M:odify,P:osition,Q:uit): M
Protocol to start editing (0-12): 9
Single Protocol : 9
1. Key : Z
2. Description : (Z) Zmodem
3. Baud rates : Minimum: 300 Maximum: 19200
4. DSL : 10
5. Temp log : "[Main Data Dir]\DSZTEMP.LOG"
6. (U)Load log : "[Main Data Dir]\DSZ.LOG"
(D)Load log : "[Main Data Dir]\DSZ.LOG"
7. (U)L string : "protocol.bat dsz port [Port] rz [Directory]\[Filename]"
(D)L string : "protocol.bat dsz port [Port] sz [Directory]\[Filename]"
8. Return codes : Transfer Successful
9. (U)Load codes : A. 0 B. 0 C. 0 D. 0 E. 0 F. 0
(D)Load codes : A. 0 B. 0 C. 0 D. 0 E. 0 F. 0
Protocol Edit: (1-9,[,],B,J,T,Q,?):
===========================================================================
January, 1993 (Preliminary) Page 95
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=========================\
< Protocol Variable Strings >
\=========================/
The following variable strings are available in options "5", "6", and "7"
as indicated below in the "Cmds" column. To enter these codes, type
Control-P followed be the appropriate key listed below:
Cmds Key String Meaning
---- --- -------------- -----------------------------------
7 "B" [Baud] (Locked) baud rate of system
567 "C" [Current Dir] Current path (Main BBS Directory)
7 "D" [Directory] Directory of current file
7 "F" [Filename] Filename of current file
567 "M" [Main Data Dir] Main Data Files Directory
7 "P" [Port] Communications port
7 "R" [Real Baud] Actual baud rate of current user
567 "U" [UL Directory] Upload Directory of current section
Path names DO NOT end in a backslash (e.g. C:\BBS\DFILES). Note the "\"
between [Directory] and [Filename] in the above definition of the Zmodem
protocol.
1. Key:
This field holds the command that is used to execute the protocol or
command. It may be up to 12 characters in length.
2. Description:
This field is the used to describe the protocol or command. It is used
when T.A.G. generates a protocol menu for the user. Standard Control-P
colors are available.
3. Baud rates:
These fields define the minimum and maximum baud rates required to use
the protocol or command. Uses of this may include prohibiting 9600 baud
users from using Xmodem, or alternately, forcing 300 baud users to use
Ymodem.
4. DSL:
This field indicates the minimum DSL required for a user to access the
protocol or command.
5. Temp log:
This field contains the path and name of the log file (if the protocol
uses one) to which file transfer data is written (e.g. DSZLOG should
point to this file for DSZ transfers). From here, the system will move
the log entries to the appropriate upload or download log, if defined,
for permanent records. See the table above this section for the variable
strings available in this field. When defining a protocol which does not
support log files, these fields should be left blank. Non-protocol
commands do not use this field.
===========================================================================
January, 1993 (Preliminary) Page 96
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
6. (U)Load log / (D)Load log:
These fields contain the path and name of the permanent log files for
both uploads and downloads. The log entries after each transfer are
moved to these files for permanent records. See the table above this
section for the variable strings available in this field. In the event
that the protocol being defined does not support a log file, the log
fields should remain blank. Non-protocol commands do not use this field.
7. (U)L string / (D)L string:
These fields contain the actual commands and options necessary to
execute an upload and/or download. When an external protocol is being
defined, the string will normally consist of the control batch filename
(PROTOCOL.BAT in the above example) followed by the command line
required to execute the external protocol being defined. The detailed
command line information required can normally be found in documentation
included with the external protocol, itself. See the table above this
section for the variable strings available in this field. Note: Except
for ASCII file transfers, T.A.G. does not support internal protocols.
Creating an external protocol allows complete control of the calling
command line. The shell currently used, more often than not, does not
return error levels correctly from executed files unless they are called
from a batch file. Additionally some protocols do not return correctly and
on some errors and may leave the board sitting in DOS. Thus it is highly
recommended that standard external protocols call protocol.bat which simply
is a line of parameters which will in turn call the protocol in question.
See the above Zmodem example for a clearer example.
Protocol Edit: (1-9,[,],B,J,T,Q,?): 7
(U)pload/(D)ownload/(Q)uit: U
(I)nternal command/protocol, (E)xternal protocol, or (Q)uit: E
New upload string
:
Creating an Internal protocol/Command displays a list of available options.
Simply choose one, and a set string will be placed in the field.
Protocol Edit: (1-9,[,],B,J,T,Q,?): 7
(U)pload/(D)ownload/(Q)uit: U
(I)nternal command/protocol, (E)xternal protocol, or (Q)uit: I
0. Disable (make inaccessible) 1. Quit - Abort Transfer
2. Next matching file 3. ASCII (DL only)
4. Batch (add to queue)
Internal: (0-4):
===========================================================================
January, 1993 (Preliminary) Page 97
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
The status of a transfer is determined through comparison of the error
level returned to the system and the information stored in options "8" and
"9" (see these options for more information).
8. Return codes:
This field indicates whether the upload/download return error levels
listed in option 9 represent successful or failed transfers. The
following table shows the results for both settings:
Transfer Successful:
1. If the error level returned matches one of those listed, then the
transfer was successful.
2. If the error level returned does not match one of those listed, then
the transfer is assumed to have failed.
Transfer Failed:
1. If the error level returned matches one of those listed, then the
transfer failed.
2. If the error level returned does now match one of those listed, then
the transfer is assumed to be successful.
Internal protocols and non-protocol commands do not use this field.
9. (U)Load codes / (D)Load codes:
These fields list the error levels the protocol is expected to return
for good or bad transfers according to the return code setting in option
8. Valid error levels for MS-DOS range from 0 to 255. For protocols
which have less than 6 different return codes, simply set the remaining
values to be duplicates of another already existing value. DSZ (tm) for
example returns zero on a successful transfer; thus setting all the
return codes to zero will prevent any weird error levels from causing
problems. Internal protocols and non-protocol commands do not use this
field.
===========================================================================
January, 1993 (Preliminary) Page 98
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===================================\
< Batch File Transfer Protocol Editor >
\===================================/
NN Key Description
-- ======== ==================================================
0 Q (Q) Quit - Abort transfer
1 Y (Y) Ymodem Batch
2 G (G) Ymodem-G Batch
3 Z (Z) Zmodem Batch
Batch Protocols: (D:elete,I:nsert,M:odify,P:osition,Q:uit): M
Protocol to start editing (0-3): 0
Batch Protocol : 3
1. Key : Z
2. Description : (Z) Zmodem Batch
3. Baud rates : Minimum:300 Maximum:19200
4. DSL : 10
5. Temp log : "[Main Data Dir]\DSZTEMP.LOG"
6. (U)Load log : "[Main Data Dir]\DSZ.LOG"
(D)Load log : "[Main Data Dir]\DSZ.LOG"
7. (U)L string : "protocol.bat dsz port [Port] rz [UL Directory]"
(D)L string : "protocol.bat dsz port [Port] sz @[Current Dir]\dszlist.tmp"
8. Return codes : Transfer Successful
9. (U)Load codes: A. "z" B. "Z" C. "s" D. "S" E. "r" F. "R"
(D)Load codes: A. "z" B. "Z" C. "s" D. "S" E. "r" F. "R"
L. (U)L FileList: ""
(D)L FileList: "[Current Dir]\DSZLIST.TMP"
M. Max cmd chars: 128
P. Log position : (F)ilename: 51 (S)tatus: 1
/===============================\
< Batch Protocol Variable Strings >
\===============================/
The following variable strings are available in options "5", "6", "7", and
"L" as indicated below in the "Cmds" column. To enter these codes, type
Control-P followed be the appropriate key listed below:
Cmds Key String Meaning
---- --- --------------- -----------------------------------
7 "B" [Baud] (Locked) baud rate of current user
567L "C" [Current Dir] Current path (Main BBS Directory)
7 "D" [Directory] Directory of current file
7 "F" [Filename] Filename of current file
567L "M" [Main Data Dir] Main Data Files Directory
7 "P" [Port] Communications port
7 "B" [Real Baud] Actual baud rate of current user
567L "U" [UL Directory] Upload Directory of current section
===========================================================================
January, 1993 (Preliminary) Page 99
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Path names DO NOT end in a backslash (e.g. C:\BBS\DFILES). Note the
"\" after the [Main Data Dir] in the log definitions.
The current file counter is only incremented whenever [Filename] appears.
Thus several [Filename]'s would produce an actual list of several different
files; while several [Directory]'s would repeat the same directory
constantly until a [Filename] was encountered to move the pointer to the
next file.
1. Key:
This field holds the command that is used to execute the protocol or
command. It may be up to 12 characters in length.
2. Description:
This field is the used to describe the protocol or command. It is used
when T.A.G. generates a protocol menu for the user. Standard Control-P
colors are available.
3. Baud rates:
These fields define the minimum and maximum baud rates required to use
the protocol or command. Uses of this may include prohibiting 9600 baud
users from using Xmodem, or alternately, forcing 300 baud users to use
Ymodem.
4. DSL:
This field indicates the minimum DSL required for a user to access the
protocol or command.
5. Temp log:
This field contains path and name of the log file (if the protocol uses
one) to which the result of the file transfer is written (e.g. DSZLOG
should point to this file for DSZ transfers). It is highly recommended
that only protocols that produce some T.A.G. readable log be used, as
errors in crediting the user's account can occur with aborted transfers
if one does not exist. The system will analyze each file's log entry and
then move into the appropriate upload or download log, if they are
defined, for permanent records. See the table above this section for the
variable strings available in this field. If no log file exists, T.A.G.
can only guess as to the result of the transfer. With batch downloads,
this means the system will charge the user for all files listed in the
queue, as there is no way it could know how many files were actually
transferred. With batch uploads it will be possible for users to upload
files that were not specified in the queue, and not receive any kind of
indication that the file was uploaded. It would not appear in the file
listing, and the user would not receive any credit. To run a protocol
without a transfer log, simply leave this field blank. Internal
protocols and non-protocol commands do not use this field.
===========================================================================
January, 1993 (Preliminary) Page 100
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
6. (U)Load log / (D)Load log:
These fields contain the path and name of the permanent log files for
both uploads and downloads. The log entries after each transfer are
moved to these files for permanent records. See the table above this
section for the variable strings available in this field. In the event
that the protocol being defined does not support a log file, the log
fields should remain blank. Internal protocols and non-protocol commands
do not use this field.
7. (U)L string / (D)L string:
These fields contain the actual commands and options necessary to
execute an upload and/or download. When a protocol which is not internal
to T.A.G. (external protocol), is being defined, the string will
normally consist of the control batch filename (PROTOCOL.BAT in the
above example) followed by the normal command line required to execute
the external protocol being defined. The detailed command line
information required can normally be found in documentation included
with the external protocol. See the table above this section for the
variable strings available in this field.
Creating an external protocol allows complete control of the calling
command line. The shell currently used, more often than not, does not
return error levels correctly from executed files unless they are called
from a batch file. Additionally some protocols do not return correctly and
on some errors and may leave the board sitting in DOS. Thus it is highly
recommended that standard external protocols call protocol.bat which simply
is a line of parameters which will in turn call the protocol in question.
See the above Zmodem example.
There are two standard methods for sending multiple files. The first method
is an ASCII file (each file name and complete path listed on an individual
line) containing a list of the files to send; basically we tell the
protocol to "send the files listed in this file". DSZ (tm) allows this and
is used in the above example. Option "L" is defined to create a list of
files to send (see that option for more information) and then the download
string points at the list of files with "@[Current Dir]\dszlist.tmp". The
second method for sending multiple files is specifying them on the command
line. Because of DOS's command line length limitations (128 characters in
most cases) this often limits the number of files that can be sent at one
time. A sample protocol string which uses this method is as follows.
(U)L string: ""
(D)L string: "protocol.bat clink T [Directory]\[Filename]
Here T.A.G. will process the command line adding files until either the
maximum line length defined in option "M" is exhausted (see that option for
more information), or the system simply runs out of files to send. In the
later case, the system will stop processing the command line when the first
[Directory] or [Filename] appears for which no file is available and simply
return what it has up to that point. In the above download string, no extra
"\"'s will appear if there are only 2 files to send.
===========================================================================
January, 1993 (Preliminary) Page 101
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Protocol Edit: (1-9,L,M,P,[,],B,J,T,Q,?): 7
(U)pload/(D)ownload/(Q)uit: U
(I)nternal command/protocol, (E)xternal protocol, or (Q)uit: E
New upload string
:
Creating an Internal protocol/command displays a list of available options.
Simply choose one, and a set string will be placed in the field which
T.A.G. will in turn look for (yes, you could just use the external option
and simply type the set string if you know them and it will make no
difference, it must be in capitals however).
Protocol Edit: (1-9,L,M,P,[,],B,J,T,Q,?): 7
(U)pload/(D)ownload/(Q)uit: U
(I)nternal command/protocol, (E)xternal protocol, or (Q)uit: I
0. Disable (make inaccessible)
1. Quit - Abort Transfer
Internal: (0-1):
The status of a transfer is determined through comparison of the log
information and the information stored in options "8", "9", and "P" (see
these options for more information). If no protocol log exists, the best
guess options described in option "5" are used.
8. Return codes:
This field indicates whether the upload/download return status codes
listed in option 9 represent successful or failed transfers. The
following table shows the results for both settings:
Transfer Successful:
1. If the status code found matches one of those listed, then the
transfer was successful.
2. If the status code found does not match one of those listed, then the
transfer is assumed to have failed.
Transfer Failed:
1. If the status code found matches one of those listed, then the
transfer failed.
2. If the status code found does now match one of those listed, then the
transfer is assumed to be successful.
Internal protocols and non-protocol commands do not use this field.
===========================================================================
January, 1993 (Preliminary) Page 102
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
K. (U)Load codes / (D)Load codes:
These fields list the status codes the protocol log file is expected to
contain for good or bad transfers according to the return code setting
in option 8. The status is obtained as defined in option "P" (see that
option for more information). These status codes may be up to 10
characters in length. For protocols which have less than 6 different
return codes, simply set the remaining values to be duplicates of
another already existing value. DSZ (tm) for example can have up to 6
different values in the status column. Granted there are 3 for each
downloads and uploads, but you will never see the other 3 in either case
so it makes little difference. Internal protocols and non-protocol
commands do not use this field.
L. (U)L FileList / (D)L FileList:
These fields specify files which should be created with a list of all
the files to transfer. They are in ASCII format, and the files to
transfer are listed one per line. Having a list file defined takes
precedence over specifying files on the command line. If both are done,
the system will assume all files are going to be sent even if the system
could not fit them all on the command line. Non-standard protocols could
be driven using this option, where the batch file would run some kind of
processing program to that this list and put it in the format required
before actually calling the protocol. If you have a custom batch file,
it is not necessary to call it through protocol.bat. See the table above
this section for the variable strings available in this field.
M. Max cmd chars:
This field indicates the maximum DOS command line length allowed on your
system. As far as we know, 128 characters is by far the over-all
standard, but other replacement DOS's may allow longer command lines. If
the command line limited is reached, the string returned is that after
the last [Filename] was successfully inserted. So for example if the
[Directory] should fit on the command line, but the [Filename] will not,
the string returned will not contain a trailing directory entry without
a filename.
P. Log position:
These fields indicate the position of the important information in the
protocol log which T.A.G. uses to determine the status of transfers.
Logs are assumed to be in ASCII format, with one line listed per file.
Both fields indicate the character position in the log line starting
from column 1 of the needed information. The (F)ilename and (S)tatus
fields begin at the indicated column and end with the next space (" ")
encountered. Internally, the filename is converted to upper case and all
forward slashes ("/") are mapped to back slashes ("\") before the
information is used. Also the status field is truncated to 10 characters
if it is longer since the return codes have a 10 character maximum.
===========================================================================
January, 1993 (Preliminary) Page 103
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/========================\
< MINI-DOS System Security >
\========================/
The MINI-DOS environment gives the SysOp the means to permit users who are
not necessarily completely trusted access to a protected DOS like
environment. While we cannot guarantee anything, we gone to great extent to
provide the best security possible to important system files and other
files not related to the system.
When first entering the Mini-DOS environment, the only files a user, with a
SL below that of a SysOp, can modify are *.MSG, *.CLR, *.TXT, and message
text files located in the Message Text File Directory.
OVERRIDE
To override this protection, the user may enter the "OVERRIDE" command,
where they will be asked to enter SysOp password #3. If entered
correctly, most of the protection measures will be disabled. The only
exceptions being the files important to the system. These include all
*.LST, *.DAT, *.DIR, and *.LOG files. There is no reason for a user to
do anything with these files, so they are protected.
===========================================================================
January, 1993 (Preliminary) Page 104
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=========================\
< Programmable Text Strings >
\=========================/
The programmable text string options allows the SysOp to change specific
commonly used messages on the system to their liking. The programmable
string files are stored in the AFILES directory, and must be compiled
before they can take effect.
The programmable text string system completely supports T.A.G. color codes
(Control-C + ColorNumber) and T.A.G. SDR codes in all "Editable" string
files.
Programmable text string files:
"Default" string files: MSTRDEF.TXT TSTRDEF.TXT
These files are released (new) with each version of T.A.G. and should not
be changed by the sysop. These strings are "overridden" by the
corresponding entries in the "Editable" strings files. It is not advisable
to make changes directly to these files, since they are replaced each new
version.
MSTRDEF.TXT User string default file - Contains the default values for
user strings which can be overridden in the "Editable"
MSTRMSG.TXT and MSTRCLR.TXT string files.
TSTRDEF.TXT System string default file - Contains the default values for
those strings which can be overridden in the "Editable"
TSTRMSG.TXT and TSTRCLR.TXT string files.
"Editable" string files: MSTRMSG.TXT MSTRCLR.TXT TSTRMSG.TXT TSTRCLR.TXT
These files can be created by the sysop to customize the default
settings. MSTRMSG.TXT and TSTRMSG.TXT correspond to non-ansi strings,
and MSTRCLR.TXT and TSTRCLR.TXT correspond to ansi strings.
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).
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).
===========================================================================
January, 1993 (Preliminary) Page 105
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
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).
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).
"Compiled" string file: TAGSTR.DAT
This file is created by the string compiler from the corresponding
"Default" and "Editable" files.
/==================================\
< Changing programmable text strings >
\==================================/
1. Exit T.A.G. Do not modify string files from a shell!
2. Find the string you want to change in the "Default" string files.
3. Copy the "block" (Including the leading and trailing "*"'s) from the
"default" string file to the corresponding "Editable" string file(s).
4. Make changes to the strings as necessary, never changing the keyword
line, or removing the "*"'s indicating the start/end of the block.
5. Run TAGSTR to compile the TXT files into DAT files. Make sure to use
the version of TAGSTR corresponding to your T.A.G. version.
6. Restart T.A.G.
Structure of programmable text string files:
The structure of the "Editable" programmable text string files is:
*[!]<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 "*".
===========================================================================
January, 1993 (Preliminary) Page 106
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Notes on programmable text strings:
T.A.G. color codes (Control-C follow by a color number "0" to "9") are
completely supported. Though it is possible to use ANSI graphic
characters in these strings, I highly recommend you do NOT do this. The
main reason being that ANSI graphics are not filtered out of text by
T.A.G., so when a user not supporting them logs onto the system, they
will see the ugly ANSI control codes in their true form.
Some lines, when displayed, are not followed by a carriage return (e.g.
prompts for user input). These lines are flagged with an "*" in their
descriptions.
The programmable string files are completely optional. If any are
missing or corrupted to the point that T.A.G. cannot read them, the
system will automatically use the built in default strings.
The compiled TAGSTR.DAT string file MUST be located in the AFILES
(Alternate Text Files) directory. After compilation to the TAGSTR.DAT
file, the "Editable" string files are not referenced by T.A.G., and may
be stored offline.
/=====================\
< Display Control Codes >
\=====================/
Currently, T.A.G. supports only one DC code, control-P. To force a pause
while displaying a text file, place a control-P on a separate line of the
text file.
===========================================================================
January, 1993 (Preliminary) Page 107
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===============\
< MULTINODE Setup >
\===============/
/====================\
< Theory of multinode >
\====================/
T.A.G. can be run in a Multinode environment. Multinode consists of running
multiple copies of T.A.G., and sharing certain data files.
Multiple copies of T.A.G. can be run in several ways, depending on your
hardware.
On a single CPU, multi-taskers such as DesqView or Double-DOS (among
others) can be used. Minimum memory for a T.A.G. to run properly is
approximately 350K. The amount may need to be increased for external
programs such as doors, mailers, external editors, etc.
On a network, a copy can be run from each CPU. T.A.G. is aware of common
networks, including PC-NET, Lantastic, Novell, and Banyan. You must
specify the type of network in the system configuration. Many networks
can be used as simply MS-NET, which is a simple Microsoft compatible
network.
Each copy of T.A.G. MUST have its own separate startup directory, and
SWAP directory. After that, sharing of files is dependant on the setup of
the AFILES, DFILES, MULTINODE, and NODELIST directories. You can choose
to share them with all nodes, or some.
When T.A.G. shares files is determined by the presence or absence of a
particular file from where it is "supposed" to be. IF a file is where it
is "supposed" to be, T.A.G. will use it.
For example: The files USER.LST and NAMES.LST are "Supposed" to be in the
DFILES directory. If they are found there, T.A.G. will use them from
there. If they are NOT there, T.A.G. tries to find them in the MULTINODE
directory. This searching method allows flexibility in the sharing and
isolating of files.
===========================================================================
January, 1993 (Preliminary) Page 108
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================================\
< General MultiNode Directory Structure >
\=====================================/
The standard multinode directory structure is similar to the following
example:
C:\ --+-- BINKLEY
|
+-- MSGS
| |
| +-- LOCAL
| |
| +-- ECHO
| . Msg*.Bbs
|
+-- MULTI
| . Auto.Msg . Macros.Lst . Shortmsg.Dat . User.Lst
| . Bbslist.Msg . Main.Dic . Sprot.Dat . Validate.Dat
| . Bprot.Dat . Mboards.Dat . Tagerror.Log . *.DIR
| . Fboards.Dat . Menus.Lst . Taglines.Msg
| . Fzscan.Dat . Mzscan.Dat . Tagquote.Msg
| . LastOn.Dat . Names.Lst
|
|
+-- AFILES
| . Welcome.Msg . Welcome.Clr
|
+-- BBS1
| | . Mailer.Bat . Status.Dat
| | . Mchat.Bat . Tag.Exe/Ovr
| |
| +-- GFILES
| . Sysop.Log . Usage.Log
|
+-- BBS2
| | . Mchat.Bat . Status.Dat . Tag.Exe/Ovr
| |
| +-- GFILES
| . Sysop.Log . Usage.Log
|
+-- FILES
|
+-- GAMES
|
+-- UTILS
===========================================================================
January, 1993 (Preliminary) Page 109
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===============\
< Multinode Setup >
\===============/
1. SHARE *should* be loaded when running Multinode.
2. Each node requires a separate startup directory with a STATUS.DAT file
in each. Each startup directory requires separate copies of BAT files.
3. Each node requires a separate GFILES directory for the sysop logs for
each node, and the usage logs.
4. Typically, a new MULTINODE directory is created for shared files. The
tree on the previous page lists files which *can* be moved to the new
MULTINODE directory. These files are not REQUIRED to be shared, but CAN
be shared.
5. Use TAGSETUP.EXE in each startup directory to set/change paths and
node numbers.
6. Set the Network type in T.A.G.
/===========\
< PKEYS/PDATA >
\===========/
All the Multinode commands share the same Pkey, the backquote "`".
PKEY "`"
PDATA FUNCTION DESCRIPTION
----- --------- --------------------------------------------
B Broadcast Send a message to all active nodes.
M Message Send a message to one node.
W Who's on Shows a list of users currently online.
C<Filename> ChatDoor Calls external Multinode Chat Door.
<Filename> is the filename of the batch file to be
called. Tested doors include Saberchat and RAP.
/===========\
< "DIR" Files >
\===========/
T.A.G. ".DIR" files can be placed in the MULTINODE Directory by
preceding the filename with a backquote "`" symbol.
===========================================================================
January, 1993 (Preliminary) Page 110
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==================\
< Caveats (warnings) >
\==================/
While T.A.G. may be multinode, and SHARE aware, most of the utilities are
not. If you are running external utilities with T.A.G. (everybody does)
it is IMPORTANT to ensure that T.A.G. is not trying to access the same
file as the utility at the same time. The results of this are
unpredictable, but at the least, are unadvisable, and at worst, can
result in the loss/corruption of the file. Most often, either T.A.G. or
the utility will report runtime errors of 153 or 154.
There are two typical situations where T.A.G. and external programs
conflict.
(1) Tossing/Scanning mail (RA/Hudson)
Unless you are using a share aware tosser/scanner, AVOID tossing or
scanning mail while a user is on. The recommended method for ensuring
that a user is not on is for the BAT for Node 1 to create a semaphore
file when a user logs in, and erase it when the user logs out. Node 2
can test for the existence of the semaphore file and avoid tossing mail
while a user is on.
A FIDO style message is relatively immune to this problem, since
tossers add new files to the directory, rarely opening existing MSG
files.
(2) Midnight maintenance
AVOID running non-share-aware utilities which read the user list,
".DIR" files or other frequently-accessed file while a user is on.
Encourage your local utility author to add "Share Aware" to his
software.
/=============\
< Door Programs >
\=============/
T.A.G. creates Dorinfo?.Def, where "?" is the node number of the node
creating the dorinfo file. For more than 9 nodes (1-9) T.A.G. uses letters
to replace the ? in the Dorinfo?.Def filename (i.e., node 10 generates
DORINFOA.DEF). Also, the Door.Sys file has the node number in it. Make
sure to modify batch files accordingly.
===========================================================================
January, 1993 (Preliminary) Page 111
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/===================================================\
< Setting up an external full screen editor (QuickED) >
\===================================================/
Setting up an external full-screen editor is easy. The interface was kept
as general as possible, so it should be fairly easy to use other full
screen editors so long as they follow some basic standards.
NOTES:
You MUST be running a fossil driver in order to use the QuickED full
screen editor.
QuickED is a separate product written by Dror and Oren Tirosh. It
must be downloaded separately and the requirements for running it
must be read.
INSTALLATION OVERVIEW:
1. Place the QuickED files in your main BBS directory and run the
install program.
2. Modify your personal data menu to allow user control of the editor
status.
3. Create a EXTEDIT.BAT file for T.A.G. to call the editor.
Installing QuickED is easy. Place the files in your main BBS directory and
run the QEDINST.EXE program. Nothing needs to be changed, simply quitting
out of the install program at that point will be fine.
You may wish to browse the (S)etup features at a later time, some
interesting features exist. Registration only effects a limited number of
features, which is explained in the QuickEd documentation.
A user option exists which should be placed in your personal data menu to
give users the control over the use of the full screen editor. Choices are
to ask the user each time they create a message, always use the editor, or
never use the editor. The command information is as follows:
Function : Toggle Editor Status
Pkey : D
Pdata : 14
Users who do not support ANSI graphics will automatically default to use of
the internal editor.
T.A.G. looks for a batch file called "EXTEDIT.BAT" in the main program
directory to see if a full screen editor is available. If it exists, and
the user chooses to use it, a generic door call is made to that batch file
to execute the editor (see the menu documentation for information on the
generic door call parameters). If installing QuickED, the batch file
"EXTEDIT.BAT" should contain the following line:
quicked %7 %1 %2 300
This passes the port number, baud rate, time left, and seconds before
timeout respectively.
===========================================================================
January, 1993 (Preliminary) Page 112
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
If the user is replying to a message, a file called "MSGTMP" (with no
extension) is created for the external editor in a ready to quote format.
It is a standard ASCII file with the familiar quoting character ">" already
inserted before each line. QuickED allows quoting from this file using the
Control-<K> <Q> option if it exists.
Upon returning, T.A.G. expects written message to appear in a file called
"MSGTMP" (with no extension - yes, the same file as the quote file). The
format expected is normal ASCII with $8D (141 decimal) used to indicate a
soft carriage return, and a <CR> <LF> sequence to indicate a hard carriage
return.
The following error levels are checked upon returning from the editor:
0 Normal return, save message.
1 User aborted the message, don't save it.
2 User inactivity/timeout, hang up.
===========================================================================
January, 1993 (Preliminary) Page 113
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============================================\
/ PC-Board(tm), RBBS(tm), QuickBBS(tm), GAP(tm), \
\ and DOOR.SYS External Program Examples /
\==============================================/
<< IMPORTANT >> COMMAND.COM must appear in your Main BBS Directory before
any door command will operate.
External program example using the Door Master program:
Menu Name: On Line Games #8
Command number: 9
1. Long desc: (C)avern's of ASCII
2. Short desc: (C)OA
3. Key: C
4. General SL: 50
5. AR flag: @
6. Program Key: =
7. Program data: "COA.BAT"
8. Flags: SL security check, GSL and AR, Normal CMD
This is the listing of the COA.BAT file:
REM ** Execute DoorMaster with parameters to create PCBOARD.SYS.
REM ** Note: PCBOARD must be in upper case.
DM PCBOARD %1 %2 %3 %4 %5 %6
REM
REM ** Copy the created PCBOARD.SYS file into the COA directory.
copy pcboard.sys d:\doors\coa
REM
REM Change Drives, then Change to the Cave's of ASCII directory.
d:
cd \doors\coa
REM
REM Execute Cave's of ASCII on the "kesmi1" dungeon.
coa_play kesmi1
REM
REM Copy the status list created by COA into bulletin 12.
copy kesmi1.lst c:\bbs\dfiles\bullet12.msg
REM
REM Back to the main BBS drive and directory.
c:
cd \bbs
You will need DM.EXE and COMMAND.COM in your main BBS directory.
===========================================================================
January, 1993 (Preliminary) Page 114
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/============================================\
< External program using the QuickDoor program >
\============================================/
Menu Name: On Line Games #8
Command number : 9
1. Long desc : (T)ask Force PC-Board Game
2. Short desc : (T)ask Force
3. Key : T
4. General SL : 50
5. AR flag : @
6. Program Key : =
7. Program data : "TASK1.BAT"
8. Flags: SL security check, GSL and AR, Normal CMD
This is the listing of the TASK1.BAT file:
REM Execute QuickDoor to create the PCBOARD.SYS file.
quickdor %4,%5,%1,%6,%2,%3
REM
REM Change to the Task Force drive and directory.
d:
cd \doors\task
REM
REM Execute Task Force and then the scoring program
taskforc 1 c:\bbs\pcboard.sys
tfreport
REM
REM Copy the created files into bulletin 15, 16, and 17.
copy tf-rank.rpt c:\bbs\dfiles\bullet15.msg
copy tf-crypt.rpt c:\bbs\dfiles\bullet16.msg
copy tfdetail.rpt c:\bbs\dfiles\bullet17.msg
REM
REM Backup to the main BBS drive and directory.
c:
cd \bbs
You will need QUICKDOR.EXE, and a copy of COMMAND.COM in your main BBS
directory for this example.
===========================================================================
January, 1993 (Preliminary) Page 115
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/======================\
< Setting up a DOS Shell >
\======================/
Suggested programs to use:
IBMAUX20.ZIP Redirects I/O to the communications port.
IBMAUX1.SYS and IBMAUX2.SYS version 2.0 - 04/25/86
Written by Wayne E. Conrad
Modified by Gee M. Wong (Fido 107/312)
WATCHDOG.ZIP Watches the communication port for a carrier drop.
WatchDog v1.1 (WATCHDG1.COM & WATCHDG2.COM) - 08/29/84
Written by James R. Reinders
Modified by Jim Kovalsky
MARKRELE.ZIP Marks and releases memory so that the part of WATCHDOG that
stays resident can be removed. Failure to do so will almost
certainly result in a system crash if the T.A.G. swap shell
is active.
The WATCHDG#.COM programs watch the user while they are in DOS. If the
carrier should drop while they are still in DOS, WatchDog takes control of
the system and re-boots it. Without WatchDog the system would remain down
since T.A.G. is not running to answer the phone.
These programs should be available on the board from which you obtained
the T.A.G. bulletin board system.
Several steps need to be taken in order to create an active local or
remote shell:
1. Take the appropriate IBMAUX#.SYS file and add it to your "CONFIG.SYS"
file. (Use IBMAUX1.SYS for COM1, and IBMAUX2.SYS for COM2). For COM1 you
would add this line:
device=ibmaux1.sys
2. Copy COMMAND.COM and the appropriate WATCHDG#.COM into in main BBS
directory. (Use WATCHDG1.COM for COM1, and WATCHDG2.COM for COM2).
3. The "SHELLLOC.BAT" and "SHELLREM.BAT" batch files must be in the Main
BBS Directory. Note: These files may need to be modified for your
particular system setup. Specifically the main BBS path, and the proper
IBMAUX and WatchDog programs.
===========================================================================
January, 1993 (Preliminary) Page 116
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=======================\
< Setting Up SHELLLOC.BAT >
\=======================/
SHELLLOC.BAT is used for local mode shell to DOS operations. The standard
batch file is as follows:
echo Enter "EXIT" to return to T.A.G.
prompt $p$g
command.com
c:
cd \bbs
exit
The "c:" and "cd\bbs" may change depending on where T.A.G. resides on your
system.
/=======================\
< Setting Up SHELLREM.BAT >
\=======================/
SHELLREM.BAT is used for remote mode shell to DOS operations. The standard
batch file is as follows:
echo off
mark
watchdg1 on
ctty aux1
echo Enter "EXIT" to return to T.A.G.
prompt $p$g
command.com
c:
cd \bbs
ctty con
watchdg1 off
release
exit
The "c:" and "cd\bbs" may change depending on where T.A.G. resides on your
system. "watchdg1 on", "ctty aux1", "watchdg1 off" may change depending on
which communications port your system uses.
/===========================================\
< Files= Information Line on the SysOp Window >
\===========================================/
Some door programs do not always properly close files. T.A.G. reports the
number of open files on a Files= statement on the SysOp window, so that the
SysOp can easily determine if a door is failing to close files. The Files=
statement reports two values. The first represents the number of files open
under T.A.G.; the second represents the total number of files open under
DOS. This information is also reported in the SysOp Log when a user logs
off. Although these numbers will vary from system to system depending on
its configuration and/or what the user is doing, common values at the menus
are Files=1,6.
===========================================================================
January, 1993 (Preliminary) Page 117
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=====================================\
< Automatic Archive Checking of Uploads >
\=====================================/
T.A.G. can very easily check all archived uploads for integrity immediately
after the upload is complete. This is done by calling T.A.G. calling
FILETEST.BAT (if it exists). FILETEST.BAT is called by T.A.G. with the
following parameters:
%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.
Some SysOps have used DOS communication routines such as IBMAUX or GATEWAY
to display the actual testing process. This is fine so long as you are
extremely careful that any programs you call after the test line will not
destroy the error level returned by the test.
===========================================================================
January, 1993 (Preliminary) Page 118
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/=============\
< Questionnaire >
\=============/
The questionnaire is a feature which allows a SysOp to create user
questionnaires. These can be used to allow a user to apply for higher
access such as Visiting SysOp, etc.
The questionnaire uses the "?" Program Key. The Program data consists of an
optional leading @ and a five character ID which is passed to the
questionnaire program. Using "xxxxx" to represent the 5 character ID the
following files are used:
Without the [@] parameter:
xxxxx.* Questionnaire list similar to a bulletin list. It indicates
the 2 character ID that the user must type for each
questionnaire (the menu).
xxxxxQ@@.* Individual questionnaire files. "@@" represents a 2
character ID that the user must type. This works exactly
like the bulletin system ("Q" stands for question file).
xxxxxA@@.TXT Answer file for the respective xxxxxQ@@.* questionnaire file
("A" stands for answer file). This file is automatically
created the first time a questionnaire is answered and it
accumulates all subsequent user responses.
With the [@] parameter:
xxxxxQ.* Questionnaire file the user is immediately sent into (i.e.
there is no menu). ("Q" stands for question file.)
xxxxxA.TXT Answer file for the respective "xxxxxQ.*" questionnaire file
("A" stands for answer file). This file is automatically
created the first time a questionnaire is answered and it
accumulates all subsequent user responses.
Note: An extension of ".*" indicates that both a ".MSG" and/or a ".CLR"
version of the file may exist. Questionnaire listing and data files
reside in the Alternate Text File Directory; answer files reside in
the Main Data Files Directory since they change as the questionnaire
system is used.
Questionnaire File Format
Basically questionnaires are standard text files. At the points where you
wish the system to stop and request input from the user, simply place a
"@Q@" anywhere you want in the text. See the example questionnaire below
for an idea of how it works.
===========================================================================
January, 1993 (Preliminary) Page 119
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/================\
< Calling Examples >
\================/
For these examples "JUNK" is assumed as the 5 character ID code passed to
the questionnaire: (Pdata: "JUNK")
Files used in the included example:
JUNK.MSG - Question list file (the menu).
JUNKQ1.MSG - Questionnaire when the user enters "1".
JUNKA1.TXT - Answer file for the above questionnaire.
JUNKQHA.MSG - Questionnaire when the user enters "HA".
JUNKAHA.MSG - Answer file for the above questionnaire.
The following examples assume Pdata is "@JUNK". Files used in the included
example:
JUNKQ.MSG - Questionnaire called.
JUNKA.TXT - Answer file for the above questionnaire.
Example of file JUNK.MSG
-= Questionnaire =-
1. Application for Visiting SysOp Status
2. Application for Higher Access
Example of file JUNK1.MSG
This questionnaire is for application for Visiting SysOp Access. If you
are running a board, you will receive higher access if you complete this
questionnaire.
1. Enter the name of your board: @Q@
2. Enter your board hours: @Q@
3. Enter the board phone number: @Q@
4. Enter a two line description of your board.
@Q@
@Q@
Thank you for completing the questionnaire.
===========================================================================
January, 1993 (Preliminary) Page 120
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/================================================\
< System Hints and Other SysOp & CoSysOp Functions >
\================================================/
[> Text files may contain Special codes for formatting text, which include:
1. Placing a "~*" (without the quotes) or a Control-B at the beginning
of a line, will center the line according to the current user's line
length. (Using the Turbo Pascal editor, a Control-B can be generated
by pressing Control-P + Control-B)
2. Placing a "~(" (again without quotes) at the beginning of a line will
cause the line to be right justified according to the user's line
length.
3. To change the color of text in any line you can imbed a Control-C
followed either a Control-@ (color #0) though Control-I (color #9) or
a "0" (color #0) through "9" (color #9) (without quotes of course) to
change the following text to the corresponding color. (Using the
Turbo Pascal editor, a Control-C can be generated by pressing
Control-P + Control-C. It is highly advised to use the "0"-"9" ASCII
characters for the color numbers as I have yet to locate an editor
that will generate an Control-@ (ASCII 0 (dec)).
4. Many control codes can be used without trouble (BELL (Control-G) for
example).
[> To Delete several public messages in a message section (or to empty a
message section completely prior to removing the section), there is a
feature that is a sub command of the (S)can command that may be used -
(B)lock delete. You will be prompted for the lowest and highest number
to be deleted. After a "Delete messages XX to YY (Y/[N])?" prompt is
answered "Y", the messages will be deleted. To remove a single message
use the (D)elete sub command. This command will allow you to optionally
remove the maker's post credit as well.
[> To Add a file quickly to a section listing, simply place the file in the
proper upload directory in DOS and then upload the file from the file
section. T.A.G. will see that the file already exists, and will ask the
user if s/he wishes to add it to the section list (local logons will
assume this is the case). By answering yes and entering the description,
T.A.G. will add the file to the listing without any transfer taking
place. To add multiple files to the section list, place the files in the
proper upload DOS directory and use the Upload command from the file
section. By using global file specifications (for example *.*, *.ZIP or
MAIN??.ZIP) the system will search the DOS directory for all matching
filenames and prompt you as described above. This is a handy feature for
uploading a small number of files or for finding "lost" files. Although
this method will work with an unlimited number of files, a faster method
may be to use special utilities designed especially for uploads of large
numbers of files. These are discussed in the next section.
===========================================================================
January, 1993 (Preliminary) Page 121
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
[> The three utilities DIRTXT, TXTFILE, and FILETXT should be used for
Adding large numbers of files to the system at one time. These utilities
convert the file listings to a text format to allow easy editing of
descriptions. See the FUTIL###.ZIP on most T.A.G. distribution systems
archive for more information (where "###" is the latest version number
available).
[> Upon exiting normally, T.A.G. returns an error level of 255 to DOS. To
have the system Automatically reboot on an error, the batch file used to
boot the system can look at the error level and reboot the system if it
is not 255. A sample batch file may look as follows (BBS.BAT):
:bbs
c:
cd \bbs
tag
if errorlevel 255 goto end
REM ** Abnormal exit, rerun the batch file **
go to bbs
:end
[> When in Chat mode with a user, you and the user have several options
available:
- Entering "@" on a blank line will exit chat mode in nothing is typed
for a short period of time.
- Entering "//bye" on a blank line will immediately log the user off of
the system.
- Entering "//beep" on a blank line will beep twice on both the
keyboard and remote sides. It can be used to alert either the user or
the SysOp if one should wander off.
- Entering "//type [Path\]<Filename.Ext>" on a blank line will print
the specified file to screen while in chat mode. The Main BBS
directory is the default directory.
[> Password checking is performed against the user's entered information.
The user's password cannot be contained in the following or it will be
rejected:
Computer type
Phone number
Zip code
City & State
Address
Real Name
User Name
"PASSWORD" (it cannot be the word itself)
===========================================================================
January, 1993 (Preliminary) Page 122
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
/==============\
< Runtime Errors >
\==============/
While every effort has been made to ensure the trouble free running of
T.A.G BBS, occasional Runtime Errors occur. T.A.G. handles runtime errors
by creating or appending to the file TAGERROR.LOG in the BBS startup
directory, a screen capture at the time of the error, and containing
pertinent information.
When reporting a runtime error, you should note the runtime error location,
as shown in the TAGERROR.LOG file. To help identify any errors, the
following is a list of common Runtime Errors:
DOS Errors
1 Invalid DOS function number
2 File not found
3 Path not found
4 Too many open files (not enough FILES in CONFIG.SYS)
5 File access denied
6 Invalid file handle
8 DosError - Not enough memory
12 Invalid file access code
15 Invalid drive number
16 Cannot remove current directory
17 Cannot rename across drives
18 No more files
IO Errors
100 Disk read past end of file error
101 Disk write error (disk full)
102 File not assigned
103 File not open
104 File not open for input
105 File not open for output
106 Invalid numeric format
Critical Errors
150 Disk is write protected
151 Unknown unit
152 Drive not ready
153 Unknown command
154 CRC error in data
155 Bad drive request structure length
156 Disk seek error
157 Unknown media type
158 Sector not found
159 Printer out of paper
160 Device write fault
161 Device read fault
162 Hardware failure (might be share violation / network error)
===========================================================================
January, 1993 (Preliminary) Page 123
T.A.G. BBS Version 2.6d Main Documentation
===========================================================================
Fatal Errors
200 Division by zero
201 Range check error
202 Stack overflow error
203 Heap overflow error
204 Invalid pointer operation
205 Floating point overflow
206 Floating point underflow
207 Invalid floating point operation
208 Overlay manager not installed
209 Overlay file read error
210 Object non initialized
211 Call to abstract method
212 Stream registration error
213 Collection index out of range
214 Collection overflow error
215 Arithmetic overflow error
216 General Protection fault
===========================================================================
January, 1993 (Preliminary) Page 124