
A.3  VSPS Installation On MSDOS


CONTENTS

1  TERMS ...........................................

2  REQUIREMENTS
   2.1  Required hardware...........................
   2.2  Recommended hardware........................
   2.3  Optional hardware...........................
   2.4  The VSP Evaluation Board (VSPE).............
   2.5  Software needed to operate the Simulator....
   2.6  Software required to create user simulators.
   2.7  Software for user simulators using FORTRAN..

3  INSTALLATION
   3.1  Getting started quickly.....................
   3.2  VSPS automatic installation requirements....
   3.3  VSPS automatic installation procedure.......
   3.4  VSPE automatic installation procedure.......

4  CONFIGURATION
   4.1  CONFIG.SYS and ANSI.SYS.....................
   4.2  TERMINAL.ID, Simulator display configuration
   4.3  Microsoft `C' Compiler......................
   4.4  Microsoft FORTRAN Compiler..................
   4.5  PLink86 Linker..............................
   4.6  Printing graphic screens....................
   4.7  AUTOEXEC.BAT and AUTOEXEC.TXT...............

5  DIRECTORIES AND FILES
   5.1  ...for the Simulator........................
   5.2  ...for creating user simulators.............
   5.3  ...for the VSP Evaluation Board (VSPE)......
   5.4  Filename extensions.........................

6  TESTS
   6.1  VSPS Installation test......................
   6.2  User simulator creation test................
   6.3  VSPE Installation test......................
   6.4  User simulator test with VSPE support.......

7  RUNNING THE SIMULATOR ...........................

8  DEVELOPING USER SIMULATORS
   8.1  Single user module..........................
   8.2  Single user module with VSPE support........
   8.3  Multiple user modules.......................
   8.4  Multiple user modules with VSPE support.....

9  CHECKLIST .......................................
1  TERMS

a) In this section 'DOS' refers to the Microsoft MSDOS operating system, not the IBM
   mainframe operating system called DOS.  MSDOS is called PCDOS when running on the
   IBM personal computer family.

b) `Computer' means an IBM PC/AT or compatible (see Required Hardware).

c) `Simulator' and `VSPS' refer to the VSP Simulator program provided by Zoran.

d) `User simulator' refers to a simulator created by linking user VSP code.

e) `simulator' (lower case) usually applies to both the VSPS and user simulators.

f) `VSPE' refers to Zoran's Vector Signal Processor Evaluation board for the IBM
   PC/AT and compatibles.

g) Directories are `siblings' if they share a common parent.  Thus the directories
   \ZORAN\VM and \ZORAN\VEXAMPLE are siblings because their parent is \ZORAN.

h) DOS commands and filenames are CAPITALIZED for emphasis although DOS actually
   ignores case.

i) When referring to a product, the word `version' may be abbreviated `v', or
   omitted.  Examples: `VSPS v2.35', `DOS 3.1'.
2  REQUIREMENTS

To install and run the Simulator you need the following:

2.1  Required Hardware

a) An IBM PC/AT computer or close compatible (example: Compaq Deskpro 286).  Older
   PCs such as the PC/XT have an 8-bit expansion bus and will not accept future Zoran
   development boards.  Also, the speed of an AT-class machine is needed for linking
   user simulators in a reasonable time.
b) A hard disk with at least two megabytes space available
c) 640K of RAM.

     NOTE: the Simulator requires 640K of RAM, less the amount for DOS.
     `Resident' software loaded after DOS must not occupy more than about five
     Kbytes.  The DOS command `CHKDSK' will tell you how much disk and RAM space
     is available.  CHKDSK displays a summary which includes the following
     lines:
     
          xxxxxxx bytes available on disk -- item `b' above
           xxxxxx bytes free -- should be >578000


2.2  Recommended Hardware

For computers other than Compaq:

* Color Graphics Adapter ("CGA") or Enhanced Graphics Adapter ("EGA") (or compatible
  boards) and appropriate monitor, on PCs.

The Simulator can use an IBM monochrome adapter (text-only display), but will display
only `character' plots of signals; a color adapter allows `graphic' plots.

