Meridian Installation Instructions

Sage-ST ^TM 4.1

(Meridian 286)

Graphics libraries, tools and libraries have been included. Make sure that the 16 BIT EXTENDED MODE COMPILER is loaded BEFORE running the installation process. This is done by running the ADAEXT.BAT file.

To install Sage-ST ^TM , type

        A:INSTALL
        or
        B:INSTALL
        or
        A:INSTALL ? (where ? = C, D, etc. = destination drive)

The library may be installed using one of two methods.

1. Sage-ST ^TM may be installed in its own directory (eg. C:\Sage-ST) and then you can create a project library (eg. D:\PROJECT\ADA.AUX) with a link back to Sage-ST ^TM .

Advantage - Only one copy of Sage-ST ^TM is required for multiple projects that 'with' Sage-ST ^TM packages.

Disadvantage - If any of the HelpLib, CheckLib or FormChk packages are used in the project the package body must be compiled directly into the Sage-ST ^TM library, not into the project library. In this case these packages cannot 'with' any of the non-Sage-ST ^TM packages. If you are using overlays and want to overlay any of the Sage-ST ^TM code this will require a little more work as \ you must put back OBJ files that are removed for overlays when compiling other projects.

2. Sage-ST ^TM may be installed into the project directory as the development library (e.g., D:\PROJECT\ADA.AUX).

Advantage - Compiling any of the HelpLib, CheckLib or FormChk packages requires only a compilation of a package body into the development library. These packages may 'with' any of the other non-Sage-ST ^TM packages. If you are using overlays this is easier to keep the library setup which works best for the project.

Disadvantage - Multiple copies of Sage-ST ^TM may exist on the system. Initial setup and going to new versions would require multiple installations of the library.

NOTE: If you are not using graphics on a project, you may want to delete the graphics packages in order to save space, especially if you are using multiple copies of the library. REMOVING GRAPHICS gives instructions on how to perform this procedure.

This example will cause a load from the source drive (A, B, C, etc.) to the current drive or destination drive (if specified as in the last example). The following drives and directories are used by default: Sage-ST ^TM _Library

        C:\SAGE\MERIDIAN
        Contains the ADA.LIB and some .OBJ files for Sage-ST
        ^TM
        4.1
        C:\SAGE\MERIDIAN\ADA.AUX
        Contains the rest of the OBJ and .INT files for Sage-ST
        ^TM
        4.1
        C:\MERIDIAN\TEST
        Contains test program, CHECKER.EXE, and sample .BAT files. This will
        always be in the "\MERIDIAN\TEST" directory on the same drive as that
        chosen for the main library (ADA.LIB).
        C:\MERIDIAN\GRAPH
        Contains the graphics fonts (*.FNT files) and the graphics tools,
        SAGERC.EXE and SAGERDIR.EXE, as well as the skeleton body of
        SGKDRIVE.ADB. SGDemo.EXE is also included for demonstration. A
        library (C:\MERIDIAN\GRAPH\ADA.LIB) is also linked to
        \SAGE\MERIDIAN\ADA.LIB for use as a development directory.

THOR/REBUILD

        C:\ADA\THOR
        Contains the THOR.EXE and REBUILD.EXE programs and associated files.

CONFIGR/MONITOR/LOG

        C:\ADA\PROGRAM
        Contains the CONFIGUR.EXE, LOGGER.EXE, and MONITOR.EXE and associated files.

GRAPL

        C:\ADA\GRAPL
        Contains the GRAPL.EXE program.

QBE

        C:\ADA\QBE
        Contains the QBE.EXE program and associated files.

SQL

        C:\ADA\SQL
        Contains the SQL.EXE program for interactive SQL.

TOOLS_COLLECTION

        C:\ADA\TOOLS
        A collection of tools such as BREAKUP, ADDFILE, SAGESTAT, etc.

DOCUMENTATION_ASCII

        C:\ADA\DOC
        Documentation of the library procedures and specification files in ASCII format. The files include
        SAGEDOC.ACD procedure/function documentation
        SAGEDOC.ACS specification file listing
        The complete documentation in WordPerfect format is on a separate disk.
        A file called REF.MER which documents the Meridian specific libraries included with
        Sage-ST
        ^TM
        is found on the documentation disks.

Should the LNLIB Library Manager commands not install properly, a \FAMBUILD.BAT file will be created which contains the appropriate Meridian commands which were attempted during installation. These commands may be modified and used as required.

This version of Sage-ST ^TM requires the DOS Meridian OpenADA 4.1.4 compiler. Please note that any earlier versions (4.1, 4.1.1, etc.) are incompatible with Sage-ST ^TM 4.1.

For further information, contact :

Sage-ST ^TM Development
Idaho National Laboratory (INL)
P.O. Box 1625
Idaho Falls, Idaho 83415-3770

(208) 526-0656

SUBTOPICS

Problems Porting Sage-ST ^TM to Meridian
Additional Idea for Improving Productivity
Using Overlays
Removing Graphics Go Back To Sage-ST TABLE OF CONTENTS