                          
                             INSTALLING BRIK 2.0

The following files should be in this package.

  name             description
  -----------      -----------
  addbfcrc.c       (generic) brik C source
  assert.h         (generic) brik C source
  brik.c           (generic) brik C source
  brik.h           (generic) brik C source
  initcrc.c        (generic) brik C source
  getopt.c         (generic) getopt function C source

  install          (generic) installation instructions
  brik.doc         (generic) formatted user manual
  crc.lst          (generic) CRCs -- verify with "brik -Cv"

  makefile.nix     (**IX) make file
  brik.1           (**IX) manual for formatting with "nroff -man"

  addbfcrc.asm     (MS-DOS/Turbo C) 8086 assembly code
  brik.prj         (MS-DOS/Turbo C) project file for tc.exe
  makefile.tcc     (MS-DOS/Turbo C) make file
  turboc.c         (MS-DOS/Turbo C) brik C source
  turboc.cfg       (MS-DOS/Turbo C) configuration file for tcc.exe

  descrip.mms      (VAX/VMS) make file
  makebrik.com     (VAX/VMS) script to compile and link
  options.opt      (VAX/VMS) options for linker
  vms.c            (VAX/VMS) brik C source

  makefile.msc     (MS-DOS/MSC) make file (not tested)

Brik is believed to compile and execute in the following environments:

1.   Turbo C 2.0, MS-DOS 2.x or higher
2.   VAX/VMS 4.7 with VAX/VMS C 2.4
3.   4.3BSD from Berkeley on a VAX-11/785
4.   Microport System V/AT version 2.2

Make sure all the needed files are in the current directory.  Then follow
instructions below for your specific type of system.  If doing so doesn't
give you a running copy of brik, read brik.h and experiment with the various
compilation options.

1.   MS-DOS, Turbo C 2.0

Examine the files "makefile.tcc" and "turboc.cfg".  Edit them if necessary
to make sure they have the correct names for your include and library
directories.

To use the command-line compiler, you will need a good make program such as
NDMAKE (tested with version 4.31).  Rename the file "makefile.tcc" to
"makefile" and follow instructions in it.

To use the Turbo C integrated environment, first convert the supplied
configuration file "turboc.cfg" to "tcconfig.tc" using the "tcconfig.exe"
program supplied with Turbo C.  A project file "brik.prj" is supplied. 
Assemble addbfcrc.asm using either Microsoft's assembler or Borland's Turbo
assembler (be sure to use the /mx switch).  Then compile as usual with the
integrated environment.

2.   VAX/VMS

2.1.   If you have DEC's make utility called "mms", proceed as follows:

     a.   Delete "makefile" so mms won't get confused
     b.   Type "mms" at the VMS prompt
     c.   If all goes well, mms will compile and link the necessary files,
          yielding "brik.exe" in the current directory.
     d.   Move "brik.exe" wherever you want it and define a symbol with
          a command line of the following type:

               $ brik :== $my$disk:[bindir]brik.exe

         where my$disk is the name of your device and bindir is the name
         of the directory in which "brik.exe" is kept.

2.2.  If you don't have "mms", use the command file supplied.  Invoke it as:

     $ @makebrik

When it exits, brik.exe should have been created in your current
directory, and the symbol "brik" should also have been defined for
you.  If you move brik.exe to another directory be sure to redefine the
symbol "brik" correctly as described above in part I.

Be sure to read the section in the manual on VAX/VMS bugs.

3.   4.xBSD, System V, and other **IX-like environments

Rename the file "makefile.nix" to "makefile".

Give the command "make sys_v" or "make bsd" as appropriate.

If you are using Ultrix, you may wish to type "make ultrix" rather than "make
bsd" to get around an Ultrix bug described in "brik.h".

If you wish to use the large model library under Microport System V/AT, type
"make uport".  To use the default small model library, type "make sys_v".

                                  -- Rahul Dhesi
                                     1989/07/11
