INSTALLATION NOTES FOR THE GIGI TOOL KIT -- VMS VERSION

This tape should be read into a single VMS directory.  It contains all the
sources needed to build the following GIGI tools:

	HC2X	 - generate double-sized hard copy on the LA34VA printer,
		   from a file of ReGIS graphics.
	DIGITZ	 - use the Summagraphics Bit Pad to digitize a hard copy
		   image, generating a ReGIS file.
	DIGITIZE - a version of DIGITZ that runs in GIGI BASIC.
	RBOS	 - support the use of GIGI BASIC OLD, SAVE, and HOST commands,
		   using the host as a file server.
	PROGKEY  - help the user to program GIGI's programmable keys.
	PCU	 - pie chart utility, a program for generating pie charts
		   from data files.
	COPYSHOW - a VMS DCL procedure to copy a GIGI Slide Projector tray
		   file plus all ReGIS files referenced by it.

This tape contains a DCL procedure, MAKEGIGI.COM, that will generate all
the above tools.  The only other user action needed after running MAKEGIGI
is to define the GGLIB logical name and to place certain files into the
directory defined as GGLIB.

HC2X, DIGITZ, and RBOS are Fortran programs generated from several libraries,
as well as their respective main programs.  The build procedure first
compiles the libraries, and then generates those tools.

PROGKEY is a VMS BASIC program that requires no other programs or libraries.

PCU is a VMS PL/1 program that includes its own library.  It also requires
the MACRO-32 library used by the Fortran routines.

DIGITIZE is a GIGI BASIC program that is simply loaded by RBOS, and then
RUN in the GIGI terminal.

COPYSHOW is just a VMS DCL procedure, and is ready to use.

COPYSHOW, DIGITZ, PCU, and RBOS each have a "help" file, of file type ".hlp".
HC2X and PROGKEY are self-explanatory.

Both RBOS and DIGITZ have a VMS DCL command procedure (with the same name)
that should be used to invoke the .EXE file created by the build
procedure.  These command procedures assume that the files are located
in a directory accessible through the "GGLIB" logical name.

Also, PCU and HC2X both refer to the logical "GGLIB" internally to access
the help file, in the case of PCU, and the file HC2X2.GGM in both of them.
Note that the logical "GGLIB" is required for some of the GIGI software
products distributed by Digital, and if those software products are
installed, that will require you to place those files in that same
directory.  (Of course, the source code could be changed to refer to
another logical.)


Note:  the Fortran files were created from Ratfor sources using a Ratfor
preprocessor.  The Ratfor sources have been included as an aid to user
maintenance of the tools.  The preprocessor used is similar but not
identical to other versions of Ratfor;  thus the user wishing to re-generate
the Fortran using the user's Ratfor preprocessor (if available) may
need to make some changes to the Ratfor code.  Most changes needed
concern the unique Ratfor statements "stringdata" and "stringdcl", which
generate Fortran data and declarative statements, respectively, as an
aid to defining character arrays.

The use of Ratfor is not required, however, to build and run these tools.