Date: 3/9/93
Rev: 1.2

               SGL V1.16 - The programmer's notes
               ----------------------------------

SGL, meaning "Small memory GL" is a stripped down version 
of the normal GL program.  This allows the developer to 
provide support for the G-Lock in his/her program with a
reduced memory-hungry version of the GL program.  Also,
since SGL is provided with every G-Lock, your program 
will also have access to the SGL program as desired.

Removed items:
  * User interface
  * Hotkeys (both 1.3 and 2.0 style)
  * ILBM Loading
  * (With this: ECS/AA key handling)
  * Requester code (now using AutoRequests)
  * Arexx commands dealing with the above (they
        don't give error returns, the just don't
        do anything)
  * Some ToolTypes parsing.
  * Most CLI parameters.

The big advantage here is the amount of memory consumed,
and measuring under WB 2.05 (A600) starting SGL from
Workbench gave us a memory usage of 26232 bytes when
SGL was running. All of this memory can be allocated
as FAST memory. The program size is a mere 3072 bytes.

To not confuse the user SGL can be terminated easily:
Just execute either SGL or GL. This will bring up
a requester informing the user that SGL just quit,
and that they now can select GL to bring up the
user interface (Tech note: In other words, SGL _quits_ 
with a requester when it receives the "ACTIVATE" 
message. Convoluted but clever...)

CLI Options Supported:

    FORCEPAL
    FORCENTSC
    CHECKINTERVAL n
    PRIORITY n
    MODE (BYPASS | GENLOCK)
    NORESETREQUEST
    TOLERANCE n
    SETUP n
    SYNC
    PARALLEL
    MAXBRIGHTNESS n
    MINBRIGHTNESS n
    LACEON
    LACEOFF

TOOLTYPES Supported:

     SETUP n
     LACE=(ON | OFF)
     FORCE=(NTSC | PAL)
     MAXBRIGHTNESS=n
     MINBRIGHTNESS=n
     CHECKINTERVAL=n
     PRIORITY=n
     MODE=(NORESETREQUEST | BYPASS)
     SWITCHER=SYNC
     PARALLEL=TRUE     
     
All of these work as they do in the full-blown GL.

Please note that the user does really not need ARexx to be
running when you wish to send ARexx commands to SGL (or GL
for that matter).  Sending the G-Lock ARexx commands directly
works quite well, thus the developer can even reduce the 
memory burden on the system further by having the user never 
run the ARexx server.

1993, Jesper Steen Møller