The present Simulator does not use color or the special features of the EGA, so the
least-cost display for graphic plots would be the CGA and a "composite" green or
amber monitor.


2.3  Optional Hardware

* An 80287 math co-processor.

The Simulator automatically uses a math co-processor if one is present.  This
increases the speed of floating-point ("real-number") operations.


2.4  The VSP Evaluation Board (VSPE)

With Zoran's Vector Signal Processor Evaluation (VSPE) board, you can test your VSP
programs on an actual VSP as well as via simulation.  The VSPE package includes all
software for creating user simulators with VSPE support.  This software installs
automatically.


2.5  Software Required to Operate the Simulator

* MS/PCDOS Operating System, version 3.1.  Version 3.2 supports the IBM Convertible
  and is not required.  Version 3.00 should work, but is not tested by Zoran.
   
     NOTE: The DOS `VER' command displays the version number.


2.6  Software Required to Create User Simulators:

* Microsoft's `C' Compiler, version 3.00
* Phoenix Software's Associates `Plink86' Object Linker, version 1.47 or 1.48.

     NOTE: The current Plink86 version is 1.48.  The VSPS link files will work
     for 1.47 and 1.48, but we recommend that users of v1.47 contact Phoenix for
     an upgrade to 1.48 as support for 1.47 may be dropped in the next release
     of the VSPS.
     
     The file OVERLAY.LIB which comes with Plink86 is specific to a given
     Plink86 version; when upgrading be sure to replace this file.


2.7  Software for User Simulators Using FORTRAN:

* Microsoft's FORTRAN compiler, version 3.31 or higher.
3  INSTALLATION

The Simulator software is distributed on a set of diskettes.  An installation
procedure on the first diskette will automatically copy the Simulator files to the
proper directories on the hard disk.

This procedure will:

   * expect to find a hard disk drive named C:
   * use the DOS `RESTORE.COM' program (see section 3.2: VSPS Automatic Installation
     Requirements, below)
   * create a \ZORAN directory on drive C: if no such directory exists
   * create several subdirectories under the \ZORAN directory
   * create a \MSF directory on drive C: if no such directory exists


3.1  Getting Started Quickly

To use the Simulator immediately, just complete the following steps:

     3.2. VSPS automatic installation requirements

     3.3. VSPS automatic installation procedure

     4.1. CONFIGURING THE PC: CONFIG.SYS and ANSI.SYS

     4.2. CONFIGURING THE PC: TERMINAL.ID

...then proceed to section 7, "Running the Simulator".

To completely configure the Simulator, proceed to the section "Configuring the PC".
Refer to the Checklist in section 9.

3.2  VSPS Automatic Installation Requirements

Two conditions must be true for the VSPS automatic installation procedure to work.
(These do not apply to VSPE installation).

Requirements:

1) `RESTORE.COM' must be on the DOS search path

To see if this is true, enter the command `PATH' at the DOS prompt on the hard disk.
PATH will respond with either:

   a) `No path', or
   b) `PATH=', followed by a list of directories (the `path directories')

For RESTORE.COM to be `on the path',

   * a PATH must be in effect (response `b' above), and
   * RESTORE.COM must be on one of the path directories

If both of these are true then RESTORE.COM is `on the path', so proceed to "2) No
resident programs...", below.

Otherwise:

* If no path is set (`a' above), set a temporary path by entering `PATH \'.  Verify
that the path has been set by entering `PATH' again.  This time, PATH should respond

   `PATH=\'

* If RESTORE.COM is not on the hard disk, copy it from the DOS SYSTEM diskette to one
of the path directories.  (If you just entered `PATH \', copy it to `C:\', the root
directory of the hard disk).

* If RESTORE.COM is already on the hard disk, copy it from its present directory to
one of the path directories.  (If you just entered `PATH \', copy it to `C:\', the
root directory of the hard disk).

2) No resident programs should be installed
   (example: Borland's `SideKick')

