                      THE SUBS COORDINATOR v3.03+ (C) 1993
                          Kodiak Solutions Unlimited.
                              12-15 Vermeer Drive
                              S. Amboy, NJ 08879
                          Tech Supp BBS (908)525-8295


The following types of updates are allowed.

1.  SUBS Files     - List of Subs in the net (ie SUBS.LST, SUBS.1, etc.)
2.  Sub Info Req   - Type 20 messages for building SUBS.INF/SUBS.LST
3.  CATEG.NET      - Subs Categories (supported by NET33+)


The following options are also available:

1.  Edit a file (Using The TNC Editor).
2.  Convert SUBS.INF (from SUB Info Request Ping) into SUBS.LST





                                 INSTALLATION
                                 ------------


TSC303.EXE should be placed in your main BBS directory (or network data
directory).  It can be run as a standalone program, or as a door of WWIV
(LOCAL ONLY)  It now calls several other programs (such as TNCEDIT/EN3.EXE
/SUBINF.EXE), so it needs as much memory as possible.  

All the files needed by TSC should be placed in your networks data directory.
This includes TNCEDIT.EXE, SUBINF.EXE etc....

The Subs Coordinator CAN BE installed as a chain like this:

A. Description  : The Subs Coordinator v3.03+
B. Filename     : directory\TSC303  
 
                                  (Where directory (above) refers to where
                                   TSC303.EXE can be found, it's best if it's
                                   in your net's data directory).
C. SL           : 255
D. AR           : None.
E. ANSI         : Optional
F. DOS Interrupt: NO         <--- This is critical
G. 300 Baud     : Allowed
H. Shrink       : Yes        <--- This is necessary
I. Disable Pause: Yes
J. Local only   : Yes        <--- This is necessary


In your CONFIG.SYS file, you should have a statement saying (something like
this):

FILES=30

The "FILES=" statement is a suggested number (If the number is higher, that is
alright).  The Network Coordinator program doesn't open anywhere near that
amount of files at one time, but if you are running this as a chain, the BBS
may leave some files open before you run the program.





When you run the program, it will first attempt to figure out which directory
your network files are kept in.  Once it has figured that out, it will ask you
to choose which type of update to send.  If you select an option that allows
more than one file to be sent (such as SUBS.LST, SUBS.1, etc...), a list
of available files will be shown to you.  Use the cursor (OR MOUSE) to
highlight the selection then press space (or push mouse button) to select the
file (a check mark will appear next to each file selected).  When you have 
tagged all the files you want to send press ENTER. (or ESC to ABORT).  

Note: There are times when files will be shown to you
that should not be sent.  It is assumed that as the SC, you know which files
should/shouldn't be sent via the network.  If in doubt, consult the network
docs.

The program will then ask you to select which nodes to send the files to.
Highlight the selection (using mouse or cursor keys), then press return.
Depending on what selection you made, a prompt MAY come up asking for an AREA
CODE, GROUP NUMBER, or NODE NUMBER.  The program will then select the desired
nodes and begin sending the files.

Once the update has been sent, you will be brought back to the main menu
again.




			      THE CATEG.NET FILE
                              ------------------


This is a new file that WWIV and TSC are now supporting.  Basically, it 
carries a list of all the different SUBS categories.  The format is a 
category number, followed by a period, some spaces, and then the category
name.  There should only be one category on a line, and a category 0 should 
always be defined.  WWIV doesn't require a category 0, but the SUB.INF file
converter will only places subs whose categories are in categ.net into the
SUBS.LST file.  Try not to have more than a screen full of categories.
TNC will support as many as you need, but it becomes very difficult for the
members of your network to categorize their subs.  A sample CATEG.NET file is
included and recommended.   


Example CATEG.NET file:


0.  Subs With No Category Selected
1.  Sysop/CoSysop Subs
2.  Science Fiction Subs
99. Miscellaneous Subs




When you change/add a new sub, and this file is in your network data
directory, WWIV will ask you what category to place the sub in.  This info
is sent along with the SUBS.INF (ping) to the NC when he/she requests it, 
which allows TNC to automate the sorting/categorizing of SUBS.LST.  
 



		         THE SUB INFO REQUEST OPTION
                         ---------------------------


This option allows the subs coordinator (SC) to request a list of SUBS 
Hosted on each node of his network (these are also know as SUB PINGS).  This
information, is placed in a file called SUBS.INF in the NC's network data
directory.  The SC can then manually sort/edit this file and create a
SUBS.LST file or, use the CONVERT SUBS.INF Option below to automate the
process.  These PINGS should be sent about once a month (to allow plenty of
time for a response).
  

			
                         THE CONVERT SUBS.INF Option
                         ---------------------------


This option on the TSC main menu, will take the current SUBS.INF file,
sort it, remove records that are EXACT DUPLICATES, place them in the
proper categories (when CATEG.NET is used), and create a NEW SUBS.LST file
(The old one will be deleted).  SUBS.INF is then deleted.  Note, that this
option does NOT add onto an existing SUBS.LST file.  For this reason, you
should allow at least a week between sending the SUB INFO Request (Ping),
and converting the SUBS.INF file.
 

The following procedure should be followed for best results.

1.  Send out CATEG.NET, and urge users to update their subs in \\BOARDEDIT
    using the 'J' option.  Tell them that their subs will not be placed in
    the proper category until they update it.  Allow several weeks for this
    to occur.
2.  Send out a SUBS Info Request (Ping).  Wait a few weeks for the responses.
    (Do not send out another SUBS Info Request until you've finished
    the whole process)
3.  Use the CONVERT SUBS.INF option to create your SUBS.LST file.
4.  Use The TSC Editor to make any minor changes to SUBS.LST (optional).
5.  Send the new SUBS.LST to your network.
6.  Go Back to Step 2 or 3 for the next SUBS.LST update.





                              THE DE3.EXE FILE
                             ------------------

This file is NOT included in the DEMO version, but left it in the docs.
The DE3.EXE file is the program that is used to decode the sub updates.
It should be placed in the network's data directory, if using an earlier 
version of the network software (like NET30.ZIP), you may have to put it in
the main BBS directory.  If installed with WWIV 4.21a or higher, your NETWORK
name (ie FREDnet, WWIVnet, OTHERnet, etc...) must be entered exactly the same
(upper/lower case doesn't matter though) as the network name you requested.
If not, the network will not know where to place the files.  TSC updates are
more strict regarding this (for your own good), than NETUP, but the fact of
the matter remains, that the REAL net name should be there (note that network
gating mail will not work properly, if this isn't set properly - regardless of
whether you are running a NETUP network, or a TNC network), so no matter what
network you run, that name should be accurate.




                                     OTHER
                                     -----


Revision Log.


v3.03 - Initial Public Release.

  Your suggestions for new features are welcome, not all may be implemented,
  but it sure doesn't hurt to ask.




                         THE MAIN FILES INCLUDED W/TSC
                         -----------------------------


TSC303.EXE   - Main TSC program - sends updates via network.
               Place this file in main BBS directory, or network data
               directory.

SUBVAL.303   - This is the validation code for your version of TSC
               Do not give this out to anyone (except SUBS Coordinator).
               This file should be placed in your network data directory.
               (NOT INCLUDED IN DEMO)

EN3.EXE      - This performs all of the encryption.  It is called by
               TSC303 whenever encryption is necessary.  It should be
               placed in the same directory as your NETWORK data files
               (like BBSLIST.NET etc...)  Do not give this out to
               anyone (except SUBS COORDINATOR)  
               (NOT INCLUDED IN DEMO)

DE3.EXE      - This program performs the network decryption.  Each
               node in the network MUST have this file in the directory
               containing your network's data files (same as above).
               (NOT INCLUDED IN DEMO)  

TNCEDIT.EXE  - This is the text editor I wrote for TNC/TSC.  It supports 
               Wordstar format block commands (like Ctrl-K B, Ctrl-K K, etc.),
               as well as the standard Cut & Paste editing.

SUBINF.EXE   - This program is called by TSC to create a new SUBS.LST file
               by sorting/categorizing the SUBS.INF file

CATEG.NET    - Sample CATEG.NET file.



                              POOR DOCUMENTATION
                              ------------------


I apologize for the poor documentation, I just haven't had sufficient time to
really organize it.  If anyone is interested in writing the documentation for
this software, go right ahead and send me a copy.  If it's better than what
I'm using at that time, I'll include it with future versions of TNC (with
proper credit to the author of course).    



