  This file contains additional information on the NEW ROUTING file,
"NODELIST.SYS"

   Immediately upon installation of this new version, RUN UPGRADE.EXE!!
Otherwise POPULOUS will simply _NOT_ run until you Do!!

   Starting in version 1.04, a complete list of ALL nodes in ALL leagues
is now maintained in the file called "NODELIST.SYS", this file contains
the actual ROUTING INFORMATION for Each node found there-in, previously
this information had been contained in the seperate EMP*.DAT files.  Running
the UPGRADE program will initially modify your CONFIG.DAT file as necessary
(IE: It now keeps a seperate version number for the last version run) then
it will CREATE the Nodelist file and apply your DEFAULT Routing commands to
all the nodes found in the file (You DO have a DEFAULTS.SYS don't you??)
Finally, the Old routing information will be REMOVED from your EMP*.DAT
files. If you DO NOT Have a DEFAULTS.SYS file (Created in EMPIRE Mode), all
nodes in the nodelist will simply have defaulted to routing via the LEAGUE
LEADER for that league, you may create the necessary default routing file
after running The Upgrade program via the "DEFAULT ROUTING" command found
on the EMPIRE mode MANAGER menu.

   This new design has been implemented to allow the useage of a single
outbound file for each DESTINATION site and to add flexibility to the
Routing.  Instead of maintaining seperate routing files for each league,
Only one "Master" is required which affects ALL nodes in ALL leagues.

PROCESSING NEW EMP*.DAT or EMP*.DIF Files:
   If you receive a NEW EMP*.DAT file or an EMP*.DIF file, NEW Nodes will
automatically be added to the Nodelist, Note however that It MAY NOT be
save to REMOVE a node from the nodelist (since that node may be in many
different leagues) so any DELETED nodes will be left in the nodelist
until it is rebuilt.

REBUILDING THE NODELIST FILE:
   You may MANUALLY rebuild the nodelist via the NEW menu function under
the manager menu "REBUILD Nodelist".  The Nodelist ALSO automatically tracks
CHANGED installed EMP*.DAT files and will AUTOMATICALLY rebuild itself
during either the NET process mode or during Nightly MAINT mode, including
application of DEFAULT Routing.  Any time the Nodelist is rebuilt, the
DEFAULT routing will automatically be reapplied.

NODELIST Information.
   each site in the Nodelist is identified by a combination of "unique" ID's
as defined in the seperate EMP*.DAT files as well as their address' also as
found in the EMP*.DAT files.  The ID of each site is a simple CRC calculation
based on Board name+Sysop Name,  Since the board name or Sysop name MAY be
spelled differently in alternate leagues, and therefore results in a different
ID for the same board, NEW sites are determined to exist in the Nodelist or
not by first comparing the ID, if this differs the SYSOP name or ADDRESS
is compared for a match. Since nodes MAY be identical but have different ID's
or address' the Nodelist also maintains an unlimited list of ALTERNATE ID's
and ADDRESS' for each Newly added site determined to exist previously in
the nodelist.

EMPIRE MODE:
   This change in routing had MAJOR effects on this portion of the program!
the Individual Node Routing function now changes the information contained
in the NODELIST to allow nodes to be routed individually without need to
enter that specific node in the DEFAULT routing statements (although that is
the PREFERRED METHOD!!).  Additionally there are a number of new menu
selections under the DataBase Menu, including  VIEW NODELIST which will
report on all the sites in the nodelist, including any/all alternate
address'/ID's for each site, the ID of the Node this site is VIA'd by as
well as the MAIN Address/ID for each node.  the MANAGER menu also contains
an option to MANUALLY rebuild the nodelist.

FILE ATTACHES.
   Since each site in the Nodelist may have more then ONE ID or ADDRESS,
there is a slight problem with determing WHAT ID or ADDRESS to use.  Currently
the ID and or ADDRESS defaults to the FIRST one found in the list, therefore
the fileattach message or File generated may have a different ID or ADDRESS
then that found in the current league.  PLEASE LET ME KNOW IF THIS CAUSES
ANY PROBLEMS, I DON'T SEE WHERE IT SHOULD, BUT THEN AGAIN I DON'T RUN
MULTIPLE NETWORKS LIKE EVERYONE ELSE (grin).