SideKick is one resident program which interferes with RESTORE.COM.  If your
\AUTOEXEC.BAT file installs any resident programs, you should temporarily change your
\AUTOEXEC.BAT file to disable their installation, reboot the PC, install the VSP
Simulator, then undo the changes to \AUTOEXEC.BAT.


3.3  VSPS Automatic Installation Procedure

To install the Simulator files:

* Place release diskette #1 in drive A:

* Type the following command at the DOS prompt:

     A:INSTALL

* Follow the instructions displayed by the installation program.  Be sure to insert
the diskettes in the proper order.

* When installation is complete, follow any supplemental instructions displayed by
the installation procedure.


3.4  VSPE Automatic Installation Procedure

[Skip this section if you do not have a VSPE board]

To install the VSPE files:

* Place the release diskette in drive A:

* Type the following command at the DOS prompt:

     A:INSTALL

* Follow the instructions displayed by the installation program.

* When installation is complete, follow any supplemental instructions displayed by
the installation procedure.


4  CONFIGURING THE PC

4.1  CONFIG.SYS and ANSI.SYS

The file \CONFIG.SYS (`\' means `on the root directory') should include the following
statement as its first line to ensure correct operation of the Simulator:

     DEVICE=ANSI.SYS
     
For the above statement to work, the file ANSI.SYS must also be on the root directory
of the hard disk.  ANSI.SYS is found on the DOS SYSTEM diskette.

Changes to \CONFIG.SYS do not take effect until you reboot your PC (hold down the
CTRL and ALT keys, then press DEL).


4.2  TERMINAL.ID, Simulator Display Configuration File

If your system does not have a graphics display (e.g. a `Color Graphics' or `Enhanced
Graphics' adapter with appropriate monitor), rename the file TERMINAL.IDX on the
\ZORAN\VM\ directory to TERMINAL.ID.  This disables `graphic' plotting, which is not
possible on a monochrome text adapter; use `character' plotting instead.


4.3  Microsoft `C' Compiler

The Microsoft `C' Compiler should be installed and be accessible via the DOS search
path.  In addition, a `SET  INCLUDE=' command must be issued to tell the compiler
where to find `include' (header) files.  Details of both operations appear in the
section `AUTOEXEC.BAT...' below.


4.4  Microsoft FORTRAN Compiler

The automatic installation procedure copies two Microsoft FORTRAN library files to
the \MSF directory, creating the directory if necessary.  If you do not wish to
create user simulators using FORTRAN source code, the compiler itself is not
required.

If you wish to create user simulators using FORTRAN, the Microsoft FORTRAN compiler
should be installed on the directory listed in the file \ZORAN\VM\E.LNK (which
currently specifies the \MSF directory).


4.5  PLink86 Linker

The PLink86 linker should be installed and be accessible via the DOS search path.  In
addition, a `SET  OBJ=' command must be issued to tell PLINK86 where to find its
overlay library, OVERLAY.LIB.  Details of both operations appear in the section
`AUTOEXEC.BAT...', below.
4.6  Printing Graphic Screens

The contents of the screen of a PC can be copied to the printer by pressing
SHIFT-PrtSc (hold down SHIFT while pressing the */PrtSc key).  This is knows as a
`screen dump'.

However, to obtain screen dumps of graphic screens (rather than text mode) you must:

* have a graphics display (of course);
* have a graphics printer such as an EPSON MX- or FX- series;
* run the MSDOS `resident' command GRAPHICS.COM before running the Simulator.  This
  may be done automatically when your PC is booted via the AUTOEXEC.BAT file (see the
  following section).


4.7  AUTOEXEC.BAT and AUTOEXEC.TXT

For the VSPS and its utilities to run from directories other than \ZORAN\VM, the DOS
search path must be set properly.

Also, for Microsoft `C' and the PLink86 linker to work, the DOS search path must be
set properly and two SET commands must be issued.  The usual place for these things
to be done is in the \AUTOEXEC.BAT file, which is executed when the PC is booted.
     
     NOTE: spaces are significant in the SET command.  There should not be a
     space before the equal sign (`=').

Lastly, a program called GRAPHICS must be run to enable graphic screen dumps (see
previous section).

The following `fragment' of an AUTOEXEC.BAT file, stored as \ZORAN\VM\AUTOEXEC.TXT,
performs all the required operations.  Your hard disk probably has an existing
\AUTOEXEC.BAT file; do not simply replace it with the contents of AUTOEXEC.TXT.
Instead, use AUTOEXEC.TXT as a guide when changing your \AUTOEXEC.BAT, with
appropriate changes if your directory layout differs.  Lines beginning with `:' are
comments.

     : AUTOEXEC.TXT: Fragment of \AUTOEXEC.BAT for VSPS
     : Last edit 8/1/86 JJC
     :
     : Set DOS prompt to show the search path
     PROMPT $p$g $a
     :
     : Set DOS search path so DOS can find `C' compiler
     : and PLink86.  Assumes `C' compiler is on \MSC,
     : FORTRAN compiler (if installed) is on \MSF, and
     : PLINK86.EXE is on \UTILS.
     : Edit this string into PATH command in \AUTOEXEC.BAT
     PATH \UTILS;\ZORAN\VM;\MSC;\MSF;
     :
     : Set `INCLUDE' environment variable so Microsoft `C'
     : can find header files for itself and the VSPS.
     SET INCLUDE=\MSC\INC;\ZORAN\VM
     :
     : Set the `OBJ' environment variable so PLink86
     : can find the file OVERLAY.LIB (assumed here to be
     : on the \UTILS directory).  \ZORAN\VM\E.LNK tells
     : where to find other library and object files.
     : NOTE: NO SPACES BETWEEN `OBJ' and `='.
     SET OBJ=\UTILS
     :
     : Install the DOS graphic print-screen facility.
     : To be done after all PROMPT, PATH and SET commands.
     : (GRAPHICS need not be installed on text-only systems)
     : GRAPHICS.COM must be on the root directory or
     : on the PATH.
     GRAPHICS
5  DIRECTORIES AND FILES

5.1  Simulator Directories and Files

Directory (directory description)
   File           Description                       

\MSF (Microsoft FORTRAN files)
   MATH.LIB       Microsoft FORTRAN libraries;
   FORTRAN.LIB    used to link user simulators

\ZORAN\VEXAMPLE (Examples for creating user simulators)
   EXAMPLE1.FFP   VSP source code example: Load, FFT, Store
   DEFER1.FFP     Load, FFT, Store, with DEFER
   EXAMPLE2.FFP   FFT of cosine, find max freq
   EXAMPLE3.FFP   Overlapped FFTs (separate RAM sections)
   EXAMPLE4.FFP   Use FORTRAN subroutines to create
                  squarewave, print FFT and power spectrum
   FORPACK.FOR    FORTRAN code for subroutines in EXAMPLE4
   EXAMPLE4.LNK   "Link file" to link EXAMPLE4.OBJ and
                  FORPACK.OBJ into a user simulator
   TEST2.*        User simulator creation test
   TESTVSPE.*     User simulator creation test with VSPE
                  board support; installed with VSPE

\ZORAN\VM (`VM' = `VSPS MAIN' directory)
   AUTOEXEC.TXT   Fragment of \AUTOEXEC.BAT
   B.LNK          Beginning of user simulator link
   CREATE.BAT     Parses, compiles, and links VSP source
                  into a user simulator
   CLEANUP.BAT    Deletes parse, compile, link results;
                  leaves .FFP and .EXE
   E.LNK          End of user simulator link
   INSTALL1.BAT   From installation; can be deleted
   PARSER.EXE     ("Parser"); produces `C' code from VSP
                  source (`.FFP').  Driven by VP.BAT
   README         (this file)
   TEST1.*        Installation test
                  (must run in this directory)
   TRAILER        Message from installation; can be deleted
   VP.BAT         Parses .FFP into .`C' (drives PARSER.EXE)
   VC.BAT         Compiles .`C' into .OBJ (drives Microsoft
                  `C' compiler)
   VL.BAT         Links .OBJ into a simulator (drives
                  PLink86 linker)
   VSPS.EXE       The VSP Simulator program
   (others)       Used by installation test

\ZORAN\VSPUTILS (VSPS helpfiles and miscellaneous)
   (several)      Used in simulator execution and user simulator linking

\ZORAN\VSPE (VSPE board support files, if installed)
   *.OBJ          Object files for creating user simulators
                  with VSPE support
   *.HEX          VSP files for board test
   INSTALL1.BAT   From installation; can be deleted
   VSPE_B.LNK     Beginning of link with VSPE support
   VSPE_E.LNK     End of link with VSPE support
   VSPTEST.EXE    Board test (runs only in this directory)
   LOADTEST.DAT   Used by board test

\ZORAN\VUSER (Your source files go here)
   NULLFILE       Used for installation; can be deleted

     NOTE: You can make other VSP user directories, but they must have \ZORAN as
     their parent directory.  Choose any names other than the directory names
     listed above (\ZORAN\VUSER can be renamed).
     

5.2  Directories and Files for Creating User Simulators

Files            Suggested   If elsewhere, change

Microsoft `C' ("MSC") \MSC   `PATH' in \AUTOEXEC.BAT
MSC `.H' files   \MSC\INC    `SET INCLUDE' in \AUTOEXEC.BAT
MSC `.LIB' files \MSC\LIB    

PLink86 Linker   \UTILS      `PATH' in \AUTOEXEC.BAT
OVERLAY.LIB      \UTILS      `SET OBJ' in \AUTOEXEC.BAT

MATH.LIB         \MSF        \ZORAN\VM\E.LNK
FORTRAN.LIB      \MSF        \ZORAN\VM\E.LNK

(The rest of the FORTRAN compiler files are only required if you develop VSP
applications using the FORTRAN language.)

Other FORTRAN    \MSF        `PATH' in \AUTOEXEC.BAT
compiler files

5.3  Filename Extensions

The following DOS filename extensions are used by the VSP Simulator package:

Extension         Used for

.BAT              DOS batch (command) file
.BIN              VSP object code (binary)
.C                `C' source (or Parser output)
.CK               Intermediate file produced by Parser
.DAT              Installation test data
.ERR              `C' or FORTRAN compilation error file
.EXE              MS-DOS executable program
.FFP              VSP source code
.FOR              FORTRAN source
.GEN              Installation test data
.H                `C' header ("#include") file
.IEE              Installation test data
.INP              Installation test input (keystrokes)
.LER              Link error file
.LNK              Link instructions for PLink86 linker
.MAP              Link map of user simulator
.MSG              Simulator help files
.OBJ              Object code (`C' or FORTRAN compiler
.PH               Intermediate file produced by Parser
.SPS              Installation test data
.SUB              Intermediate file produced by Parser
.TST              Installation test commands
.TXT              Text files (human-readable)
.(none)           Macro files, or installation text files

6  TESTS

6.1  VSPS Installation Test

The Installation Test verifies proper installation of the Simulator files.  This test
is performed automatically at the end of the automatic installation procedure.

To run this test, go to the \ZORAN\VM directory and enter:

     TEST1

This test takes several minutes to complete.  Expect a message with the words
"completed with no errors".


6.2  User Simulator Creation Test

The User Simulator creation test checks that the Parser, Microsoft `C' Compiler,
Microsoft FORTRAN library files, and the PLink86 Linker are in place.

To run this test, go to the \ZORAN\VEXAMPLE directory and enter:

     CREATE  EXAMPLE1

This creates a user simulator called EXAMPLE1.EXE, which can then be run by entering:

     EXAMPLE1

This procedure, CREATE, is the same one you will use when creating your own User
Simulator.

You can test this user simulator via the command:

     TEST2

A user simulator takes up substantial space on the disk.  When satisfied with the
results of TEST2, enter the following commands to delete EXAMPLE1.EXE and several
other files which were generated by CREATE:

     CLEANUP  EXAMPLE1

     DEL  EXAMPLE1.EXE


6.3  VSPE Installation Test

(This section applies only if you have a VSPE board installed)

The VSPE Installation Test verifies proper operation of the VSPE board.  This test is
performed automatically at the end of the automatic installation procedure for the
VSPE software.

To run this test, go to the \ZORAN\VSPE directory and enter:

     VSPTEST

This test takes several minutes to complete.


6.4  User Simulator Test with VSPE support

This test checks the operation of the VSPE board with a user simulator, and is
similar to the test described in section 6.2.

On the \ZORAN\VEXAMPLE directory, create a user simulator with VSPE support from the
VSP source file EXAMPLE1.FFP:

     CREATE  EXAMPLE1  VSPE

To start the test, enter:

     TESTVSPE
7  RUNNING THE SIMULATOR

To run the Simulator, go to the \ZORAN\VM directory and enter:

     VSPS

You can also run the Simulator or its command files from any sibling directory of
\ZORAN\VM.  (For this to work, the DOS PATH must be set properly.  See section 3,
"Configuring the PC").

You will typically use the directory \ZORAN\VUSER when developing your own ("user")
simulator from VSP source code.  During the Installation Test the Simulator expects
the current directory to be \ZORAN\VM.

     NOTE: The current release of the Simulator cannot be run from any directory
     whose parent is not \ZORAN, since it expects certain of its files to be
     located in \ZORAN\VSPUTILS, which is a sibling of \ZORAN\VM.
8  DEVELOPING USER SIMULATORS

To develop your own VSP code using the simulator facilities, you create a `user
simulator' by parsing and compiling your code, then linking the resulting object code
with the rest of the simulator.  The directory \ZORAN\VUSER is provided for user
simulator files, but you may rename this directory or create one or more sibling
directories for your VSP code (e.g. \ZORAN\MYPROJ1, \ZORAN\MYPROJ2, etc).

     NOTE: In the present VSPS release, user simulators will not operate on any
     directory that is not a sibling of \ZORAN\VSPUTILS.


8.1  Single User Module (Simplest Case)

The simplest way to create a user simulator is by putting all VSP and `C' source code
in a single module:

a) Write VSP source code, possibly intermixed with `C' statements, using your
   favorite text editor.
   
   This source file must have the `.FFP' extension and must reside on a directory
   whose parent is \ZORAN.  (Here we use `EXAMPLE1.FFP', a file found on
   \ZORAN\VEXAMPLE)

b) Parse the VSP source (e.g. EXAMPLE1.FFP) into a `C' source file (e.g. EXAMPLE1.C),
   using the VP command.  Omit the `.FFP' extension:

     VP  EXAMPLE1

c) Compile the `C' source code created by the parse operation (e.g. EXAMPLE1.C),
   using the VC command.  Omit the `.C' extension:

     VC  EXAMPLE1

d) Link the resulting object code (e.g. EXAMPLE1.OBJ) to create a user simulator
   (e.g. EXAMPLE1.EXE).  Omit the `.OBJ' extension:

     VL  EXAMPLE1

As an alternative to `b' through `d' you can VP, VC and VL in one operation by
entering:

     CREATE  EXAMPLE1

