TAGCFG v1.50 Standard
(c)1994 TNT Software
NOTE: Anything preceded with a "|" denotes that it has been updated
since the last copy of the program was released!
Program and program documentation written by Joe McElmeel.
Table of contents
1 Legal Notice . . . . . . . . . . . . . . . . . . . . . . . . .
2 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 System requirements . . . . . . . . . . . . . . . . . .
2.2 Warranty . . . . . . . . . . . . . . . . . . . . . . . .
2.3 What TAGCFG does . . . . . . . . . . . . . . . . . . . .
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Location of files . . . . . . . . . . . . . . . . . . .
3.2 Command line options . . . . . . . . . . . . . . . . . .
3.3 Editing the STATUS.TXT . . . . . . . . . . . . . . . . .
4 Uses of TAGCFG . . . . . . . . . . . . . . . . . . . . . . . .
5 Technical information . . . . . . . . . . . . . . . . . . . .
6 Support information . . . . . . . . . . . . . . . . . . . . .
7 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .
1 Legal Notice
TAGCFG is copyrighted software but you are free to distribute it as long
as all files remain in their original, unmodified state, and then PKZIP -AV
(authenticity verification) stays in-tact.
You can use TAGCFG as much as you want, for as long as you like as long as
you do not attempt to "hack" the software or modify the distribution arch-
ive and distribute a modified copy of the program.
2 Preface
2.1 System requirements
TAGCFG has been tested on all typed of AT-compatible MS-DOS systems,
it has also been tested under multi-tasking environments such as Desq-
view v2.42, and Windows v3.1 with no problems.
Almost any version of PC or MS-DOS should work. It has been tested on
DOS versions up to and including 6.00.
| T.A.G. BBS Version 2.7 is required since this program relies heavily
| on the structure of the STATUS.DAT file which can vary from version
| to version of the BBS software!
This program requires about 20-30KB of disk space on your floppy or
hard drive.
2.2 Warranty
This program comes with NO warranty of any kind. Any loss of data,
damage to your system, or unexpected/unexplained results are NOT the
author's fault and are NOT the author's responsibility. This program is
only guaranteed to take up disk space.
However, if you do have a problem, I will be more than willing to help
you figure out what ever your problem might be and offer my services.
2.3 What TAGCFG does
TAGCFG can write your STATUS.DAT (configuration) to an ASCII text file
with descriptive "identifers" for each field and group of fields for
viewing and for editing.
It can also read in the STATUS.TXT text file that it made into your
configuration (to edit it).
See below for installation/first time setup!
3 Installation
3.1 Location of files
You can place the files from the archive in any directory that you
choose, but I found that the Main BBS directory works the best.
3.2 Command line options
When exeucting TAGCFG, you must execute it with one of the following
command lines:
To write your STATUS.DAT file to a "STATUS.TXT" file for viewing or
editing:
| TAGCFG <filename of STATUS.DAT> <filename of text output> <Security>
| "<filename of STATUS.DAT>" is the complete path and filename to the
| STATUS.DAT file that you want written to a text file for viewing or
| editing with at text file editor.
| "<filename of text output>" is the file that TAGCFG will write the
| output to which will contain (almost) all the fields in your
| STATUS.DAT file in readable format, and grouped exactly as seen in
| //SYSTEMCONFIG on the BBS.
"<Security>" is the security level to use. Below is an explanation.
1 = User level; exclude paths, the system passwords, the chat password
and the new user password from the output file.
2 = Co-SysOp level; exclude paths and system password #3 from the out-
put file.
3 = SysOp level; include everything in the output file.
If you want TAGCFG to read in the STATUS.TXT, and re-write it after it
has read it in and save it to the STATUS.DAT, then simply use the
above command line but add another parameter -- "/R" (omit quotes).
3.3 Editing the STATUS.TXT
To edit the output file of TAGCFG, enter your favorite text editor (I
use QEdit, personally) and edit any options on the right side of the
equals sign ("=").
Do not attempt to enter any invalid data, such as a non TRUE/FALSE
value for the flagged options. This could possibly corrupt your
STATUS.DAT file!
If you enter an out-of-range number for the security levels, they may
loop around (for instance, 256 = 1) so try to avoid that, too.
4 Uses of TAGCFG
If you are sharing your configuration with a fellow SysOp, or helping
another SysOp that is just starting out, this can be a way of doing it.
You may wish to use TAGCFG in "User level" (1), for an additional
informative text file for your users to view while on-line just to see
how you have your system set up.
Another use may be for any SysOps that run their board remotely (at
1200 or 2400 baud) and don't like to crawl through TAG's system config;
you can re-configure your entire system from a single text file and
simply upload it to your BBS!
5 Technical information
TAGCFG was written in about two weeks starting on February 24th, 1993.
TAGCFG is written in Pascal, compiled with Turbo Pascal v7.0 by Borland
International.
The T.A.G. BBS data structures have been provided by Paul Williams and
Victor Capton of The T.A.G. Team. Without them, TAGCFG would be use-
less!
All TNT Software-compressed archives have a valid PKZIP v2.04g -AV
verification code made with a registered version of PKZIP v2.04g and
have been PKZIPped with Maximum Compression enabled.
All executable files from TNT Software have been compressed with
PKLITE v1.20 with the extended compression enabled for code size
decrease and hack/virus prevention.
6 Support information
Any problems, questions, suggestions, comments, queries, complaints,
gripes, or anything else TAGCFG-related can be reported to me in any or
all of the following ways:
US Mail:
~~~~~~~
| TNT Software
| c/o Joe McElmeel
18081 Koester
Riverview, MI 48192-7413
InterNet:
~~~~~~~~
| inferno@gatecom.com
BBS:
~~~
| The Galaxy BBS, (313)284-5455, Riverview, MI.
| Supporting V.34/V.FC/V.32terbo/V.32bis/HST with a USR Dual Standard.
| New users have access to all TNT Software products on their first call
| at no charge.
Networks:
~~~~~~~~
FidoNet: 1:2410/480.
FidoNet conferences:
~~~~~~~~~~~~~~~~~~~
| FE_HELP, FE_BETA, TAG, TAGMULTI, TAG_DOORS, and TAGBETA.
7 Acknowledgements
I would like to thank the following people for their contributions to
the TAGCFG program:
Elbert Johnson for thinking of the idea of the program.
Paul Williams and Victor Capton for working their butts off on T.A.G.
BBS and for the support they've given in the TAG echo (and NetMail).
-End of File-