Process for Building the DSP Code for Local and Global
   --------------------------------------------------------

                                                       Rev. 24-OCT-1994 

This is a first draft initial sketch of what goes on to build the DSP code.
          -------------------------


1. Get an OS/2 window on the PC pointed to   C:\DSPCode\Work

2. Execute the  GetFiles  command file.
   This will prompt for the Trigger account password.
   Wait for this command file to complete.  This command file:

    - copies the DSP source files (and associated command files) from
      the PC back to the VAX, in a "Last_Good_Version" directory.

    - deletes the contents of the working directories on the PC to
      guarantee that nothing is "left over"

    - copies the DSP source files (and associted command files) from
      the VAX to the PC.  The DSP source files must be in the directory

        MSUTRGROOT:[TRG_C40.FIRST_RELEASE...]


3. Go to the  Local  subdirectory and execute the following command files:
     LocalAsm all
     LocalLnk all
     LocalBld all     this makes the 11 local  .blx  files

4. Go to the Global subdirectory and execute the following command files:
     GlobalAsm 
     GlobalLnk 
     GlobalBld         this makes the 1 global  .blx  files

5. Hand copy the 12  .blx  files to the appropriate machine and directory.
   In the TRIGGER account, they are stored in

        MSUTRGROOT:[TRG_C40.FIRST_RELEASE.EXECUTABLES]

   but this is NOT where they are read from by TCC.  By default, the TCC
   extracts them from its local disk directory

        DUA0:[L15CT$EXEC] 

   thus the 12  .blx  files must be placed in this directory for TCC to 
   "automatically" use them.