/======================================\
< T.A.G. Version 2.5g 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. 2.5g - Copyright (C) 1986-1990 Robert Numerick, )
\________________ and Victor Capton. _________________/
\__________________________/
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
T.A.G. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Purpose and Requirements . . . . . . . . . . . . . . . . . . . . . 1
Updated Releases . . . . . . . . . . . . . . . . . . . . . . . . . 1
Commercial Releases . . . . . . . . . . . . . . . . . . . . . . . 1
The Source Code . . . . . . . . . . . . . . . . . . . . . . . . . 2
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Copyright and License . . . . . . . . . . . . . . . . . . . . . . 2
Installation of a New T.A.G. System . . . . . . . . . . . . . . . 2
T.A.G. Alpha Sites . . . . . . . . . . . . . . . . . . . . . . . . 3
Additional Information or Help . . . . . . . . . . . . . . . . . . 3
SysOp Keyboard Functions . . . . . . . . . . . . . . . . . . . . . . 4
F1 Modify SL. . . . . . . . . . . . . . . . . . . . . . . 4
Shift-F1 Modify DSL. . . . . . . . . . . . . . . . . . . . . . . 4
Alt-F1 Validate User. . . . . . . . . . . . . . . . . . . . . 4
F2 Modify SF Flags. . . . . . . . . . . . . . . . . . . . 4
Shift-F2 Modify AR Flags. . . . . . . . . . . . . . . . . . . . 4
Alt-F2 Modify File Points. . . . . . . . . . . . . . . . . . . 4
F3 Disable com port. . . . . . . . . . . . . . . . . . . . 4
Shift-F3 Shell to DOS w/o user. . . . . . . . . . . . . . . . . 4
Alt-F3 ALERT off. . . . . . . . . . . . . . . . . . . . . . . 4
Ctrl-F3 Shell to DOS with user. . . . . . . . . . . . . . . . . 5
F4 Toggle SysOp window. . . . . . . . . . . . . . . . . . 5
Shift-F4 Turn Off Sysop Window. . . . . . . . . . . . . . . . . 5
F5 Hang Up. . . . . . . . . . . . . . . . . . . . . . . . 5
Shift-F5 Hangup with Message. . . . . . . . . . . . . . . . . . 5
F6 Update time and status. . . . . . . . . . . . . . . . . 5
Shift-F6 Redraw SysOp window. . . . . . . . . . . . . . . . . . 5
F7 Subtract 5 minutes. . . . . . . . . . . . . . . . . . . 5
Alt-F7 Execute BAT file. . . . . . . . . . . . . . . . . . . . 5
F8 Add 5 minutes. . . . . . . . . . . . . . . . . . . . . 5
F9 Temporary SysOp access toggle. . . . . . . . . . . . . 5
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. . . . . . . . . . . . . . . . . . . . . . 6
Scrl-Lock SysOp available. . . . . . . . . . . . . . . . . . . . 6
Alt-Break SysOp available. . . . . . . . . . . . . . . . . . . . 6
Home Chat capture. . . . . . . . . . . . . . . . . . . . . . 6
Shift Express Logon. . . . . . . . . . . . . . . . . . . . . 6
Ctrl-Q Sysop Menu. . . . . . . . . . . . . . . . . . . . . . . 6
Files which are part of the T.A.G. system . . . . . . . . . . . . . . 7
File Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8
T.A.G. Command Line Parameters . . . . . . . . . . . . . . . . . . 21
Changing the Communications Port . . . . . . . . . . . . . . . . 21
Specifying an Alternate Directory for STATUS.DAT . . . . . . . . 21
=========================================================================
October 1, 1990 Page i
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
System Configuration . . . . . . . . . . . . . . . . . . . . . . . 22
Accessing the System Configuration On-line . . . . . . . . . . . 22
Description Of System Configuration Functions . . . . . . . . . 23
System Passwords . . . . . . . . . . . . . . . . . . . . . . 24
System information . . . . . . . . . . . . . . . . . . . . . 25
Open/Closed Systems . . . . . . . . . . . . . . . . . . . . . 25
Sysop Chat Hours . . . . . . . . . . . . . . . . . . . . . . 25
300 baud hours . . . . . . . . . . . . . . . . . . . . . . . 25
Time Limitations . . . . . . . . . . . . . . . . . . . . . . 26
Modem Communications Configuration . . . . . . . . . . . . . . . 27
No call reinit time . . . . . . . . . . . . . . . . . . . . . 27
Com-port Number . . . . . . . . . . . . . . . . . . . . . . . 27
Carrier Detect Mask . . . . . . . . . . . . . . . . . . . . . 28
Wait modem speed . . . . . . . . . . . . . . . . . . . . . . 28
Use FOSSIL driver . . . . . . . . . . . . . . . . . . . . . . 28
Modem initialization string . . . . . . . . . . . . . . . . . 28
How an Incoming Call is Processed . . . . . . . . . . . . 29
Modem answer string . . . . . . . . . . . . . . . . . . . . . 29
Modem hangup string . . . . . . . . . . . . . . . . . . . . . 30
Modem offhook string . . . . . . . . . . . . . . . . . . . . 30
Modem after hangup string . . . . . . . . . . . . . . . . . . 30
Modem result codes . . . . . . . . . . . . . . . . . . . . . 31
Single value security settings . . . . . . . . . . . . . . . . . 32
Full SysOp . . . . . . . . . . . . . . . . . . . . . . . . . 32
CoSysOp of system . . . . . . . . . . . . . . . . . . . . . . 32
SubOp of message system . . . . . . . . . . . . . . . . . . . 32
Download system CoSysOp . . . . . . . . . . . . . . . . . . . 32
No download ratio check . . . . . . . . . . . . . . . . . . . 32
Add a system to BBS list . . . . . . . . . . . . . . . . . . 33
Send normal private mail . . . . . . . . . . . . . . . . . . 33
See unvalidated files . . . . . . . . . . . . . . . . . . . . 33
See who posted anonymous . . . . . . . . . . . . . . . . . . 33
Reply to anonymous mail . . . . . . . . . . . . . . . . . . . 33
Post any pub anonymously . . . . . . . . . . . . . . . . . . 33
Send anonymous private . . . . . . . . . . . . . . . . . . . 33
See passwords remotely . . . . . . . . . . . . . . . . . . . 33
No post/call ratio check . . . . . . . . . . . . . . . . . . 33
Privilege (SL) . . . . . . . . . . . . . . . . . . . . . . . 33
Privilege (DSL) . . . . . . . . . . . . . . . . . . . . . . . 34
No download point check . . . . . . . . . . . . . . . . . . . 34
SysOp password #1 logon . . . . . . . . . . . . . . . . . . . 34
Read text file into msg . . . . . . . . . . . . . . . . . . . 34
Read msg validate cmd . . . . . . . . . . . . . . . . . . . . 34
Read msg user view cmd . . . . . . . . . . . . . . . . . . . 34
Post/call key flag . . . . . . . . . . . . . . . . . . . . . 34
SL/AR - Sysop menu . . . . . . . . . . . . . . . . . . . . . 34
=========================================================================
October 1, 1990 Page ii
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
General variables . . . . . . . . . . . . . . . . . . . . . . . 35
Maximum private sent per call . . . . . . . . . . . . . . . . 35
Maximum feedback sent per call . . . . . . . . . . . . . . . 35
Max public posts per call . . . . . . . . . . . . . . . . . . 35
Max mail waiting normal . . . . . . . . . . . . . . . . . . . 35
Max mail waiting CoSysOp . . . . . . . . . . . . . . . . . . 35
Max mail waiting SysOp . . . . . . . . . . . . . . . . . . . 36
Number back SysOp log days . . . . . . . . . . . . . . . . . 36
Number days keep Usage Log . . . . . . . . . . . . . . . . . 36
Max number of logon tries . . . . . . . . . . . . . . . . . . 36
Percent upload time refund . . . . . . . . . . . . . . . . . 36
Normal max lines/message . . . . . . . . . . . . . . . . . . 36
CoSysOp max lines/message . . . . . . . . . . . . . . . . . . 36
Maximum pages per call . . . . . . . . . . . . . . . . . . . 36
Starting logon menu number . . . . . . . . . . . . . . . . . 36
Minimum K-Bytes to post . . . . . . . . . . . . . . . . . . . 36
Minimum K-Bytes to upload . . . . . . . . . . . . . . . . . . 37
Maximum number of users . . . . . . . . . . . . . . . . . . . 37
Maximum files batch download . . . . . . . . . . . . . . . . 37
Maximum files batch upload . . . . . . . . . . . . . . . . . 37
Number of novice msg days . . . . . . . . . . . . . . . . . . 37
Maximum daily time bank deposit . . . . . . . . . . . . . . . 37
Maximum daily time bank withdraw . . . . . . . . . . . . . . 37
Maximum time in time bank . . . . . . . . . . . . . . . . . . 37
Main data file directory . . . . . . . . . . . . . . . . . . 38
Alternate text file directory . . . . . . . . . . . . . . . . 38
Message text file directory . . . . . . . . . . . . . . . . . 38
Swap file directory . . . . . . . . . . . . . . . . . . . . . 38
Swap shell active/inactive . . . . . . . . . . . . . . . . . 38
High Message Pointer . . . . . . . . . . . . . . . . . . . . 39
Chat colors . . . . . . . . . . . . . . . . . . . . . . . . . 39
=========================================================================
October 1, 1990 Page iii
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Optional flagged functions . . . . . . . . . . . . . . . . . . . 40
Title screen pause . . . . . . . . . . . . . . . . . . . . . 40
Blank off-line wait screen . . . . . . . . . . . . . . . . . 40
Logon to bulletin section . . . . . . . . . . . . . . . . . . 40
Handles allowed on system . . . . . . . . . . . . . . . . . . 40
Keyboard security protection . . . . . . . . . . . . . . . . 40
Front End Mailer . . . . . . . . . . . . . . . . . . . . . . 41
New user message sent to . . . . . . . . . . . . . . . . . . 41
SysOp mail forwarded to user . . . . . . . . . . . . . . . . 41
Minutes before time out . . . . . . . . . . . . . . . . . . . 41
Minutes before time out bell . . . . . . . . . . . . . . . . 41
Guest user number . . . . . . . . . . . . . . . . . . . . . . 42
The system operator is . . . . . . . . . . . . . . . . . . . 42
Store bad logon information . . . . . . . . . . . . . . . . . 42
Logon uses Auto-Message . . . . . . . . . . . . . . . . . . . 42
Logon takes phone off-hook . . . . . . . . . . . . . . . . . 43
Generic logon information . . . . . . . . . . . . . . . . . . 43
Logon asks for phone number . . . . . . . . . . . . . . . . . 43
Alert beeps only chat on . . . . . . . . . . . . . . . . . . 43
Auto chat buffer open . . . . . . . . . . . . . . . . . . . . 43
Scan/File find in SysOp log . . . . . . . . . . . . . . . . . 43
Direct screen writes . . . . . . . . . . . . . . . . . . . . 44
Screen snow checking . . . . . . . . . . . . . . . . . . . . 44
Try to use EMS for overlays . . . . . . . . . . . . . . . . . 44
Instant logon key . . . . . . . . . . . . . . . . . . . . . . 44
Local Security . . . . . . . . . . . . . . . . . . . . . . . 44
Show available upload space . . . . . . . . . . . . . . . . . 44
Show GIF resolution . . . . . . . . . . . . . . . . . . . . . 44
Time limitations . . . . . . . . . . . . . . . . . . . . . . 46
Calls allowed per day . . . . . . . . . . . . . . . . . . . . 46
Upload/download number of files ratio . . . . . . . . . . . . 46
Upload/download K-bytes ratio . . . . . . . . . . . . . . . . 46
Post/call ratio . . . . . . . . . . . . . . . . . . . . . . . 46
Range setting command information . . . . . . . . . . . . . . 47
S:et . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
T:oggle . . . . . . . . . . . . . . . . . . . . . . . . . 47
The Access Validation Editor . . . . . . . . . . . . . . . . . . . 48
Access Validation Fields . . . . . . . . . . . . . . . . . . . . 49
Record Number . . . . . . . . . . . . . . . . . . . . . . . . 49
Description . . . . . . . . . . . . . . . . . . . . . . . . . 49
Validation Key . . . . . . . . . . . . . . . . . . . . . . . 49
SL/DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
AR/SF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
File Points . . . . . . . . . . . . . . . . . . . . . . . . . 49
Time Bank . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
=========================================================================
October 1, 1990 Page iv
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Auto Validation Command . . . . . . . . . . . . . . . . . . . . 49
Adding the Validation Manager to TAG . . . . . . . . . . . . . . 49
Deleting Validation Records . . . . . . . . . . . . . . . . . . 50
Inserting Validation Records . . . . . . . . . . . . . . . . . . 50
Modifying Validation Records . . . . . . . . . . . . . . . . . . 50
Validation Edit Commands . . . . . . . . . . . . . . . . . . . . 51
Positioning Validation Records . . . . . . . . . . . . . . . . . 51
The User Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table of Special Flags (SF) for Users . . . . . . . . . . . . . 53
Auto private mail delete . . . . . . . . . . . . . . . . . . 53
No post/call ratio . . . . . . . . . . . . . . . . . . . . . 53
Cannot abort upload scan: . . . . . . . . . . . . . . . . . . 53
Cannot post anonymous . . . . . . . . . . . . . . . . . . . . 53
Cannot add to BBS list . . . . . . . . . . . . . . . . . . . 53
Cannot page sysop . . . . . . . . . . . . . . . . . . . . . . 53
No download limit . . . . . . . . . . . . . . . . . . . . . . 53
Cannot post public mail . . . . . . . . . . . . . . . . . . . 53
Cannot send private mail . . . . . . . . . . . . . . . . . . 53
Not allowed to vote . . . . . . . . . . . . . . . . . . . . . 53
Allowed only one call per day . . . . . . . . . . . . . . . . 53
Public mail is marked not validated . . . . . . . . . . . . . 53
Protect from deletion . . . . . . . . . . . . . . . . . . . . 53
Ignore file points . . . . . . . . . . . . . . . . . . . . . 53
Uploaded files not validated immediately . . . . . . . . . . 54
[PAUSE] active . . . . . . . . . . . . . . . . . . . . . . . 54
ANSI active . . . . . . . . . . . . . . . . . . . . . . . . . 54
Color active . . . . . . . . . . . . . . . . . . . . . . . . 54
Onekey input . . . . . . . . . . . . . . . . . . . . . . . . 54
Alert active . . . . . . . . . . . . . . . . . . . . . . . . 54
User is male . . . . . . . . . . . . . . . . . . . . . . . . 54
Mailbox is closed . . . . . . . . . . . . . . . . . . . . . . 54
Tabs active . . . . . . . . . . . . . . . . . . . . . . . . . 54
CLS character used . . . . . . . . . . . . . . . . . . . . . 54
Adjusting Numeric Values . . . . . . . . . . . . . . . . . . . . 55
Built in Security Features . . . . . . . . . . . . . . . . . . . 55
=========================================================================
October 1, 1990 Page v
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Extended User Listing Description . . . . . . . . . . . . . . . 56
User# . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Rec# . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
<<TAGGED>> . . . . . . . . . . . . . . . . . . . . . . . . . 57
AR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
SF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Call spread . . . . . . . . . . . . . . . . . . . . . . . . . 57
Mail waiting . . . . . . . . . . . . . . . . . . . . . . . . 57
MSG base SubOp . . . . . . . . . . . . . . . . . . . . . . . 57
Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
TimeBank . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Starting menu . . . . . . . . . . . . . . . . . . . . . . . . 58
Last <MSG/DL> base . . . . . . . . . . . . . . . . . . . . . 58
Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Normal User Listing Description . . . . . . . . . . . . . . . . 58
Abbreviations used in normal listing . . . . . . . . . . . . 59
Short User Listing Description . . . . . . . . . . . . . . . . . 59
User Editor Main Command Descriptions . . . . . . . . . . . . . 60
(Space) Toggle tag status of this user . . . . . . . . . . . 60
(=) Oops (load old data) . . . . . . . . . . . . . . . . . . 60
([) Back one user . . . . . . . . . . . . . . . . . . . . . . 60
(]) Forward one user . . . . . . . . . . . . . . . . . . . . 60
(/) Change all tagged . . . . . . . . . . . . . . . . . . . . 61
({) Search backward . . . . . . . . . . . . . . . . . . . . . 61
(}) Search forward . . . . . . . . . . . . . . . . . . . . . 61
(.) List all tagged . . . . . . . . . . . . . . . . . . . . . 61
(;) Relist user . . . . . . . . . . . . . . . . . . . . . . . 61
(-) Clear for reentry . . . . . . . . . . . . . . . . . . . . 62
(\) New user config . . . . . . . . . . . . . . . . . . . . . 62
(E) Special flags . . . . . . . . . . . . . . . . . . . . . . 62
(F) AR flags . . . . . . . . . . . . . . . . . . . . . . . . 62
(I) Last boards . . . . . . . . . . . . . . . . . . . . . . . 62
(L) Laston date . . . . . . . . . . . . . . . . . . . . . . . 62
(M) Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . 63
(N) New default list . . . . . . . . . . . . . . . . . . . . 63
=========================================================================
October 1, 1990 Page vi
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
(O) Options menu . . . . . . . . . . . . . . . . . . . . . . 63
General text . . . . . . . . . . . . . . . . . . . . . . . 64
Security level . . . . . . . . . . . . . . . . . . . . . . 64
D/L security level . . . . . . . . . . . . . . . . . . . . 64
AR flags set . . . . . . . . . . . . . . . . . . . . . . . 64
Special flags set . . . . . . . . . . . . . . . . . . . . 64
User status . . . . . . . . . . . . . . . . . . . . . . . 64
Days since last on . . . . . . . . . . . . . . . . . . . . 64
Number of calls . . . . . . . . . . . . . . . . . . . . . 65
User age . . . . . . . . . . . . . . . . . . . . . . . . . 65
User gender . . . . . . . . . . . . . . . . . . . . . . . 65
# 1/10's call/post . . . . . . . . . . . . . . . . . . . . 65
#K-DL/1K-UL . . . . . . . . . . . . . . . . . . . . . . . 65
# DL's/1 UL . . . . . . . . . . . . . . . . . . . . . . . 65
0-9,P,K,N: Alter option specifications . . . . . . . 66
SPACE: Toggle user tag status by number . . . . . . . . . 66
C:hange an option's state . . . . . . . . . . . . . . . . 66
E:mpty tag table . . . . . . . . . . . . . . . . . . . . . 66
I:nvert tag table . . . . . . . . . . . . . . . . . . . . 66
S:how tagged users . . . . . . . . . . . . . . . . . . . . 66
T:ag operations . . . . . . . . . . . . . . . . . . . . . 66
Union . . . . . . . . . . . . . . . . . . . . . . . . . 67
Intersection . . . . . . . . . . . . . . . . . . . . . 67
Difference . . . . . . . . . . . . . . . . . . . . . . 68
Divergence . . . . . . . . . . . . . . . . . . . . . . 68
(Q) Quit . . . . . . . . . . . . . . . . . . . . . . . . . . 69
(U) Jump to user . . . . . . . . . . . . . . . . . . . . . . 69
(V) Validate user . . . . . . . . . . . . . . . . . . . . . . 69
(W) Undelete user . . . . . . . . . . . . . . . . . . . . . . 69
(Y) Message base SubOp . . . . . . . . . . . . . . . . . . . 69
(0) Mail posts/waiting . . . . . . . . . . . . . . . . . . . 69
(!) Password . . . . . . . . . . . . . . . . . . . . . . . . 70
(#) User number . . . . . . . . . . . . . . . . . . . . . . . 70
($) Money (credit,debit) . . . . . . . . . . . . . . . . . . 70
(*) Delete user . . . . . . . . . . . . . . . . . . . . . . . 70
(') Change colors . . . . . . . . . . . . . . . . . . . . . . 70
(@) Time bank . . . . . . . . . . . . . . . . . . . . . . . . 70
(%) User history . . . . . . . . . . . . . . . . . . . . . . 70
(+) Configuration flags . . . . . . . . . . . . . . . . . . . 70
=========================================================================
October 1, 1990 Page vii
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
The Message Board Editor . . . . . . . . . . . . . . . . . . . . . 71
Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
File name . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
SL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
AR flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Post SL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Anonymous . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Max Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Allow ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
The File Board Editor . . . . . . . . . . . . . . . . . . . . . . . 73
Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
[@]File name . . . . . . . . . . . . . . . . . . . . . . . . . . 74
DL Path Name . . . . . . . . . . . . . . . . . . . . . . . . . . 74
UL Path Name . . . . . . . . . . . . . . . . . . . . . . . . . . 74
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
AR flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
See names DSL . . . . . . . . . . . . . . . . . . . . . . . . . 74
No ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
The Event Editor . . . . . . . . . . . . . . . . . . . . . . . . . 75
Internal Events . . . . . . . . . . . . . . . . . . . . . . . . 75
Event Type . . . . . . . . . . . . . . . . . . . . . . . . . 76
Description . . . . . . . . . . . . . . . . . . . . . . . . . 76
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Scheduled day(s) . . . . . . . . . . . . . . . . . . . . . . 76
Time active . . . . . . . . . . . . . . . . . . . . . . . . . 76
Permission/restriction . . . . . . . . . . . . . . . . . . . 77
Logon/chat . . . . . . . . . . . . . . . . . . . . . . . . . 77
Affected message . . . . . . . . . . . . . . . . . . . . . . 77
Unaffected message . . . . . . . . . . . . . . . . . . . . . 77
Internal Logon Restriction Events . . . . . . . . . . . . . . . 77
Internal Logon Permission Events . . . . . . . . . . . . . . . . 78
Internal Chat Restriction Events . . . . . . . . . . . . . . . . 79
Internal Chat Permission Events . . . . . . . . . . . . . . . . 79
Quirks Associated with Internal Events . . . . . . . . . . . . . 80
External Events . . . . . . . . . . . . . . . . . . . . . . . . 81
External ErrorLevel Event . . . . . . . . . . . . . . . . . . . 82
External DOS Shell Event . . . . . . . . . . . . . . . . . . . . 83
=========================================================================
October 1, 1990 Page viii
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Single File Transfer Protocol Editor . . . . . . . . . . . . . . . 84
Protocol Variable Strings . . . . . . . . . . . . . . . . . . . 85
[Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
[Current Dir] . . . . . . . . . . . . . . . . . . . . . . . . 85
[Directory] . . . . . . . . . . . . . . . . . . . . . . . . . 85
[Filename] . . . . . . . . . . . . . . . . . . . . . . . . . 85
[Main Data Dir] . . . . . . . . . . . . . . . . . . . . . . . 85
[Port] . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
[Real Baud] . . . . . . . . . . . . . . . . . . . . . . . . . 85
[UL Directory] . . . . . . . . . . . . . . . . . . . . . . . 85
Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Description . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Baud rates . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Temp log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
(U)Load log / (D)Load log . . . . . . . . . . . . . . . . . . . 86
(U)L string / (D)L string . . . . . . . . . . . . . . . . . . . 86
Creating an external protocol . . . . . . . . . . . . . . . . 86
Creating an Internal protocol . . . . . . . . . . . . . . . . 87
Return codes . . . . . . . . . . . . . . . . . . . . . . . . . 87
Transfer Successful . . . . . . . . . . . . . . . . . . 87
Transfer Failed . . . . . . . . . . . . . . . . . . . . 87
(U)Load codes / (D)Load codes . . . . . . . . . . . . . . . . . 87
=========================================================================
October 1, 1990 Page ix
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Batch File Transfer Protocol Editor . . . . . . . . . . . . . . . . 88
Batch Protocol Variable Strings . . . . . . . . . . . . . . . . 88
[Baud] . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
[Current Dir] . . . . . . . . . . . . . . . . . . . . . . . . 88
[Directory] . . . . . . . . . . . . . . . . . . . . . . . . . 88
[Filename] . . . . . . . . . . . . . . . . . . . . . . . . . 88
[Main Data Dir] . . . . . . . . . . . . . . . . . . . . . . . 88
[Port] . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
[Real Baud] . . . . . . . . . . . . . . . . . . . . . . . . . 88
[UL Directory] . . . . . . . . . . . . . . . . . . . . . . . 88
Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Description . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Baud rates . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
DSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Temp log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
(U)Load log / (D)Load log . . . . . . . . . . . . . . . . . . . 90
(U)L string / (D)L string . . . . . . . . . . . . . . . . . . . 90
Creating an external protocol . . . . . . . . . . . . . . . . 90
Creating an Internal protocol . . . . . . . . . . . . . . . . 91
Return codes . . . . . . . . . . . . . . . . . . . . . . . . . 92
Transfer Successful . . . . . . . . . . . . . . . . . . . 92
Transfer Failed . . . . . . . . . . . . . . . . . . . . . . . 92
(U)Load codes / (D)Load codes . . . . . . . . . . . . . . . . . 92
(U)L FileList / (D)L FileList . . . . . . . . . . . . . . . . . 92
Max cmd chars . . . . . . . . . . . . . . . . . . . . . . . . . 93
Log position . . . . . . . . . . . . . . . . . . . . . . . . . . 93
MINI-DOS System Security . . . . . . . . . . . . . . . . . . . . . 94
OVERRIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
=========================================================================
October 1, 1990 Page x
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Programmable Text Strings . . . . . . . . . . . . . . . . . . . . . 95
COMMSTR.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . 96
"[PAUSE]" . . . . . . . . . . . . . . . . . . . . . . . . . . 96
"[WAIT]" . . . . . . . . . . . . . . . . . . . . . . . . . . 96
"One moment please ..." . . . . . . . . . . . . . . . . . . . 96
"Thank you" . . . . . . . . . . . . . . . . . . . . . . . . . 96
">><*><<" . . . . . . . . . . . . . . . . . . . . . . . . . . 96
"How about sending the SysOp a letter instead." . . . . . . . 96
"Enter a short reason" . . . . . . . . . . . . . . . . . . . 96
"Paging system operator, please hold ..." . . . . . . . . . 96
"Entering chat mode ..." . . . . . . . . . . . . . . . . . . 96
"Leaving chat mode ..." . . . . . . . . . . . . . . . . . . . 96
"Are you sure you want to log off ? (Y/N) : " . . . . . . . . 96
"Would you like to leave the SysOp a Comment ? (Y/N) : " . . 96
MAINSTR.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . 97
"Would you like an ANSI logon screen (Y/N)? " . . . . . . . . 97
"To be a guest on the system enter "GUEST" as your user name" 97
"New users enter your first & last name or handle" . . . . . 97
"Enter user name or ID number: " . . . . . . . . . . . . . . 97
"Name NOT found in user log." . . . . . . . . . . . . . . . . 97
"Please enter your real name or handle" . . . . . . . . . . . 97
"Enter bulletin ID, <?> to List, or <CR> to Quit? " . . . . . 97
"Thank you for taking the time to vote." . . . . . . . . . . 97
"Enter questionnaire ID, <?> to List, or <CR> to Quit? " . . 97
FILESTR.TXT . . . . . . . . . . . . . . . . . . . . . . . . . . 98
"Search all directories for a file mask." . . . . . . . . . . 98
"Enter the string to search descriptions for." . . . . . . . 98
"<CR> for all files" . . . . . . . . . . . . . . . . . . . . 98
"Enter file to list interior files of" . . . . . . . . . . . 98
"Download -" . . . . . . . . . . . . . . . . . . . . . . . . 98
"Your upload/download ratio is out of balance:" . . . . . . . 98
"Access denied." . . . . . . . . . . . . . . . . . . . . . . 98
"You do not have enough file points to download this file." . 98
"File added to batch queue." . . . . . . . . . . . . . . . . 98
System Data Reference (SDR) Codes . . . . . . . . . . . . . . . . . 99
User Data (SDR Control-U Codes) . . . . . . . . . . . . . . . . 99
System Data (SDR Control-S Codes) . . . . . . . . . . . . . . . 99
Display Control (DC) Codes . . . . . . . . . . . . . . . . . . . 99
Setting up an external full screen editor (QuickED) . . . . . . . . 100
External program example using the Door Master program . . . . . . 102
External program using the QuickDoor program . . . . . . . . . . . 103
=========================================================================
October 1, 1990 Page xi
T.A.G. BBS Version 2.5g Main Documentation
=========================================================================
>>> Table of Contents <<<
Setting up a DOS Shell . . . . . . . . . . . . . . . . . . . . . . 104
IBMAUX20.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . 104
WATCHDOG.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . 104
MARKRELE.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Setting Up SHELLLOC.BAT . . . . . . . . . . . . . . . . . . . . 105
Setting Up SHELLREM.BAT . . . . . . . . . . . . . . . . . . . . 105
Files= Information Line on the SysOp Window . . . . . . . . . . . . 106
Automatic Archive Checking of Uploads . . . . . . . . . . . . . . . 106
ZIPFT.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
ARCFT.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
PAKFT.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
LZHFT.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Interfacing your System with the Matrix/Echo Mail Network . . . . . 107
What is this stuff . . . . . . . . . . . . . . . . . . . . . . . 107
Echo mail . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Matrix/Net mail . . . . . . . . . . . . . . . . . . . . . . . 107
Advantages of setting up a mailer system . . . . . . . . . . . . 108
Disadvantages of setting up a mailer system . . . . . . . . . . 108
Questionnaire . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Questionnaire File Format . . . . . . . . . . . . . . . . . . . 110
Calling Examples . . . . . . . . . . . . . . . . . . . . . . . . 110
System Hints and Other SysOp & CoSysOp Functions . . . . . . . . . 111
Special codes for formatting text . . . . . . . . . . . . . . . 111
Delete several public messages in a message section . . . . . . 111
Add a file quickly to a section listing . . . . . . . . . . . . 112
Adding large numbers of files to the system . . . . . . . . . . 112
Automatically reboot on an error . . . . . . . . . . . . . . . . 112
Chat mode with a user . . . . . . . . . . . . . . . . . . . . . 113
Password checking . . . . . . . . . . . . . . . . . . . . . . . 113
=========================================================================
October 1, 1990 Page xii
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
___________________
/ \
(o) Written by: (o)
\ /
(o) Victor Capton (o)
/ and \
(o) Robert Numerick (o)
\___________________/
*********************************************************************
Additional programming by Paul Loeber, Randy Goebel and Paul Williams
*********************************************************************
Special thanks to Wayne Bell for his original ideas
for a user-friendly BBS interface
*********************************************************************
T.A.G. is founded in the belief in the Shareware marketing concept
which encourages low cost, high quality software.
Purpose and Requirements
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
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
quarterly, but we are unable to give a firm schedule.
Commercial Releases
At this time there are no plans for a commercial release. But we will
consider reasonable offers should interest be shown.
=========================================================================
October 1, 1990 Page 1
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
The Source Code
The source code for T.A.G., written in Turbo Pascal 5.5, is not available
for the general public.
Warranty
This product is provided on an "as is" basis. The Tag Team does not
accept responsibility for system damage, loss of profit, or any other
special, incidental, or consequential damages resulting from the use or
inability to use this product.
Copyright and License
T.A.G. is not public domain software; it is copyrighted by Robert
Numerick and Victor Capton. 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 distribute the program with any "bundled" software packages.
4. Do not accept ANY kind of remuneration for the program.
5. Do not alter the program in any manner.
6. The Standard Released versions may not be used in any commercial
manner.
Any Commercial version of the software found in the Shareware or Public
Domain market area will be in violation of both licensee and copyright
agreements!
Installation of a New T.A.G. System
A start up package is distributed under the name of GFILE*.ZIP, where "*"
indicates the version number in question. This compressed file contains
complete documentation concerning the setup of a new system.
=========================================================================
October 1, 1990 Page 2
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
>> T.A.G. Alpha Sites <<
System Name Number Bauds Node # Main SysOp
------------------- ------------ --------------- ------- ---------------
*A*R*T*H*U*R* 313-879-2318 3/12/24/96(HST) 120/120 Victor Capton
Genesis II <temp. down> 3/12/24/96(HST) 120/14 Robert Numerick
Downriver Download 313-292-0665 3/12/24/96(HST) 120/137 Paul Loeber
The Black Hole 313-879-7387 3/12/24/96(HST) 120/36 Randy Goebel
CRIMP/John Galt 313-582-6671 3/12/24/96(HST) 120/116 Paul Williams
Additional Information or Help
For more information contact one of the Alpha or Beta sites or send mail
to:
The Tag Team
P.O. Box 1009
Taylor, MI 48180
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.
=========================================================================
October 1, 1990 Page 3
T.A.G. BBS Version 2.5f 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 (one exception being during a
download or upload):
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 online 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.)
=========================================================================
October 1, 1990 Page 4
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
Take 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.
Give 5 minutes to the user's time on-line.
F9 Temporary SysOp access toggle.
Toggles Temporary Sysop access for the user online. 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.
=========================================================================
October 1, 1990 Page 5
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 online.
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.
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.)
=========================================================================
October 1, 1990 Page 6
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/=========================================\
< Files which are part of the T.A.G. system >
\=========================================/
File name conventions:
Files with an extension of ".*" indicate that both a ".MSG" and possibly
a ".CLR" version may be present. ".CLR" files are displayed for users
with their ANSI graphics active.
Flags:
A = This file is located in the Alternate Text File Directory.
B = This file is located in the Main BBS Directory.
D = This file is located in the Main Data Files Directory.
F = This file is feature based. This means if the feature in question
is not being used or is not likely to ever occur, then the file
need not be present.
M = This file is printed by a command in the standard menu system
included with the start up system. If you remove the command,
obviously the file is no longer needed.
O = This is an optional file. No error messages will be generated if
it is not present.
S = This is a system file used to store information concerning the
system.
=========================================================================
October 1, 1990 Page 7
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/================\
< File Definitions >
\================/
FLG Filename Description
--- ------------- --------------------------------------------------
DS *.brd These files contain the header information for the
public message section with the corresponding
section file name and defined in the message section
manager.
S *.dir These files contain the file listing for the file
sections with the corresponding section file name as
defined in the file section manager. They appear in
the appropriate file directory (or alternately may
be placed in the main data files directory).
AF <BoardName>.* These files contain descriptions of message and file
sections corresponding to the board name defined in
appropriate section manager.
AF <HelpID>#.* 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.
AF access.* This file is displayed to users when they
successfully validate themselves with the
auto-validation command (PKey="5").
AO 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.
AO arlevel@.* This file is displayed 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).
OB arcft.bat This batch file performs archive integrity checking
for "*.ARC" files. It is called whenever such a
file is uploaded. See the automatic archive
checking section of this documentation for more
information. See the file "notest" also.
DOS auto.msg This file contains the auto-message that may be
displayed when a user logs onto the system.
DFS bbslist.msg This file contains a list of other bulletin boards
generated by the main system "Other BBS" command.
=========================================================================
October 1, 1990 Page 8
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
BF binkley.bat (See also Mailer.Bat) Binkley Term (tm) mailer batch
file. This file is used in conjunction with Binkley
Term (tm) mail processing system. When the Binkley
front end option is active, T.A.G.'s
initialization/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. Binkley Term
should return the following error levels:
1 - Exit T.A.G. normally with error level 255 (same as
using (Q)uit from the wait screen).
3 - 300 baud caller connection.
10 - Keyboard local logon - F1 from Binkley Term.
12 - 1200 baud caller connection.
20 - Temporarily disable the mailer program and remain at
the wait screen - F2 from Binkley Term. Use (X) to
re-activate the mailer program from the wait screen.
24 - 2400 baud caller connection.
96 - 9600 baud caller connection.
AO birthday.* This file is displayed whenever a user calls on
their birthday. If it does not exist, a default
congratulations is used (see postbday.* also).
DS boards.dat This file contains the configuration information for
each of the message sections on the system.
AO bdlprot.* This file is used to create a customized batch
download protocol menu instead of using the standard
system generated menu.
DS bprot.dat This file contains all the configuration information
concerning batch transfer file protocols.
AO bulprot.* This file is used to create a customized batch
upload protocol menu instead of using the standard
system generated menu.
AF 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@@.msg" file description.
=========================================================================
October 1, 1990 Page 9
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
AF 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.
For example:
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
AO 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).
DS callers.log This file contains a list of all the current day's
callers, including local calls made by SysOps.
DOS 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.
AFO chatoff.* This file can be user for an alternate response to
the SysOp available command when the chat call is
off (see chaton.* also).
AFO chaton.* This file can be used for an alternate response to
the SysOp available command when the chat call is on
(see chatoff.* also).
AOS 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). An "OTHER" option is automatically
added by T.A.G. at the bottom of the list where
users will be asked to type their computer type if
none of the selections fit. If this file does not
exist, users will just be asked to enter their
computer type in all cases. This file may be
changed at any time without effecting current users.
=========================================================================
October 1, 1990 Page 10
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
BOS commstr.txt This file contains common programmable strings to
both the main and file systems. See the section on
programmable strings for more information.
A dosmenu.msg This file contains the menu displayed from the
Mini-DOS environment when the user asks for help by
entering "?".
AO dsl###.* These files contain a message for all users with the
DSL specified by "###". "###" is a number from 0 to
255 (e.g. dsl10.msg).
DS email.dat This file contains the message header information
for all private mail on the system.
BOS extedit.bat This file is the bat file used to invoke a full
screen editor from the message menu. See the
Example, Setting up the external full screen editor
in this doc file.
BF extern#.bat These files are executed when the appropriate Alt-F5
key sequence is given. "#" is a number from "1" to
"9" (e.g. extern1.msg). One of these files could be
used to execute an external full screen chat program
for example. The following parameters are passed on
the command line:
1) Communications port (1 to 4)
2) Baud rate (300, 1200, 2400, etc)
3) Minutes remaining on-line
4) ANSI graphics status (0=off or 1=on)
DS fboards.dat This file contains the configuration information for
each of the file sections on the system.
BOS filestr.txt This file contains programmable strings for the file
system. See the section on programmable strings for
more information.
AF 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" or "SHIT" because the user has no
reason what-so-ever to enter such things in their
user name.
AO goaway.* This file is displayed when the user has paged the
SysOp more than the maximum number of times defined
in the system configuration.
=========================================================================
October 1, 1990 Page 11
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
AF 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.
AF 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)
DS laston.dat This file contains a list of the last few callers to
log onto the system. The information is displayed
when a user logs on.
AFO 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.
A logoff.* This file is displayed when a user logs off the
system in the normal method.
BO logon.bat This file contains special feature logon
instructions. If it exists, T.A.G. will call it
with six parameters (the user's baud rate, time
remaining in minutes, user number, first name, last
name, ANSI graphics (1=On, 0=Off), and the current
communications port respectively). The call is made
using the generic doors format.
AMO 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.
AO 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".
DSF macros.lst The file contains the macros that users have defined
for themselves. Space is NOT wasted for users who
have not defined macros.
=========================================================================
October 1, 1990 Page 12
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
BF mailer.bat (See also Binkley.Bat) This file is used in
conjunction with any front end mailer or mail
processing system. When the front end option is
active, T.A.G.'s initialization/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
mailer should return the following error levels:
1 - Exit T.A.G. normally with error level 255 (same as
using (Q)uit from the wait screen).
3 - 300 baud caller connection.
10 - Keyboard local logon - F1 from Binkley Term.
12 - 1200 baud caller connection.
20 - Temporarily disable the mailer program and remain at
the wait screen. Use (X) to re-activate the mailer
program from the wait screen.
24 - 2400 baud caller connection.
96 - 9600 baud caller connection.
BOS mainstr.txt This file contains programmable strings for the main
system. See the section on programmable strings for
more information.
AO msghelp.* This file is displayed when a user requests help
when entering a message. Standard help text is
displayed when this file is not present.
DS menus.lst This file contains the configuration information of
the menus on the system.
DS names.lst This file contains a sorted linked pointer list of
the current users on the system. It allows quick
searching for names and numbers.
BO newlogon.bat This file contains special feature logon
instructions for a user logging on for the first
time. If it exists, T.A.G. will call it with six
parameters (the user's baud rate, time remaining in
minutes, user number, first name, last name, ANSI
graphics (1=On, 0=Off), and the current
communications port respectively). The call is made
using the generic doors format.
A 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.
=========================================================================
October 1, 1990 Page 13
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
DF newqa.txt This file contains the answers to the new user
questionnaire (see newqq.* also).
AF 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).
AF no300.* This file is displayed when a user tries to logon at
300 baud outside the restricted times defined in the
system configuration. After the file is displayed,
the user is disconnected (see yes300.msg also).
AO noaccess.* This file is displayed when users choose menu
options which are inaccessible (the privilege level
can cause inaccessible commands to be displayed).
AMO noboard.* This file, if present, is displayed when a user with
a DSL lower than the "privilege" level defined in
the system configuration (normally a new user) trys
to access a file board that is only available to
validated users.
AO 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.
AF 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.
FO 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 in meaningless, just so long
as it exists. Please note that the file does not
have an extension. See the files "arcft.bat",
"pakft.bat", and "zipft.bat" also.
AFO 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.
=========================================================================
October 1, 1990 Page 14
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
AF 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.
AF other.* This file contains help and information which is
displayed when a user is adding a number to the
other BBS listing.
OB pakft.bat This batch file performs archive integrity checking
for "*.PAK" files. It is called whenever such a
file is uploaded. See the automatic archive
checking section of this documentation for more
information. See the file "notest" also.
AO 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).
AF postcall.* This file is displayed anytime a user fails the
post/call ratio check.
BO postdl.bat This file, if it exists, is executed after all
downloads (whether batch or otherwise) as a post
processing function. The following parameters are
passed to the file:
1) Current baud rate (300,1200,2400, etc)
2) Communications port (1 to 4)
3) User ID number
AMO 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.
BO postul.bat This file, if it exists, is executed after each
upload as a post processing function. The following
parameters are passed to the file:
1) Current baud rate (300,1200,2400, etc)
2) Communications port (1 to 4)
3) User ID number
4) Upload pathname where the file went
5) Filename of the file uploaded
6) Filename of the *.DIR list for the upload section.
=========================================================================
October 1, 1990 Page 15
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
AMO 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.
BFS protocol.bat This file is used by the external protocol system to
call the various external protocols via the protocol
editor. This file is used because the shell
currently used, more often than not, does not return
error levels correctly from executables unless they
are called from a batch file. Additionally some
protocols do not return correctly at all on some
errors and may leave the board sitting in DOS. This
file fixes those problems.
It simply contains a line of parameters as follows:
%1 %2 %3 %4 %5 %6 %7 %8
AO 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.
AO quotehlp.* This file contains help text to the user explaining
the /QUOTE feature in the message base.
BFS shellloc.bat This file contains the instructions that will be
executed when a local shell to DOS is executed. See
the section on shelling to DOS for more information.
BFS shellrem.bat This file contains the instructions that will be
executed when a remote shell to DOS is executed. See
the section on shelling to DOS for more information.
DS shortmsg.dat This file contains all the short messages still
waiting for users. Messages stored in this file
include:
"So-n-so read your message on 00/00/00 00:00:00",
"You were validated on 00/00/00 00:00:00",
etc.
AO 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).
AO sdlprot.* This file is used to create a customized single file
download protocol menu instead of using the standard
system generated menu.
=========================================================================
October 1, 1990 Page 16
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
DS sprot.dat This file contains all the configuration information
concerning single file transfer protocols.
AO sulprot.* This file is used to create a customized single file
upload protocol menu instead of using the standard
system generated menu.
BS status.dat 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 the command line
parameters sections for more information.
AF sysfull.* This file is displayed to any new users who try to
logon after the system has reached the maximum
number of users.
DS 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.
DSF 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.
DM sysopmnu.msg This file is displayed by the standard main menu
command ";". It contains a list of the special
flags and their meanings.
DM system.msg This file is displayed by the standard main menu
command "I". It contains software/hardware/SysOp
information about the current system.
BS tag.* The files TAG.EXE and TAG.OVR are the programs for
the main system of the board itself.
AF 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)
=========================================================================
October 1, 1990 Page 17
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
S 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:
<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\gfiles\xxxgif.msg
*.ARC @c:\bbs\gfiles\noarc.msg
AOS 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
=========================================================================
October 1, 1990 Page 18
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
AS 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.
AO 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.
DOS 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.
AO user###.msg These files contain private logon messages to the
users whose numbers are specified by "###" (e.g.
user128.msg).
DS users.lst This file contains the user information of all users
currently on the system.
=========================================================================
October 1, 1990 Page 19
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
DFS voting.dat 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.
A 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.
AO welcome#.* These files are displayed after the welcome.msg file
in increasing order. "#" is a number from "1" to
"9" (e.g. welcome1.msg).
DM write.msg This file is displayed by the standard message menu
command "H". It is a help file giving information
on the features of the message editor.
AF yes300.* This file is displayed when a 300 baud user logs on
during the 300 baud hours specified in the system
configuration. It is used to notify the user that
there is a restriction (See no300.msg also).
OB zipft.bat This batch file performs archive integrity checking
for "*.ZIP" files. It is called whenever such a
file is uploaded. See the automatic archive
checking section of this documentation for more
information. See the file "notest" also.
=========================================================================
October 1, 1990 Page 20
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/==============================\
< T.A.G. Command Line Parameters >
\==============================/
Two command line parameters are available when booting the system. The
first is a one time option allowing the SysOp to change the
communications port used when booting the system. The second is used to
specify an alternate location for the status.dat file other than the
current directory. Both these parameters CANNOT be used at the same
time.
Changing the Communications Port
This parameter is only used when accidentally assigning an invalid
communications port in the system configuration, or when first putting up
a T.A.G. system on a computer which does not have a COM1 Port.
Usage:
TAG /COM1 - Boots the system and changes the communications port to COM1.
TAG /COM3 - Boots the system and changes the communications port to COM3.
Notes:
COM posts 3 & 4 are ONLY available if you are running a fossil driver.
After using these parameters once, the communications port default is
permanently changed in the system configuration and it is not
necessary to use it again.
Specifying an Alternate Directory for STATUS.DAT
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.
Usage:
TAG <Path Name> Replace <Path Name> with the complete path to the
directory containing the status.dat file.
=========================================================================
October 1, 1990 Page 21
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/====================\
< System Configuration >
\====================/
Accessing the System Configuration On-line
Time left: 07:58:35 ("?"=Help)
Main Menu: //SYSTEMCONFIG
Loading ...
FA? Yes
: XXXXXXXXXXXXXXXX
Alternately, the System configuration can be access via the wait screen,
or via the Control-Q HotKey, and selection (S)ystem Config.
<< 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
SysOp (A,B,D,E,F,L,M,P,S,U,V,Q=Quit): S
FA? Yes
: XXXXXXXXXXXXXXXX
When accessing the system configuration function on-line, a user is
prompted with "FA?". This questions whether 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 system
configuration 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.
=========================================================================
October 1, 1990 Page 22
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Description Of System Configuration Functions
A. System passwords.
B. System information.
C. The system is : Open
D. Sysop hours : None Defined
E. 300 baud hours : Always Allowed
F. Time limitations represent the: total time allowed for use each day.
G. Modem communications configuration.
H. Single value security settings.
I. General variables.
J. Optional flagged functions.
K. Time limitations ......................\\ Complete
L. Calls allowed per day ..................\\ range
M. Upload/download number of files ratio... >>
N. Upload/download K-bytes ratio...........// security
O. Post/call ratio .......................// settings.
System configuration: (A-O,Q=Quit):
=========================================================================
October 1, 1990 Page 23
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
A. System Passwords:
This allows you set any of the master system passwords or the new
user password. Only users with a SL of 255 can use this command
on-line. The third SysOp password can only be changed by calling
the system configuration from the wait screen.
1. SysOp password #1:
This password is used for remote logon of users above the SysOp
password #1 logon level, 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 (both
//BOARDEDIT and from the wait screen), file section manager (both
//DLBOARDEDIT and from the wait screen), events editor (//EVENTEDIT
and from the wait screen), limited system configuration access
on-line (//SYSTEMCONFIG), and the protocol editors (both //BATCH
and //SINGLE).
3. SysOp password #3:
This password is used for the menu editor (//MENUEDIT and from the
wait screen), full system configuration access (//SYSTEMCONFIG and
from the wait screen), shell to DOS command (PKey="."), the default
shut down system password (PKey="~"), 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.
=========================================================================
October 1, 1990 Page 24
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
B. System information:
1. System name: *A*R*T*H*U*R*
2. SysOp name : Victor Capton
3. Board phone: 313-879-2318
System Info (1-3,Q):
1. System name: This string specifies the name of the system
currently running. T.A.G. displays this field on
the wait screen 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 and to
check that a telephone entered for the user's voice
number is not that of the system.
C. Open/Closed Systems
The system is: 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".
D. Sysop Chat Hours
Sysop hours: This defines a time range when the SysOp is normally
available for a chat call. The system uses this
information to automatically turn the chat call
feature on and off. Using the SysOp available
toggle key (scroll lock) will override this setting
during times outside of this range. All times
should be entered in 24 hour format.
E. 300 baud hours: This defines the time range when 300 baud callers
are allowed on the system. The files no300.msg and
yes300.msg are used to inform the user of these
restrictions (see their file description for more
information).
=========================================================================
October 1, 1990 Page 25
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
F. Time Limitations
Time limitations represent <"... maximum time allowed for each call.
... total time allowed for each day.">:
This designates whether the time limitation information is on a per
call basis or a daily time limit from all calls made by a user. You
are prompted for your choice as follows:
What do you wish the time on-line to represent:
1) Time allowed per call
2) Time allowed per day
(<Q>=Quit):
=========================================================================
October 1, 1990 Page 26
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
<< Modem Communications Configuration >>
!. No call reinit time: 48 minutes
A. Com-port number : 1
B. Carrier Detect Mask: 128 (Non-FOSSIL only)
C. Wait modem speed : 9600 (Variable)
D. Use FOSSIL driver : No
E. Modem initialization string:
"AT&F|~~~~ATH0Q0V0E0M0X7S2=2S10=10&A1&M4|"
F. Modem answer string : "ATA"
G. Modem hangup string : "~~~~^A^A^A~~~ATH0"
H. Modem offhook string: "ATH1M0"
I. Modem after hangup string: "ATH1"
J. Modem result codes:
Case 1 Case 2
OK : "0"
RING : "2"
NO CARRIER: "3"
300 : "1" ""
1200 : "5" "15"
2400 : "10" "16"
9600 : "13" "17"
Modem: (!,A-J,Q=Quit):
!. No call reinit time:
This value defines the number of minutes of inactivity between
calls before T.A.G. will reinitialize the modem - a handy feature
for SysOps who accidentally leave the modem off-hook often!
A. Com-port Number:
This value defines the communication port to which the modem is
connected. Communication ports COM1 through COM4 are supported at
this time.
Note: Most systems only have one communications port, in this case
it is usually COM1.
WARNING: If you should somehow set the Com-Port Number to an
inactive communications port, causing the system to refuse
to boot, T.A.G can be restarted by using the "/COMx"
command line parameters to switch ports (replacing x with
the Com Port Number, i.e. "/COM2"). See the command line
parameters section for more information.
=========================================================================
October 1, 1990 Page 27
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
B. 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".
C. Wait modem speed:
This number defines the speed at which the system sends modem
commands and waits for a caller. For most modems this is the
highest baud rate available, but a few brands may require another
value (my old 1200 baud modem preferred commands at 300 baud, and
in fact produced random problems if 1200 was used). The wait speed
can be defined as Variable, meaning that communication between the
modem and the hardware will occur at the caller's baud rate or
Locked, which indicates that this communication will occur at
specified baud rate (usually 19,200 or 38,400 baud) regardless of
the caller's connect rate.
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. If a baud rate above 9600
has been selected (as described in the previous paragraph), a
FOSSIL driver MUST be used. Baud locking implements CTS/RTS
hardware flow control.
E. Modem initialization string:
This defines the modem string which prepares the system for
incoming calls. The string presented here will work with the HST
9600 baud modem and the string "ATH0Q0V0E0M0&D2S0=0S2=1S10=10" will
work with most 2400 and 1200 baud modems. However, there is no
guarantee that your modem supports all of these commands. The
phrase "Hayes Compatible" doesn't mean much these days.
WARNING: Do <<NOT>> enable the auto-answer feature on your modem to
run the T.A.G. bulletin board system. The board answers
the modem itself and will not function properly with
auto-answer enabled.
=========================================================================
October 1, 1990 Page 28
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 : Configures 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)
F. Modem answer string:
This string is sent to the modem in response to an incoming call.
AT : Attention modem
A : Answer the phone
=========================================================================
October 1, 1990 Page 29
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
G. Modem hangup string:
This string is sent to the modem in order to disconnect the line,
and thus hang up on the user. This string is sent only when the DTR
signal to drop the carrier is ignored by the modem.
~~~~ : Pause 2 seconds
^A^A^A : Send 3 control-A's to return to local mode
~~~ : Pause 1.5 seconds
AT : Attention modem
H0 : Put the phone on-hook (hangup)
H. Modem offhook string:
This string is sent to the modem when it is necessary to busy the
phone line. It is used during scheduled events which require the
modem to be off-hook, upon execution of the off-hook command from
the wait screen and when logging on locally when the "auto
off-hook" option has been set to active in the system
configuration.
AT : Attention modem
H1 : Take the phone off-hook
M0 : Turn the modem speaker off
I. Modem after hangup string:
This string is sent to the modem after the user has logged off of
the system. It can be used to take the modem off hook to prevent
an incoming call until the mailer program reinitializes the modem
(if used).
AT : Attention modem
H1 : Take the phone off-hook
=========================================================================
October 1, 1990 Page 30
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
J. Modem result codes:
These settings define the modem strings which are used by T.A.G. to
understand what the modem is saying. "Case 2" results are normally
only used in the case of an error correcting modem which often
returns another set of result codes when a user who also has an
error-correcting modem calls. (e.g. MNP modems often have
different result codes for MNP connections)
OK : Indicates that the command line executed contained
no errors.
RING : Indicates that a ring signal was detected (the phone
just rang).
NO CARRIER : Indicates that an attempt at a connection with a
remote caller failed and the modem is now back
on-hook (it hung up).
300 : Indicates a 300 baud connection.
1200 : Indicates a 1200 baud connection.
2400 : Indicates a 2400 baud connection.
9600 : Indicates a 9600 baud connection.
You are given the following sub-menu when choosing this item:
Modify result codes for which response ?
A) OK B) RING C) NO CARRIER
1) 300 2) 1200 3) 2400 4) 9600
Result code: (A-C,1-4,Q=Quit):
=========================================================================
October 1, 1990 Page 31
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
H. Single value security settings.
<< Single value security settings >>
1. SL-Full SysOp :250 2. SL-CoSysOp of system :200
3. ISL-SubOp of message system :199 4. DSL-Download system CoSysOp :200
5. DSL-No download ratio check :200 6. SL-Add a system to BBS list: 11
7. SL-Send normal private mail: 11 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:200 12. SL-Send anonymous private :200
13. RSL-See passwords remotely :255 14. SL-No post/call ratio check:200
15. SL-Privilege :50 16. DSL-Privilege : 30
17. DSL-No download point check :200 18. SL-SysOp password #1 logon :250
19. SL-Read text file into msg :200 20. SL-Read msg validate cmd :200
21. SL-Read msg user view cmd :200
!. AR-Post/call key flag :@
@. SL/AR - Sysop menu :255/Z
Security: (1-21,!,@,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. SubOp of message system:
The specific SL required for a user to be a SubOp of all message
sections. Please note this is only at this specific SL and not above.
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.
=========================================================================
October 1, 1990 Page 32
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.)
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.
=========================================================================
October 1, 1990 Page 33
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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 in the
message editor.
20. Read msg validate cmd:
The minimum SL required before a user can validate a user who sends
them a private message (the (V)alidate command from private mail
read).
21. Read msg user view cmd:
The minimum SL required before a user can view another user's
information who sends them a private message (the (U)ser command from
private mail read).
!. 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.
@. 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.
=========================================================================
October 1, 1990 Page 34
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
I. General variables.
<< General variables >>
1. Max private sent per call :20 2. Max feedback sent per call :10
3. Max public posts per call :25 4. Max mail waiting normal :20
5. Max mail waiting CoSysOp :75 6. Max mail waiting SysOp :100
7. Number back SysOp log days :14 8. Number days keep Usage Log :95
9. Max number of logon tries :5 10. Percent upload time refund :50%
11. Normal max lines/message :120 12. CoSysOp max lines/message :160
13. Maximum pages per call :2 14. Starting logon menu number :1
15. Minimum K-Bytes to post :50 16. Minimum K-Bytes to upload :200
17. Maximum number of users :600 18. Maximum files batch download:30
19. Maximum files batch upload :20 20. Number of novice msg days :30
21. Max daily time bank deposit :30 22. Max daily time bank withdraw:60
23. Maximum time in time bank :120
A. Main data file directory :"C:\BBS\GFILES\"
B. Alternate text file directory:"C:\BBS\AFILES\"
C. Message text file directory :"C:\BBS\MSGS\"
D. Swap file directory :"C:\BBS\SWAP\"
E. Swap shell is normally : Active (not allowing use of EMS memory)
F. High message pointer : (A):A (B):-32767 (C):1
G. Chat colors
General variables: (1-21,A-G,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. Max mail waiting normal:
The maximum number of private messages normal users may have waiting
in their mailbox at one time.
5. Max mail waiting CoSysOp:
The maximum number of private messages a CoSysOp may have waiting in
their mailbox at one time.
=========================================================================
October 1, 1990 Page 35
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
6. Max mail waiting SysOp:
The maximum number of private messages a SysOp may have waiting in
their mailbox at any one time.
7. 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).
8. 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.
9. 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.
10. 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.
11. Normal max lines/message:
The number of lines available to a normal user with less than a
CoSysOp to write a message. Note: This is mainly here for ANSI
message support; large ANSI graphic screens eat up lines fast. If you
are interested in these screens, set this value very high.
12. CoSysOp max lines/message:
This is the same as the above option, except this determines how many
lines users with a SL of CoSysOp or above have to write messages.
13. 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).
14. Starting logon menu number:
The menu at which users logging onto the system are first sent to.
15. 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.
=========================================================================
October 1, 1990 Page 36
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
16. 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.
17. 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.
18. 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.
19. 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.
20. Number of novice msg days:
The number of times that the file novice.* is displayed to a new user.
21. Maximum daily time bank deposit:
The maximum amount of time, per day, that a user is allowed to deposit
in the time bank.
22. Maximum daily time bank withdraw:
The maximum amount of time, per day, that a user can withdraw from the
time bank.
23. Maximum time in time bank:
The highest amount of accumulated time which can exist in a user's
time bank.
=========================================================================
October 1, 1990 Page 37
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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, etc).
C. Message text file directory:
This string is the complete path name of the Message Text File
Directory, which contains the textual part of all messages.
D. 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.
This feature requires that T.A.G. be placed in either on disk or in
Lotus/Intel/Microsoft Extended Memory Specification (EMS) memory while
swapped out. This string contains the pathname where T.A.G. will
remain until the shell program is complete if the disk option is
chosen (see the following paragraph). Approximately 200K of space is
required and unpredictable events may occur if available space falls
below this level.
E. Swap shell active/inactive:
This defines whether the swapping feature discussed in the previous
paragraph is active or not. If it is active, either EMS or disk
(including RAM disk) may be selected. If disk is selected, the
pathname discussed in the previous paragraph is used to hold T.A.G.
during a shell. Note: use of a hard disk for swapping will likely
significantly increase the amount of time required to shell out and
back. Use of a floppy disk is not permitted.
The swap shell system can be toggled ON or OFF, depending on the
configuration setting, for all calls to external programs. This would
come in handy, for example, if you have a normally slow hard drive and
wish to run a large door program. You can leave the swap shell OFF in
the system configuration and turn it ON for the doors in question
only.
To use this feature, place a "~" in front of the file name where ever
it is specified (PData, Protocols, etc). Note that this option toggles
the setting in the system configuration for this file. If your swap
shell is normally OFF, this will turn it ON. However if your swap
shell if normally ON, this will turn it OFF.
=========================================================================
October 1, 1990 Page 38
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
F. High Message Pointer:
These settings may be adjusted in order to fix message pointer
problems since doing so changes the message filenames assigned by
T.A.G. Incorrect use of this command may result in private mail
messages appearing in public (or vise-versa), the same message
appearing in more than one message area and/or the existence of
several "File not found" messages. Accordingly, these settings should
never be changed unless you know exactly what you are doing.
G. Chat colors:
This allows a user to change the defined ANSI colors used in chat for
both the SysOp and the users.
=========================================================================
October 1, 1990 Page 39
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
J. Optional flagged functions.
<< Optional flagged functions >>
A. Title screen pause :No B. Blank off-line wait screen :No
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 :1 H. SysOp mail forwarded to user:1
I. Minutes before time out :4 J. Minutes before time out bell:3
K. Guest user number :419 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 :On W. Screen snow checking :No
X. Try to use EMS for overlays :No Y. Instant logon key :Yes
Z. Local Security :No 1. Show available upload space :Off
2. Show GIF resolution :Yes 3. Force scan before upload :Off
4. Local logon SysOp window :Off
Flagged functions: (A-P,R-Z,1-4,Q=Quit): Q
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.
=========================================================================
October 1, 1990 Page 40
T.A.G. BBS Version 2.5f 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.
=========================================================================
October 1, 1990 Page 41
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 I advise
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.
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
GFILES 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.
=========================================================================
October 1, 1990 Page 42
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
=========================================================================
October 1, 1990 Page 43
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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
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.
=========================================================================
October 1, 1990 Page 44
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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
"intellegent" 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
procede anyway or to cancel the upload. If disabled, only the
current section is scanned for an exact filename match.
4. Logon 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.)
=========================================================================
October 1, 1990 Page 45
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
K. 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 the example below for
basic usage of range commands.
L. Calls allowed per day:
This defines, for each SL, the number of calls that are allowed per
day. See the example below for basic usage of range commands.
M. 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 the example below for basic usage of range
commands.
N. 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 the example below for basic usage of range
commands.
O. 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 the example below for
basic usage of range commands.
=========================================================================
October 1, 1990 Page 46
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Range setting command information for options "K" through "O":
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):
S:et
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.
T:oggle
This command switches the display between the table displaying
values for entries 0-132 or values for entries 133-255.
=========================================================================
October 1, 1990 Page 47
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/============================\
< The Access Validation Editor >
\============================/
<< 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
SysOp (A,B,D,E,F,L,M,P,S,U,V,Q=Quit): A
: XXXXXXXXXXXXXXXX
## Key SL DSL AR flags SF flags FPoint TmBank Credit
-- --- --- --- -------------------------- --------------- ------ ------ ------
You have been validated, enjoy the system!
1 A 50 50 -------------------------- --------------- 0 60 0
You have been validated, enjoy the system!
2 S 100 100 ------------------S------- ------G-------- 0 360 0
Validation Records: (D:elete,I:nsert,M:odify,P:osition,Q:uit):
When accessing the access validation editor on-line, a user is prompted
for Sysop password #3.
=========================================================================
October 1, 1990 Page 48
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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 TAG:
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.
=========================================================================
October 1, 1990 Page 49
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/===========================\
< 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.
/============================\
< 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 : A
2. Description:
You have been validated, enjoy the system!
3. SL : 50
4. DSL : 50
5. AR flags : --------------------------
6. SF flags : ---------------
7. Time bank : 60 minutes
8. File points: 0 points
9. Mail credit: 0 cents
Validation edit: (1-9,[,],B,J,T,Q,?):
=========================================================================
October 1, 1990 Page 50
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/========================\
< Validation Edit Commands >
\========================/
Validation Edit Help:
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.
/==============================\
< 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
=========================================================================
October 1, 1990 Page 51
T.A.G. BBS Version 2.5f 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).
Alternately, the User Editor can be accessed at the wait screen or from
any menu with the board through the Control-Q HotKey, and selection
(U)ser Editor which requires password #1.
<< 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
SysOp (A,B,D,E,F,L,M,P,S,U,V,Q=Quit): U
: XXXXXXXXXXXXXXXX
A third method of accessing the user editor is through the use of the
Control-U command. Control-U is available from 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.
=========================================================================
October 1, 1990 Page 52
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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".
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.
=========================================================================
October 1, 1990 Page 53
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
=========================================================================
October 1, 1990 Page 54
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 current 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.
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.
=========================================================================
October 1, 1990 Page 55
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Extended User Listing Description
Which list mode: (S)hort, (N)ormal, (E)xtended, <CR>Default: E
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 : Password :"LEMMEIN"
Call spread :0,0,0,0,0,1,0,1,0,0,0,0,0,0,0
Mail waiting :13 Last called on:11:36:30 pm Tue Jun 05, 1990
Screen size :80x23 Forward mail :Disabled Highest baud :9600 bps
Total calls :20 Total time on :14756 Time on today :0 mins
Calls today :0 Illegal logons:0 MSG base SubOp :None
Public posts :155 Private posts :788 Feedback to SysOp:1
Help level :1 PostCall ratio: 10.0 calls / 1 post
External edit:Ask Downloads :4 files - 108k Points :0
Last MSG base:1 Uploads :1 files - 200k TimeBank:360
Last DL base:105 UL/DL ratio :None (special flag)
Flags:CLS:Off ANSI:Off Color:Off Pause:Off Custom :Off Debits :0
Tabs:Off Alert:Off Input:OneKey Mailbox:Forward Credits:0
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.
=========================================================================
October 1, 1990 Page 56
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
<<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.
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.
=========================================================================
October 1, 1990 Page 57
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
Normal User Listing Description
Which list mode: (S)hort, (N)ormal, (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.
=========================================================================
October 1, 1990 Page 58
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Abbreviations used in normal 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.
Short User Listing Description
Which list mode: (S)hort, (N)ormal, (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 two previous user listings for a description of the usual fields.
=========================================================================
October 1, 1990 Page 59
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
User Editor Main Command Descriptions
User edit (?=Help): ?
(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.
=========================================================================
October 1, 1990 Page 60
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
(/) 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):
Tagged change (?=Help): ?
(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
Tagged change (?=Help):
({) 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, or extended mode.
=========================================================================
October 1, 1990 Page 61
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
(-) 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:
Clear (A,B,C,G,P,R,T,Z,Q=Quit,?): ?
(A)ddress (B)aud rate (maximum) (C)ity & State
(G)Birthday (P)hone number (Q)uit
(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.
(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.
=========================================================================
October 1, 1990 Page 62
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
(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. An option
also exists to disable the auto-list mode in case you have a great
number of changes.
User edit (?=Help): N
Which list mode: (S)hort, (N)ormal, (E)xtended, <CR>Default: N
Autolist mode (Y/N)? No
(O) Options menu:
This command is used to create 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.
User edit (?=Help): O
-=[ 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.
=========================================================================
October 1, 1990 Page 63
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 #, and SysOp note. This command is very handy when
you forget a user's handle but remember some other piece
information about them.
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.
=========================================================================
October 1, 1990 Page 64
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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).
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)).
=========================================================================
October 1, 1990 Page 65
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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:
=========================================================================
October 1, 1990 Page 66
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Options Menu (?=Help): T
Tagged user set operations:
Set A: Currently tagged users
Set B: Users match current options
Use what 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.
Tag type: (1-4,Q=Quit):
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.
=========================================================================
October 1, 1990 Page 67
T.A.G. BBS Version 2.5f 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.
=========================================================================
October 1, 1990 Page 68
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
(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.
(Y) Message base SubOp:
This command allows you to specify up to four message sections that
the current user will have SubOp access to. SubOp's can move or
delete any message in the specified section(s) that they wish.
(0) Mail posts/waiting:
This command allows you to change the following mail statistics:
User edit (?=Help): 0
(1)Private posts (2)Public Posts
(3)Feedback (4)Mail waiting
Mail (1-4,Q=Quit):
=========================================================================
October 1, 1990 Page 69
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
(!) 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
the TAGMail Matrix/Echo system. These fields are not used if
TAGMail is not being used. Credit represents the number of cents
the user has paid to the system for matrix mail 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.
(+) 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.
=========================================================================
October 1, 1990 Page 70
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/========================\
< The Message Board Editor >
\========================/
## Name Filename SL AR PSL MaxM Anon Password
-- ======================== ============ === == === ---- ---- --------
0 SysOp Base SYSBASE 200 10 50 No
1 General Messages GENERAL 10 10 50 Yes
2 Music Conference MUSIC 30 30 50 Yes
3 Ideas/Suggestions IDEAS 10 10 50 Yes
..
..
13 RPG Information RPGINFO 30 30 50 Yes
MSG Boards: (D:elete,I:nsert,M:odify,P:osition,Q:uit): M
Board number to start editing (0-19): 1
Board : 1
1. Name: General Messages
2. File name: GENERAL
3. SL: 10
4. AR flag: @
5. Post SL: 10
6. Anonymous: Yes
7. Max Messages: 50
8. Password: ""
9. Allow ANSI: On
MSG Board Edit: (1-9,[,],B,J,T,Q,?):
Board:
This field holds the number of the message base currently being
edited.
1. Name:
This field contains the section name for the message section that
appears in the menu prompt.
2. File name:
This field contains the file name where the header information of
the messages is stored. These files appear in the Main Data File
Directory and have an extension of ".BRD".
3. SL:
This field indicates the SL needed to access the message section.
=========================================================================
October 1, 1990 Page 71
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
4. AR flag:
This field indicates the AR flag needed to access the message
section. An AR flag of "@" means there is no AR restriction.
5. Post SL:
This field specifies the SL needed to post a public message in the
message section. You may, for example, set up an RPG (Role Playing
Game) section that normal users can read, but only RPG players can
post in.
6. Anonymous:
This field indicates whether anonymous messages are allowed in a
message section, and if so whether they are forced or not.
7. Max Messages:
This field indicates the maximum number of messages allowed in the
message section. This may be a number up to 200 messages. Messages
posted after the maximum number is reached will auto-delete the
first/oldest message. If the maximum number of messages is reduced
below the actual number of messages in the section, the system will
automatically delete any excess messages when the next message is
posted. NOTE: The messages will NOT be deleted until the next
post.
8. Password:
This field indicates the password needed to enter or read messages
in the message section.
9. Allow ANSI:
This flag indicates whether ANSI (Control-P and ESC (27 dec) codes)
characters are allowed in the message section.
=========================================================================
October 1, 1990 Page 72
T.A.G. BBS Version 2.5f 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 Public Domain Games 30 @ C:\BBS\PDGAMES\
4 Public Domain Utilities 30 @ C:\BBS\PDUTIL\
..
..
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. DSL: 10
6. AR flag: @
7. Password: ""
8. See names DSL: 240
9. No ratio: Off
DL Board Edit: (1-9,[,],B,J,T,Q,?):
=========================================================================
October 1, 1990 Page 73
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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 Gfiles 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.
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. DSL:
This field indicates the DSL needed to access the file section.
6. AR flag:
This field indicates the AR flag needed to access the file section.
An AR flag of "@" means there is no AR restriction.
7. 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.
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.
The system currently supports a maximum of 174 file sections.
=========================================================================
October 1, 1990 Page 74
T.A.G. BBS Version 2.5f 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.
<< 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
SysOp (A,B,D,E,F,L,M,P,S,U,V,Q=Quit): E
: XXXXXXXXXXXXXXXX
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 (continous). 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 a 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.
=========================================================================
October 1, 1990 Page 75
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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"
<<< 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 existance 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.
=========================================================================
October 1, 1990 Page 76
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
6. Permission/restriction:
This filed may be toggled between Permission and Restriction
depending on the type of internal event desired.
7. Logon/chat:
This filed may be toggled between logon and chat depending on the
type of internal event desired.
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.
=========================================================================
October 1, 1990 Page 77
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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:
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.)
=========================================================================
October 1, 1990 Page 78
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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."
<<< 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:
=========================================================================
October 1, 1990 Page 79
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
=========================================================================
October 1, 1990 Page 80
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
You don't always have to define a message for an event. Too many
messages and/or conflicting messages can easily overwhelm a user,
especially a new user. When defining messages, consider that multiple
logon permission events could produce the following litany:
You do not have access to the games area.
You do not have access to the files area.
You can upload.
The SysOp is NOT Available.
Your time has been adjusted to 10 minutes.
You can download.
You may play trade wars now.
Obviously, some of the above messages conflict with each other, since
being able to upload and download normally requires access to the files
area and playing Trade Wars usually will require access to the games
area. Worse yet, it is possible to have the following happen:
You have access to the games area.
You do not have access to the games area.
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
specified time not that 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).
=========================================================================
October 1, 1990 Page 81
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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 :Restrict out of balance weekdays
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
; MAKE SURE WE'RE IN PROPER DRIVE/DIRECTORY
C:
CD \BBS
;START UP BBS
TAG
;T.A.G. HAS HALTED - IS IT AN EVENT?
IF ERRORLEVEL 25 GOTO MAINT
;NO. DROPPED FOR OTHER REASON. RESTART T.A.G.
GOTO START
;MAINTENANCE EVENT - RUN THE MAINTENANCE PROGRAMS
:MAINT
TWMAINT
TODAYBBS
;EVENTS PROCESSED - RESTART T.A.G.
GOTO START
=========================================================================
October 1, 1990 Page 82
T.A.G. BBS Version 2.5f 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)
=========================================================================
October 1, 1990 Page 83
T.A.G. BBS Version 2.5f 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,?):
=========================================================================
October 1, 1990 Page 84
T.A.G. BBS Version 2.5f 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\GFILES). 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. Internal protocols and
non-protocol commands do not use this field.
=========================================================================
October 1, 1990 Page 85
T.A.G. BBS Version 2.5f 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 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. no longer
supports internal protocols. With the large number of shareware
external protocol packages available (particularly DSZ) T.A.G. has
been made much more effective and requires considerably less memory
by relying on external protocols. The latest version of DSZ is
highly recommended.
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
:
=========================================================================
October 1, 1990 Page 86
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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):
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.
=========================================================================
October 1, 1990 Page 87
T.A.G. BBS Version 2.5f 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
=========================================================================
October 1, 1990 Page 88
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Path names DO NOT end in a backslash (e.g. C:\BBS\GFILES). 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.
=========================================================================
October 1, 1990 Page 89
T.A.G. BBS Version 2.5f 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. (T.A.G. no
longer supports internal batch protocols; xternal protocol such
as DSZ and required). 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 (ignore the word
wrapping of the lengthy download string):
=========================================================================
October 1, 1990 Page 90
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
7. (U)L string: ""
(D)L string: "protocol.bat clink T [Directory]\[Filename]
[Directory]\[Filename] [Directory]\[Filename]
[Directory]\[Filename] [Directory]\[Filename]
[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.
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.
=========================================================================
October 1, 1990 Page 91
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
=========================================================================
October 1, 1990 Page 92
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
=========================================================================
October 1, 1990 Page 93
T.A.G. BBS Version 2.5f 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, *.BRD, *.DAT, *.DIR, and *.LOG
files. There is no reason for a user to do anything with these
files, so they are protected.
=========================================================================
October 1, 1990 Page 94
T.A.G. BBS Version 2.5f 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. There are a total
of 30 programmable strings contained in three text files. The strings are
stored in the files using one line apiece.
T.A.G. color codes (Control-C follow by a color number "0" to "9") are
completely supported (see the "Other SysOp & CoSysOp functions and hints
on using the system" section for information on color codes). 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.
If present these files should be placed in the Main BBS Directory.
The Mini-DOS text editor is excellent for editing there files, as it does
support Control-P type colors as in messages.
=========================================================================
October 1, 1990 Page 95
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
COMMSTR.TXT: This file contains 12 strings which are displayed in all
sections of the system. It is ONLY loaded when booting the
system so changes made to it will not appear until the
board is rebooted.
#### MaxChars Description
---- -------- ---------------------------------------------------------
* 1 45 "[PAUSE]" string. Displayed when the system pauses
between each page of information to give the user time to
catch up reading, and then press any key.
* 2 45 "[WAIT]" string. Displayed when the SysOp is doing
something while a user is on-line. For example: Changing
the SL, DSL, AR flags, or special flags on a user.
* 3 45 "One moment please ..." string. Displayed when the SysOp
drops to DOS without the user, or disables the
communications port.
4 45 "Thank you" string. Displayed after the preceding string
to tell the user the SysOp is done and the user has
control again.
* 5 45 ">><*><<" string. Displayed when paging the SysOp each
time the bell is sounded.
6 90 "How about sending the SysOp a letter instead." string.
Displayed only when the SysOp does not answer the chat
call. The system may optionally allow the user to leave
the SySOp a message.
7 90 "Enter a short reason" string. Displayed when the system
asks the user for a reason to page the SysOp.
8 90 "Paging system operator, please hold ..." string.
Displayed to indicate the system is now going to page the
SysOp.
9 90 "Entering chat mode ..." string. Displayed when the SysOp
enters the chat mode.
10 90 "Leaving chat mode ..." string. Displayed when the SysOp
exits the chat mode.
* 11 90 "Are you sure you want to log off ? (Y/N) : " string.
Displayed when the user chooses the normal log off command
to verify this is really what they wanted to do.
* 12 90 "Would you like to leave the SysOp a Comment ? (Y/N) : "
string. Displayed when logging off to ask whether the user
wishes to leave the SysOp a comment before logging off.
=========================================================================
October 1, 1990 Page 96
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
MAINSTR.TXT: This file contains 9 strings which are displayed in the
main system. This file is loaded every time the main
system is loaded (e.g. Leaving the file section and
loading the main system will reload this file).
#### MaxChars Description
---- -------- ----------------------------------------------------------
* 1 90 "Would you like an ANSI logon screen (Y/N)? " string.
Displayed when a user first calls. The system may ask
whether they want an ANSI logon screen.
2 90 "To be a guest on the system enter "GUEST" as your user
name" string. Displayed as the first line of the system
logon prompt when the guest user option is active.
3 90 "New users enter your first & last name or handle" string.
Displayed as the first line of the system logon prompt
when new users are allowed on the system.
* 4 90 "Enter user name or ID number: " string. Displayed as the
main entry line when users logon to the system and when
sending private mail.
5 90 "Name NOT found in user log." string. Displayed when the
name entered at the logon prompt was not found in the user
log.
6 90 "Please enter your real name or handle" string. Displayed
when a guest user is asked to enter a unique name for the
system records.
* 7 90 "Enter bulletin ID, <?> to List, or <CR> to Quit? "
string. Displayed after printing the list of bulletins to
ask the user what they wish to do.
8 90 "Thank you for taking the time to vote." string. Displayed
after a user leaves the voting section and has voted on at
least one question.
* 9 90 "Enter questionnaire ID, <?> to List, or <CR> to Quit? "
string. Displayed after printing the list of
questionnaires to ask the user which questionnaire s/he
would like to access.
=========================================================================
October 1, 1990 Page 97
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
FILESTR.TXT: This file contains 9 strings which are displayed in the
file system. This file is loaded every time the file
system is loaded (e.g. Going to the file system from the
main system will reload this file).
#### MaxChars Description
---- -------- ----------------------------------------------------------
1 90 "Search all directories for a file mask." string.
Displayed when the user chooses the (S)can all directories
command.
2 90 "Enter the string to search descriptions for." string.
Displayed when the user chooses the (F)ind description
command.
3 90 "<CR> for all files" string. Displayed when the user is
(L)isting the files of a section to describe their options
for a file mask.
4 90 "Enter file to list interior files of" string. Displayed
when the user chooses the (I)nterior list command to list
the files inside an archive or library file.
5 90 "Download -" string. Displayed when the user chooses the
(D)ownload file command.
6 90 "Your upload/download ratio is out of balance:" string.
Displayed when a user attempts to download a file when
their file ratio is out of balance. It begins the
description of violations.
7 90 "Access denied." string. Displayed when a user attempts to
download a file when their file ratio is out of balance.
It ends the descriptions of violations.
8 90 "You do not have enough file points to download this
file." string. Displayed when a user attempts to download
a file their does not have enough file points to download.
9 90 "File added to batch queue." string. Displayed when a
user chooses the batch option on the protocol menu to
indicate that the file was added into their batch list.
=========================================================================
October 1, 1990 Page 98
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/=================================\
< System Data Reference (SDR) Codes >
\=================================/
T.A.G. provides the means to display selected data about the current user
and selected system data items through the use of System Data Reference
(SDR) Codes in text files. To display the appropriate system or user
variable, the SysOp places a two character SDR code at the place in the
text file where the variable is to displayed.
User Data (SDR Control-U Codes):
An SDR code related to user data consists of a control-u followed
by a (case insignificant) letter corresponding to the desired user
data as shown in the table below. Please note that in most cases,
the SDR code parallels the user editor code.
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 : Last On Date/Time
M : Mailbox Status P : Phone R : Real Name
S : Security Level T : Computer Type U : User First Name
X : Screen (Rows/Cols) Y : Msg. Base SubOp 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 # : User Number $ : Debit / Credit
^ : Points @ : Time Bank
System Data (SDR Control-S Codes):
An SDR code related to system data consists of a control-u followed
by a (case insensitive) letter corresponding to the desired user
data as shown in the table below.
A : Alternate Files Path B : Board Name C : Last Caller
D : Last Date E : Errors Today G : Gfiles Path
H : Number of Users Today M : Messages Path N : Caller Number
P : Board Phone S : Sysop Name U : Multi-user path
X : Number of Users Z : Chat Password
1 : Maximum Batch DLs 2 : Maximum Batch ULs 3 : UL K-bytes today
4 : DL K-bytes today 5 : Num Calls Today 6 : Msgs Posted Today
7 : E-mail Today 8 : Feedback Today 9 : Uploads Today
0 : Downloads Today # : Node Number
Display Control (DC) 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 ot the text file.
=========================================================================
October 1, 1990 Page 99
T.A.G. BBS Version 2.5f 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.
=========================================================================
October 1, 1990 Page 100
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
NOTE:
The user's name is NOT displayed on the bottom of the screen. Not
only does this feature require registration of the product, but the
documentation as to the format of the file which QuickED gets this
name from is just about non-existent. Anyone with information on what
this file looks like, please contact Victor Capton.
=========================================================================
October 1, 1990 Page 101
T.A.G. BBS Version 2.5f 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\gfiles\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.
=========================================================================
October 1, 1990 Page 102
T.A.G. BBS Version 2.5f 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\gfiles\bullet15.msg
copy tf-crypt.rpt c:\bbs\gfiles\bullet16.msg
copy tfdetail.rpt c:\bbs\gfiles\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.
=========================================================================
October 1, 1990 Page 103
T.A.G. BBS Version 2.5f 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 reboots 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.
=========================================================================
October 1, 1990 Page 104
T.A.G. BBS Version 2.5f 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 TAG 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 TAG resides on your
system. "watchdg1 on", "ctty aux1", "watchdg1 off" may change depending
on which communications port your system uses.
=========================================================================
October 1, 1990 Page 105
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/===========================================\
< 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 value. 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=3,8.
/=====================================\
< Automatic Archive Checking of Uploads >
\=====================================/
T.A.G. can very easily check all uploads in either ZIP, ARC, or PAK
format for integrity immediately after the upload is complete. This is
done by calling ZIPFT.BAT, ARCFT.BAT, PAKFT.BAT and LZHFT.BAT
respectively and passing the full pathname of the uploaded file as the
only parameter.
Sample batch files:
ZIPFT.BAT:
pkunzip -t %1
ARCFT.BAT:
pkunpak -t %1
PAKFT.BAT:
pak /t %1
LZHFT.BAT:
lharc t %1
Note: PKUNPAK was previously called PKXARC in early versions.
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.
=========================================================================
October 1, 1990 Page 106
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
/=========================================================\
< Interfacing your System with the Matrix/Echo Mail Network >
\=========================================================/
Through the use of TAGMail, an external mail processing program written
by Mike VanderVeer, users can take advantage of the full capabilities of
the Matrix/Echo mail world. This is a separate program which should be
available on those systems running it, documentation should be included.
Several other programs (Binkley Term (tm) for one) are required for a net
mail system. These programs are listed in the TAGMail documentation
also.
What is this stuff:
Echo mail:
These message sections are giant public message areas seen on a
large number of systems. Any messages posted on each system
carrying an echo will eventually filter onto all the systems
networked. A list of available echo mail sections in your echo
should be available from your regional coordinator. Contact someone
already running echo mail if you do not know who that is.
Matrix/Net mail:
This type of mail is normally (but not required to be) private
mail. These message go directly to a particular person on a
specified system. It is also possible to send or request files
using these messages from other systems running a similar system.
Hundreds of outside written utilities exist use these message to
perform many other tasks also.
=========================================================================
October 1, 1990 Page 107
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
Advantages of setting up a mailer system:
- Expand your message system with many of the hundreds of local,
national, or international public message sections.
- Allow the use of many of the advanced features such as attaching
files to messages, or requesting files from another system, etc.
- Make use of hundreds of outside written utilities for automated
processing of information/files. TAGMail uses the standard
Matrix/Echo mail format so virtually all of the utilities written
for standard net mail will operate.
- Automatic distribution of information without having to log onto
the system(s) in question. When set up the mailer programs
automatically send and receive mail and/or files during the night.
- Your system can be set up to receive the T.A.G. and TAGMail
national echos.
- Posts in any echo mail sections can attract new callers to your
system, as every message posts contains information about the
origin system (your board in other words).
- It is a whole new world out there !!
Disadvantages of setting up a mailer system:
- The disk space required is often quite extensive. It really
depends on the Echo mail sections you bring into your system, but
even a minimum system requires several megabytes of storage.
- System usage will be affected even if your system does not handle
many high traffic Echo mail sections. Processing times for mail on
XT class machines can be lengthy on slow hard drives.
- When too many systems are running Matrix/Echo locally, boards tend
to become more generic because the same messages can be read on any
of the systems.
=========================================================================
October 1, 1990 Page 108
T.A.G. BBS Version 2.5f 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 (ie.
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.
=========================================================================
October 1, 1990 Page 109
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
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.
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.
=========================================================================
October 1, 1990 Page 110
T.A.G. BBS Version 2.5f 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.
=========================================================================
October 1, 1990 Page 111
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
[> 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.
[> 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
=========================================================================
October 1, 1990 Page 112
T.A.G. BBS Version 2.5f Main Documentation
=========================================================================
[> 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 now 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)
=========================================================================
October 1, 1990 Page 113