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


This program allows you to run your very own WWIV compatible network.  It is
significantly different than Wayne Bells NETUP program.  In general, it
accomplishes the same thing (and more), but does it in a radically different
way.  The program is REGISTERED to YOU, and is NOT transferable.  Do not give
a copy to anyone else, as they would be able to send updates through your
network (and as such could do GREAT damage).


The Network Coordinator now includes separate programs for:

1.  The Network Coordinator. 
2.  The Group Coordinators (or Zone Coordinators).
3.  The Subs Coordinator.
4.  The News Coordinator.    
5.  Turbo/Borland C Source Code to make your own DE257.EXE/DE258.EXE/etc... 
    files for your groups.


The Network Coordinator (NC module) will allow you to send net updates to:

1.  All Nodes in the Network
2.  All Nodes in a Group
3.  All Nodes in an Area Code
4.  All Area Coordinators
5.  All Area Coordinators in a Group
6.  All Group Coordinators
7.  A Single Node


The following types of updates are allowed.

1.  BBSLIST        - List of BBSes in the NET (BBSLIST.NET, BBSLIST.1, etc.)
2.  CONNECT        - List of Connections in the NET (CONNECT.*)
3.  FBACKHDR.NET   - See Below
4.  SUBS Files     - List of Subs in the net (ie SUBS.LST, SUBS.1, etc.)
5.  WWIVNEWS.*     - WWIVnews Files (ie WWIVNEWS.NET, WWIVNEWS.1, FREDNET.NWS,
    and/or *.NWS     etc...) 
6.  ZIP Files      - Any Sized Zip File
7.  FEEDBACK       - Source Verified E-mail from 1@1 (*.TXT)
8.  DECODE Updates - DE*.EXE files (they must already have DE511.EXE though)
9.  Sub Info Req   - Type 20 messages for building SUBS.INF/SUBS.LST
10. CATEG.NET      - Subs Categories (supported by NET33+)
11. NETWORKS.LST   - List of know networks


* FBACKHDR.NET - This file is inserted at the beginning of the NET analysis
                 mail the BBS sends you after receiving a net update.
                 Caution should be used with this file.  Many word processors
                 add an end-of-file marker to this file, which will cause the
                 NET ANALYSIS mail to end BEFORE displaying the whole message.
                 I suggest you create/edit this file using the built-in TNC
                 File Editor,  if you see a left-arrow at the end of the file
                 delete it.



The following options are also included/available:

1.  Edit a file (Using The TNC Editor).
2.  Run Black Dragon's NETEDIT (version 1.41 or higher)
3.  Convert SUBS.INF (from SUB Info Request Ping) into SUBS.LST




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


TNC303.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/NETEDIT/
EN511/SUBINF), so it needs as much memory as possible.  

All the files needed by TNC should be placed in your networks data directory.
This includes TNCEDIT.EXE, EN511.EXE, DE511.EXE, NETEDIT.EXE (optional),
SUBINF.EXE, TNCVAL.303, BBBSLIST.*, CONNECT.*, etc....

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

A. Description  : The Network Coordinator v3.03
B. Filename     : directory\TNC303 directory\TNCVAL.303 
 
                                  (Where directory (above) refers to where
                                   TNCVAL.303/TNC303.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.





                                HOW TO USE TNC
                                --------------


First, it is assumed, that if you wish to run your own network, that you
have sufficient knowledge of how a network works, and how to setup
all of the network files.  The docs with Wayne Bell's NET33 show the
format of most of the network files, and as such I won't get into detail
about them here.

You should setup all of your network files BEFORE running The Network
Coordinator.  It can't send a file that doesn't exist, and it can't send a
file out to a node on the network that doesn't exist yet (technically).
I've included samples of most of the files, so it shouldn't be too hard
to get started.


If when running your BBS, NETWORK3 displays some sort of divide by zero error,
this means either your BBSLIST, CONNECT, or CALLOUT.NET files are not setup 
properly, and you are not connected to the rest of the network.

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 BBSLIST - ie BBSLIST.1, BBSLIST.2,
BBSLIST.3......), 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 NC, 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.

Note that there is a limitation to the size of the Source Verified Feedback
sent through the network.  This file must be smaller than 31700 bytes before
it can be sent.  If the file is larger than that, The Network Coordinator
program will display an error message indicating the problem.

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

Note:  You must always send a BBSLIST.NET or CONNECT.NET if you want the
       BBS to Re-Analyze the network.  If you just send BBSLIST.1 for example,
       the file will be received and decoded, but it will not force the
       network to analyze it.  If you are just sending a NETWORKS.LST,
       CATEG.NET or SUBS.* update, you do not need to send the BBSLIST/CONNECT
       files.




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


This is a new file that WWIV and TNC 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 network coordinator (NC) 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 NC 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 TNC 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 TNC 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 DE511.EXE FILE
                              ------------------