e) Run your user simulator by entering its name, e.g.:
   
     EXAMPLE1
   
   and invoke the `vspop' option from the Main Menu to test your application code
   using the full power of the VSPS facilities.  The `vspop' function in your .FFP
   module is the entry point to your application.

8.2  Single user module with VSPE support

If the VSPE board and support software have been installed, you can include VSPE
board support in your user simulator via the second form of the `CREATE' and `VL'
commands.

Following the example of the previous section:

     CREATE  EXAMPLE1  VSPE
     
or

     VL  EXAMPLE1  VSPE

Run your user simulator by entering its name, e.g.:

     EXAMPLE1

The `VSP Evaluation Board Control' option of the main menu leads to a submenu which
enables you to control the VSPE board and invoke your code (`vspop' function).  As
before, the `vspop' function in your .FFP module is the entry point to your
application.


8.3  Multiple User Modules

Creating a user simulator from multiple user modules is similar to the single-module
case, with several additions.  Modules can be VSP source (.FFP), "C" (.C), or FORTRAN
(.FOR).  The files EXAMPLE4.FFP, FORPACK.FOR, and EXAMPLE4.LNK on \ZORAN\VEXAMPLE
form a multi-module example.

Follow these steps:

a) Only one .FFP module (here, EXAMPLE4.FFP) provides a `vspop' function.

