Product Name:           frc (bundle)
Product Version:        1.0
Date:                   October 7, 1994
Contents:               vx_frcv2.2, fb_frcv2.1, fbremv1.4

DESCRIPTION
-----------

This is a "bundle", containing three separate but related products:
vx_frc, fb_frc, and fbrem.  The products are related in the following way:
fbrem requires fb_frc, and fb_frc requires vx_frc.  There are three archive
files then, one for each product.  See the README files in each archive
for all pertinent information about a product, including its compatibility
requirements regarding the product it depends upon, if any.  A release
of the "bundle" will contain compatible releases of each product which
have been tested together.  The bundle's version number will increment
whenever ANY or ALL products within the bundle change.

The FASTBUS Readout Controller (FRC) is an embedded processor FASTBUS board
based on the LR33000 embedded CPU.  It was developed by the Fermilab
Computing Division's Data Acquisition Engineering Department.
It is now sold commercially by Bi-Ra Systems, under the DOE Technology
Transfer Program.  This product is the software
needed to take advantage of this board's capabilities.

frc is a bundle of software with three components:  vx_frc, fb_frc and fbrem.
vx_frc is the VxWorks Board Support Package (BSP) which is the necessary
basic operating software for the FRC board, under which everything else runs.
VxWorks is a proprietary real-time operating system, and its use requires
appropriate license from its producer, Wind River Systems, Inc.
fb_frc is an implementation of the IEEE FASTBUS Standard Routines for
the FRC board.  fbrem is a client library which provides transparent access
to fb_frc over a network via Sun's RPC (Remote Procedure Call) protocol,
supported on most UNIX platforms. With an appropriate linking procedure,
it should also run on VAX/VMS systems with appropriate third-party
networking software.  This may be supported in a future release.

FILES IN THIS ARCHIVE
---------------------

At this level, you should see:

README                  this file
README.vx_frc           README file for vx_frc product
README.fb_frc           README file for fb_frc product
README.fbrem            README file for fbrem product
vx_frcv<vers>.tar       archive file for vx_frc, version <vers>
fb_frcv<vers>.tar       archive file for fb_frc, version <vers>
fbremv<vers>.tar        archive file for fbrem, version <vers>

See README files for each product for complete listings of files contained
in that archive.

INSTALLATION
------------

First, uncompress the archive files with "uncompress" or "gunzip"
Unwind each archive for the product(s) you are taking into separate
directories.  For example, if you are taking all 3 products, and placing
them in "/usr/frc", you should create directories "/usr/frc/vx_frc",
"/usr/frc/fb_frc", and "/usr/frc/fbrem".  Unwind like this:

        cd /usr/frc/vx_frc
        tar xf <path_to_vx_frc_tarfile>
        cd /usr/frc/fb_frc
        tar xf <path_to_fb_frc_tarfile>
        cd /usr/frc/fbrem
        tar xf <path_to_fbrem_tarfile>

where <path_to_vx_frc_tarfile> means the location of the vx_frc tarfile
you obtained via FTP.  For example:

        tar xf ../vx_frc.tar

The archives are all taken at the version directory level to avoid
accidental overwriting of any previous versions you may have installed.
That is, vx_frc.tar will unwind into v2_2/...
At this point, you should refer to the README files in each product for
its installation instructions (don't worry, they are very similar).


LICENSING INFORMATION
---------------------

Please refer to the file named LICENSE in each product's archive.

ALL OTHER INFORMATION
---------------------

Please refer to README files in each product for supported platforms,
dependencies, documentation, build instructions, running instructions,
and other relevant information.