The DE511.EXE file is the program that is used to decode the network 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.  TNC 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.




                     ERROR MESSAGES YOUR NODES MAY RECEIVE
                     -------------------------------------


1.  >WARNING<  File 'DE2xx.EXE' not found. Get a copy from......:
    This message is normal, if you are using the GROUP structure
    for net files.  Quite simply, it's looking for a file that the GC
    would use to send messages to their group.  You need to make these
    yourself.  An example Turbo/Borland C program (with source code)
    is included to show you how to make these files.  This is NOT
    critical, they can still receive net updates without this file.  

2.  ERR 05: DE511  could not find CONFIG.DAT:
    DE511.EXE can't find CONFIG.DAT.  This error message shouldn't occur
    with WWIV, but might occur if used on another BBS (VBBS?).  If it occurs,
    the update will NOT be performed.

3.  ERR 06: Invalid Decryption:
    The update didn't decode properly.  Either someone was trying to send
    an update with the same encryption method (possible hack attempt), or the
    update got corrupted somehow.  The update will not be performed.

4.  ERR 07: xxxxNET Not Setup in INIT:
    This message will occur if the user is using WWIV 4.21a or higher, but
    doesn't have your net name typed in properly in the INIT program.  The
    network will not know where to place the updates, so they will be lost.

5.  ERR 08: xxxxNET Update - Non Readable:
    You are attempting to decode the file from outside the network software,
    or you are running an incompatible network.  This is also a safeguard
    from LNET/NETPURGE attempting to decode the update (which would actually
    overwrite your files if it was successful).

6.  ERR 09: Invalid Decryption:
    The update was incomplete/or corrupt (ie it got cutoff somehow).



                                VBBS Support
                                ------------

I have tried to improve the way updates are sent under TNC to support
VBBS systems.  Through some investigation, I have discovered that VBBS uses
Wayne Bell's network software to some degree to support WWIV compatible
networks.  Unfortunately, I don't have a VBBS system to test this on, so I'm 
really not sure, and I won't make any guarantees.

If the VBBS system is using NET31 or higher, and has used WWIV's INIT program
(preferrably 4.22) to create the proper files & directories, I don't see why
it shouldn't work, but you never know.

If you have VBBS systems in your network, please let me know if this works for
them, and if not, report to me the error number/message that DE511 shows them
when they receive the update, and any additional info if possible (copies of 
their NETWORKS.DAT/CONFIG.DAT/NET version/Etc... would be extremely helpful).

If there is a VBBS sysop out there who can loan/supply me with the necessary
VBBS executable files to test WWIV compatibility, I would be forever greatful.



                                     OTHER
                                     -----


Revision Log.


v1.20 - Initial Public Release.

v2.00 - Complete rewrite.  Added professional menus, mouse support, file
        tagging, removed 20 group limit - can now have as many as 255 groups,
        removed "SEND TO NODES in a FILE" option, added more support for
        sending ZIP files - prior version would only send FILE.ZIP - new
        version will send any ZIP file (smaller than 31700 bytes),  Removed
        ANSI.SYS requirement.

v2.01 - Refined the input prompts.  Created a demo version.  Made the code
        a bit more efficient.  Now shows how many nodes were selected.

v3.01 - Major update.  Now includes a text file editor, support for NETEDIT
        (a Black Dragon utility).  Supports files > 32k, Sends Sub Info
        Requests.  Source Verified Feedback, etc...  DE100.EXE was
        de-implemented, and will not be supported further.  Fixed a bug that
        would not allow you to run your network from a different drive than
        your BBS is on.  No longer get one of those short messages (saying
        "Received xxxxxxx.xxx ....") when you log on, but still appears in
        the NETDAT0.LOG file.

v3.02 - Support for CATEG.NET updates.  Source Verified E-Mail From NC now
        shows up as Type 1 - NC (instead of GC-255).  


v3.03 - Support for NETWORKS.LST updates.  Will convert SUBS.INF (ping file)
        into a sorted SUBS.LST file, and sort into categories if CATEG.NET
        is used.  The TNC Editor has been vastly improved, including support
        for 43/50 line screen mode (EGA/VGA only), Search & Replace, Multiple
        file windows, DOS Shell, Cut & Paste (clipboard style), window tiling
        or cascading.  Update types have been changed from Type 15/0's to
        Type 1/0's (for the most part).  Hopefully, this will allow VBBS
        systems to work with TNC.  All executable programs called by TNC
        (ie TNCEDIT.EXE, NETEDIT.EXE, EN511.EXE, DE511.EXE, SUBINF.EXE, etc)
        can now be placed in the networks data directory.  TNC will search
        for files in the following order:  
           1.  Current directory
           2.  Network Data Directory
           3.  Directories in your Path Statement
        New DE511.EXE/EN511.EXE files are supplied.  They are downwardly
        compatible with the prior version, so you can use the SEND DExxx
        Update option to send the new version to nodes that have the old
        version.  The new DE511.EXE files should be sent out to your
        network BEFORE sending any other updates.  Hopefully, this is the
        last revision of the EN511/DE511 files for awhile.   Also added,
        is support for sending *.NWS files (some people didn't want to send
        out WWIVNEWS.NET, but wanted something like FREDNET.NWS instead).

