#****************************************************************************
#
#       Project         : Server/Loader V3.1
#       Component       : Server example.
#       File            : README
#       Author          : 
#       Description     : 
#       History         : 
#
#****************************************************************************

This example program as-is works with a HEPC3 with one processor TIM-40
module inserted. The processor module must be a C40 type processor. If
your configuration is different, please edit the "network" file: 
1. If you have a C44 processor, change "HOSTLINK 3" to "HOSTLINK 4".
2. If you use a HEPC2E board, replace "BD API hep3b 0 0" by "BD API
   hep2e 0 0".
3. If you use a HEQUAD, change "idrom.out" in the "ND" lines by one of
   the "hequadxx.out" files (xx being 40, 50 or 60, the number indica-
   ting the processors clock frequency). You must also change "HOSTLINK
   3" to "HOSTLINK 4".

To run the example, simply type

	my32

To compile the C4x example, simply type

	make

This example is to show you how you can use the Server/Loader to boot
and run the DSP system, while a second program (written by you) can
then take over and communicate with the root processor. Essentially,
the second program acts as the Server.

The my32 batch file first boots the DSP network using the standard
Server/Loader using the -r (reset), and -l (load network) options.
The -s (serve) switch is not specified, which means that the Server/
Loader quits after having booted the DSP system. Then the my32 batch
file starts up the "mysl" program. This communicates with the DSP
system using Hunt Engineering API. To compile & link this program,
create a new console project with Microsoft C/C++ or Borland C/C++,
add mysl.cpp, and link with 'hendrv.lib' (Microsoft) or 'hebdrv.lib'
(Borland). For Borland, also define a compiler variable 'BL=1'.


If you intend to write one program that both boots the DSP network
and serves it, please have a look in the ..\exe directory.

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" in the manuals directory on
the Hunt Engineering CD).

26/01/2000

