If you have any questions, please call.
			-- Tony Ivanov
			tony@gvgpvd.GVG.TEK.COM
			(USA) 916/478-3238


Here are some important tips to get VMS Curses working for you!

First, you must have a TERMCAP file.  Next, you must either modify
the termcap file or set up a logical name for your terminal type.
Third, you must tell VMS curses where to look for the termcap file.

The termcap file should be 'SYS$LIBRARY:TERMCAP.'.  If you choose to
not put it there, you need to set up a logical name (or symbol)
that points to it.  Logical names override symbols.  As an example
of setting up a non-standard termcap file, assume you wish to put
it in SYS$USERS:[OURLIB.LIB]TERMCAP.VMS, you should then set up a
logical name of:
	$ ASSIGN/SYS "/SYS$USERS/OURLIB/LIB/TERMCAP.VMS" TERMCAP
Note, you *must* have a slash (/) at the beginning.

Users can use their own copy of termcap by creating a process-wide
logical or a symbol with above format.  Example:
	$ ASSIGN "/my$disk/my$home/LIB/TERMCAP." TERMCAP
		or
	$ TERMCAP == "/my$disk/my$home/LIB/TERMCAP."
Remember, logical names (including system-wide logical names) over-
ride symbols.

By default, the environment symbol TERM is assigned to your terminal
type (as indicated by show term) followed by a dash followed by the
page width.  To override this and use a pre-defined TERM, set up a
logical name that equivalences TERM with the proper terminal type.
Be sure to enclose the equiv. name in quotes if lower case letters
are in use.  Example:
	$ ASSIGN "vt100" TERM
To make things simple for naiive users, I have modified our termcap
file to alias vt100-80 to vt100 and vt100-132 to vt100-w.
IMPORTANT NOTE: a symbol definition for TERM will *NOT* work.

			-- Tony

-- 
/* My opinions...             *  Tony Ivanov   MS-4B       *  ...ucbvax!   */
/* shared by my company?!...  *  Grass Valley Group, Inc.  *  tektronix!   */
/* you've got to be kidding!  *  P.O. Box 1114             *  gvgpsa!      */
/* "tony@gvgpvd.GVG.TEK.COM"  *  Grass Valley, CA  95945   *  gvgpvd!tony  */