v3.03+  Added Group Coordinator module, Subs Coordinator module, WWIVnews
        module (note these modules are not as powerful as the same options
        in The Network Coordinator).  Ie TNC allows files > 31500 bytes
        these modules don't.  They are also more restricted to the PROPER
        filenames than TNC.  TNC303 really didn't change in this version
        (except for some cosmetic changes), so I didn't upgrade the version
        number.  Also TNCEDIT has been improved slightly, if you specify
        to tile the files, they stay tiled (even when loading another file)
        until either you exit TNCEDIT or change it back to cascading.


Possible Future Additions:

  1.  Add an update log.
  2.  Separate command-line programs for sending files via batch mode. 
  3.  Send SSMs to the network.
  4.  Improved Documentation.
  5.  Ability to change the network name yourself.



  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/TNC
                         -----------------------------


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

TNCVAL.303   - This is the validation code for your version of TNC
               Do not give this out to anyone (not included in DEMO).
               This file should be placed in your network data directory.

EN511.EXE    - This performs all of the encryption.  It is called by
               TNC303 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 (not included in DEMO).  


DE511.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.  It supports Wordstar
               format block commands (like Ctrl-K B, Ctrl-K K, etc..), as
               well as the standard Cut & Paste editing.  It is MOUSE aware.

SUBINF.EXE   - This program is called by TNC to create a new SUBS.LST file
               by sorting/categorizing the SUBS.INF file
               Should only be given out to SUBS Coordinator.

CATEG.NET    - Sample CATEG.NET file.

BBSLIST.*    - Sample BBSLIST files.

CONNECT.*    - Sample CONNECT files.

DE257.C      - Source Code to DE257.EXE - use this as a guide to make
               your own DE257 - DE510.EXE files.  Don't give this out,
               to anyone.

EN257.C      - Source Code to EN257.EXE - use this as a guide to make
               your own EN257 - EN510.EXE files.  Don't give this out
               to anyone.

TGC303.ZIP   - The GROUP Coordinator Module.  A copy of this zip
               should be given to each GC.  Make sure to give them the
               proper EN256+group.EXE (ie group 2 - EN258.EXE) and
               DE256+group.EXE file instead of the EN/DE257 file
               included.  They only need the EN/DE file for their
               group.

TSC303.ZIP   - The Subs Coordinator Module.  A copy of this ZIP should
               be given to the SUBS COORDINATOR.

TWC303.ZIP   - The WWIVnews Coordinator.  A copy of this ZIP should only
               be given to the NEWS COORDINATOR.




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

I am currently undertaking the task of completely rewriting the docs.  At this
point it is about 1/3 finished.  The new docs are 100% better than these, and
go into more details regarding The Group Coordinater/The Subs Coordinator/The
WWIVnews Coordinator, etc....  Needless to say, I don't want to hold back this
release for those docs.  





                            CHANGING NETWORK NAMES
                            ----------------------


There may come a time when you would like to change the name of your network.
As you may know, your network name was built-into the software, and as such
was not easily changed.  Through some programming changes, I am now better
able to handle such requests.  To discourage possibilities of piracy, there
will be a substantial fee charged to change the name, and once changed, you
are not entitled to upgrades for PRIOR network names.  The fee for changing
the network name will be $25.  See NETNAME.TXT for more details.




                     UPGRADING FROM A PRIOR VERSION OF TNC
                     -------------------------------------


If you are running a prior version of TNC, and would like to upgrade, please
fill out the form UPGRADE.TXT, and mail it along with a diskette and the 
proper processing fee (if any).  It is very important that you fill out
EVERYTHING, so that I can verify your registration.  


Users upgrading from v3.0x to 3.03 should send out the NEW DE511.EXE to their
network (via Send DExxx Update Option), or strange results may be encountered.  

Users upgrading from v2.0x to 3.03 will need to get a copy of DE511.EXE to
all of your nodes.  Those nodes that do not get the DE511.EXE will no longer
receive updates.  


                        UPGRADING FROM TNC303 BETA
                        --------------------------

The DE3.EXE file has changed slightly from the beta.  It's a good idea to
send out a new copy of all the DE files (just to make sure everyone is 
current).  Also, I'd suggest sending new copies of TGC303.ZIP, TSC303.ZIP
and TWC303.ZIP to your coordinators.