RELEASE NOTES
                                      13 May 87
                                      20:49:47



               1.  This version of GKS requires FPU hardware.  

               2.  GKS uses ILUN to decide whether or not a FORTRAN logical
                   unit has been opened.  The F77 and FORTRAN IV  run  time
                   systems  use different versions of ILUN.  When using the
                   F77 run time system, ILUN traps out with error 20 if the
                   LUN has not been previously opened.  This means that you
                   must open FORTRAN output files prior  to  calling  GOPWK
                   when  using F77, but it should not be necessary when us-
                   ing FORTRAN IV (although this has not been tested).  The
                   safest  bet is to open the graphics output file prior to
                   calling GOPWK.  

               3.  The  connection  ID  for  the  error file in the call to
                   GOPKS is not currently being used.  All output is  going
                   to the console via the .PRINT macro.  

               4.  GKS Level MA doesn't specify any way to "PAUSE" graphics
                   output.  This means that on the Tek 4107 and the  Visual
                   550,  the picture is generated and then immediately dis-
                   appears.  There are at least  two  ways  to  get  around
                   this,  neither  of  which has been implemented yet.  One
                   way is to implement the PAUSE fuction as an ESCAPE func-
                   tion  for  each driver.  The other way is to incorporate
                   input commands from higher levels of GKS (e.g.   LOCATOR
                   input).  A third less satisfying method, might be to up-
                   date the workstation (GUWK) and  then  ask  for  FORTRAN
                   input  (ACCEPT, READ etc.).  This may not work in future
                   releases however.  

               5.  GQCF  (Inquire Color Facilities) and GQCR (Inquire Color
                   Representation) are just stubs.  They  return  undefined
                   values.  

               6.  The  only  error conditions that produce any results are
                   errors 1, 2, 6, 7, 8, 20, 21, 63 and 85.   These  errors
                   produce  error messages.  Distinctions are not currently
                   made between fatal and non-fatal errors.  One of the im-
                   portant  projects for Version 1.00 will be to make error
                   handling consistent for all defined errors.   Hopefully,
                   a  mechanism  will  be found to allow the user to remove
                   the error code after debugging, to provide more room for
                   executable code.  












                                         -1-