#****************************************************************************
#
#       Project         : Server/Loader V4.07
#       Component       : Server example.
#       File            : README
#       Author          : 
#       Description     : 
#       History         : 
#
#****************************************************************************

This example program as-is works with a HEPC9 with 3 HERON4 modules
in slot 1,2,3. The board ID must be 0 (board ID is the red switch
in the upper left corner of the HEPC9).
If your configuration is different, please edit the "network" file.

To run the example, first compile/link the 3 example files. Each is
a represents a separate project. One you created the three out files
named 'module1_heron4.out', 'module2_heron4.out', 'module3_heron4.out',
to run it type

	w32 v

There is also a script for use with HEPC8, called w32_pc8. This uses a
network file network.pc8, and this network file assumes an HEPC8 with
board switch 0, and 3 HERON4's in slot 1, 2 and 3. To run:

	w32_pc8 v

The 'v' selects verbose option and is optional.

To compile the C6x examples, you need access to Code Composer Studio.
At the time of writing this, Code Composer Studio is only available
for Windows. Using Code Composer Studio, create new projects with
the Create New HERON-API Project plug-in. If you name a project
after a C file, that C file is automatically included in the project.
For example, if you create a project 'module1.pjt', then 'module1.c'
is automatically included. Similarly, 'module2.pjt' or 'module3.pjt'
naming will make the plugin include 'module2.c' or 'module3.c' into
the respective project.

The Server/Loader uses a network description file (called "network")
to decide what nodes need to be loaded via what links. This is further
described in the manual ("svloader.pdf" and "networkspec.pdf" in the
/web/pdfs/manuals directory on the Hunt Engineering CD).

13/05/2003