b) Parse all .FFP sources, then compile `C' sources (VC...) and FORTRAN sources
   (VF...) into object files.  In our example we would do the following:
   
     VP  EXAMPLE4
   
     VC  EXAMPLE4
   
     VF  FORPACK

c) Provide a "link file" -- a short text file which tells the linker how to link your
   multiple-module simulator.  The link file should:
   
   * have the same name as the file which defines `vspop',
   * have the extension`.LNK',
   * must consist exclusively of one or more lines of the form:
   
     FILE  name1  name2  name3 ...
   
   where the `names' are the names of you compiled object modules.  Each line is
   terminated by carriage-return/linefeed.  PLink assumes `name' means `name.OBJ', so
   omit the `.OBJ' suffix unless you use a different one.
   
   In our example, the link file EXAMPLE4.LNK contains the following line:
   
     FILE  example4  forpack
   
d) Link the user simulator as you would a single user module.  For example:
   
     VL  EXAMPLE4
   
   Again, we could have performed only the following two steps:
   
     VF  FORPACK
   
     CREATE  EXAMPLE4
   
   CREATE and VL automatically perform a multiple-module link if they find a .LNK
   file of the proper name.  The link file is combined with \ZORAN\VM\B.LNK and
   \ZORAN\VM\E.LNK, which PLink86 uses to link the user simulator.
   
   If no link file is found, CREATE and VL perform a single-module link.


8.4  Multiple user modules with VSPE support

If the VSPE board and support software have been installed, you can include VSPE
board support in your user simulator via the second form of the `CREATE' and `VL'
commands just as with single user modules.  Following the example of the previous
section:

     CREATE  EXAMPLE4  VSPE
     
