This directory includes the following files associated with the precompiled
gopher client version 1.2, patchlevel 0, for VMS.
 GOPHER_MN.EXE
 GOPHER_UCX.EXE
These are precompiled executables for MultiNet and UCX.  The default server
for these is Niord.SHSU.edu, port 70.  Copy these files to a system area
(we use SYS$COMMON:[SYSEXE]) and make a symbol pointing to the appropriate
executable for the TCP/IP package in use.  For example, if your system runs
MultiNet, use:
$ GOPHER :== $GOPHER_MN
and if your system runs UCX, use:
$ GOPHER :== $GOPHER_UCX
In a mixed TCP/IP environment (such as we have at SHSU), an evaluation of
the node name may be used to define the proper GOPHER symbol on your
system.  For example:
$ if f$getsyi("nodename") .eqs. "FREYA" then gopher :== $gopher_mn

Once defined as symbols, the executables can be used in a general
environment with the syntax:
$ GOPHER <hostname> <port_number>
Issued without a <hostname> or <port> is equivalent to the command line:
$ GOPHER Niord.SHSU.edu 70
Issued with a <hostname> (say, sci.wfeb.edu) but no <port> is equivalent to
the command line:
$ GOPHER sci.wfeb.edu 70

Also included and required by the definitions used to compile and link
these executables are:
 GOPHER.HELP
 GOPHERPRINT.COM
 GOPHER.TPU
To work as-is, each of these three files should be copied to a common
directory with /PROTECTION=W:RE (so that users can access them).  This
common directory should be included as a system logical GOPHER_DIR, such
as:
$ DEFINE/SYSTEM/EXECUTIVE_MODE GOPHER_DIR device:[directory]
(I don't know if the /EXECUTIVE_MODE is required or not; that's how I
defined it here and it works, so...).

GOPHER.HELP is the on-line help which is returned by a "?" at the
menu prompt entry.

GOPHERPRINT.COM is the command file to drive proper printing using the VMS
Queue Manager.  By default, the queue which this points to is SYS$PRINT. 
The headers in the file provide documentation on setting a specific print
queue.  Briefly, to use the print queue named MY_QUEUE, include the
following line in your LOGIN.COM file:
$ DEFINE GOPHERQUEUE MY_QUEUE
If you wish to use an attached printer, include:
$ DEFINE GOPHERQUEUE PORT

GOPHER.TPU is a TPU command file for use with the VMS Gopher client.  It
does very little, beyond instruct the user to press control-Z to exit, but
it is good for information purposes to people not accustomed to the TPU
editing environment.  By default (last line of the code in GOPHER.TPU), the
EDT-style keypad is used by this command code.

Again, all files should copied to a common directory which translates to the
system-level logical GOPHER_DIR: and files should be copied with
COPY/PROT=W:RE so that users may access them.

The files LYNX_MN.EXE and LYNX_UCX.EXE are precompiled executables for the
Lynx (version 2.0.10) hypertext viewer for VMS running under MultiNet and
UCX, respectively.  The 1.2 VMS gopher client allows for the use of a
Hypertext viewer (i.e., World Wide Web, WWW) and this option is included in
the precompiled versions of the executables included in this directory. 
Copy these files to a system area (as for the client executables, we use
SYS$COMMON:[SYSEXE]) and make a symbol pointing to the appropriate
executable for the TCP/IP package in use.  For example, if your system runs
MultiNet, use:
$ LYNX :== $LYNX_MN
and if your system runs UCX, use:
$ LYNX :== $LYNX_UCX
In a mixed TCP/IP environment (such as we have at SHSU), an evaluation of
the node name may be used to define the proper LYNX symbol on your system. 
For example:
$ if f$getsyi("nodename") .eqs. "FREYA" then lynx :== $lynx_mn

Finally, the file GOPHER.HLP is included in this directory.  It is a VMS
Help Librarian text file which may be inserted in your system help tables
for on-line reference about the gopher client.  For example:
$ LIBR/HELP/INSERT SYS$HELP:HELPLIB.HLB []GOPHER.HLP
will insert the file.  If you already have the file and wish to update to
the one in this directory, use LIBR/HELP/REPL .....

The file GOPHER1_2VMS0-CLIENT.ZIP is a complete distribution of the gopher
client sources for VMS as of version 1.2, patchlevel 0.

The file LYNX2-0-10.TAR includes the source set to build Lynx and the file
VMS_WWWLIB.TAR includes the library required to build the Lynx distribution
above.