or

     VL  EXAMPLE4  VSPE
9  CHECKLIST

a. Requirements (section 2)

     * PC/AT or close compatible, and DOS 3.1         (  )
     * At least two megabytes available on hard disk  (  )
     * 640K RAM                                       (  )
     * No resident programs over 5K long              (  )

b. Getting started quickly (assumes `Requirements' are met)

     * Automatic installation (A:INSTALL) performed:  (  )
     * If graphics display, TERMINAL.ID deleted
          from \ZORAN\VM directory                    (  )
     * CONFIG.SYS includes `DEVICE=ANSI.SYS'          (  )
     * ANSI.SYS file is on PC's root directory        (  )
     * PC has been rebooted so changes to CONFIG.SYS  (  )
       and AUTOEXEC.BAT take effect
          
c. For developing user simulators (assumes `a' and `b')

     * AUTOEXEC.BAT: PATH includes
          \ZORAN\VM                                   (  )
          Microsoft `C' directory                     (  )
          PLink86 directory                           (  )
     * Microsoft `C' compiler installed               (  )
     * AUTOEXEC.BAT: SET INCLUDE specifies
          Microsoft `C' header (*.H) file directory   (  )
          \ZORAN\VM                                   (  )
     * AUTOEXEC.BAT: SET OBJ specifies                (  )
          location of PLink86 `OVERLAY.LIB' file
     * PC has been rebooted so changes to CONFIG.SYS  (  )
       and AUTOEXEC.BAT take effect

d. For FORTRAN compilation (optional)

     * Microsoft FORTRAN compiler installed           (  )
     * AUTOEXEC.BAT: PATH includes
          Microsoft FORTRAN directory                 (  )
     * PC has been rebooted so changes to CONFIG.SYS  (  )
       and AUTOEXEC.BAT take effect

e. For creating user simulators with VSPE support

     * VSPE Automatic installation (A:INSTALL) performed:  (  )

