       INSTALLATION INSTRUCTIONS       VT-241 Color Management Software     Version 3.1      April, 1987       H Having a VT-241 (or other color REGIS terminal) is much more fun if you G use color combinations other than Red-Blue-Green.  These programs make  H it easy for the user to control his/her terminal colors.  A side-effect A is that a user connecting a VT-241 is immediately given a set of   pleasant colors.  D Since there is no way to tell if a terminal is a VT-240 or a VT-241 ; (REGIS monochrome or color), the programs key on the REGIS  F characteristic. VT-240s handle the color commands OK.  We have little ( experience with other REGIS terminals.       FILES IN [COLORS]   ? Program Sources, Etc.	   Sources, executables, link files, etc.   < Documentation		   In 3 forms: .TXT, .WPL for use if you use E                            WPS-PLUS, and .LN03 to print nicely on an  (                            LN03 printer.     FILES IN [COLORS.MANAGER]   9 Colors.Hlp		   A second-level help fragment which can be  6                            added to your help library.  B Color_Symbols.Com	   A fragment to be executed from whatever part G                            of Sylogin points to symbol definitions for  %                            all users.   4 Fix_CRT.Scr		   When typed, this file restores some F                            commonly-garbaged terminal characteristics I                            (turns cursor on, sets window to full screen,  H                            restores tabs to "every 8", etc.)  Note that J                            this file is helpful for all VT2xx terminals.  H                            (File extension .SCR is used for files which :                            affect screen characteristics).  E Restore_Colors.Com         Types fix_crt.scr and (if regis terminal)  F                            sets colors to "the last reasonable set".  F                            Useful after something (set-up or program) B                            has set terminal colors to monochrome, 0                            red-blue-green, or...  ? Set_Colors.Com		   System .com file, executed (somewhere) from  I                            sylogin, which does something "reasonable" at  E                            user login.  Look at the file for details.   6 Sylogout.Com_Fragment	   Add this to your Sylogout.Com  I System_Default_Colors.Scr  A pleasing set of colors for the user who has  D                            no other preference (or new user).  This E                            becomes "the" system default, and you may  E                            rename any Current_Colors_Cmd.Scr file to  @                            change it if you don't like this set.  1 User_Logout.Com		   ONLY needed if you don't use  E                            Sylogout.Com_Fragment. In that case, some  6                            users will need to do this.  E Installer's Documentation  In 3 forms: .TXT, .WPL for use if you use  E                            WPS-PLUS, and .LN03 to print nicely on an  (                            LN03 printer.                            g- And 2 "fun" files:  These files can be typed.8  < Black.Scr		   Sets all 4 colors to Black.  Mail this one to I                            your friends.  (Note: Typing OCO "blind" will e7                            get you out of this pickle).   7 Colorbar.Tst		   Does the color terminal test sequence.       Operating Philosophy of Programs  F oo  If the terminal is not ReGIS, do nothing (except OCO); otherwise,  G oo  If the user does nothing, always set the system default colors at G login.  ) oo  Provide user flexibility as follows:d  F      Users may run programs to select their own colors (explicitly or I      randomly).  If they do, the selected colors will stay with the user ,G      "forever" (are not changed to system default at any login).  This  E      is accomplished by writing a file Current_Colors_Cmd.Scr in the  D      user's SYS$LOGIN directory.  Two other files are written there:  ; 	  Current_Colors.Scr (for subsequent use by programs) and  (           Did_Colors.Before (see below).  I      Users may "do their own thing" by putting a Set_Colors.Com in their pG      SYS$LOGIN directory.  This will be executed at first login.  Some fE      users (like me) like to use this to get a fresh set of "random" p:      colors each day [my Set_Colors.Com contains "$ NCO"].  F oo  For users who do multiple logins (SET HOST 0, Clusters, Terminal F Servers), the user's selected colors are not switched at each login - < until the user logs out once.  The selection programs write 0 Did_Colors.Before, which is destroyed at logout.     Operating Sequence at Login   6 1.  If the user has a DID_COLORS.BEFORE, Go To Step 3. 								         ELSE  3 2. Execute the user's SET_COLORS.COM if it exists.     ELSE x  D 3. Type SYS$LOGIN:CURRENT_COLORS_CMD.SCR if it exists. This file is G created by the NCO, CCO, PCO or XCO commands. This sets up the default e color scheme for a user.   ELSE    I 4. Type SYS$UTILS:[COLORS.MANAGER]SYSTEM_DEFAULT_COLORS.SCR. This is the   system default color setting.o     Directory Structure   : The structure is set up to have all executable programs in      SYS$UTILS:[COLORS]c, and manager & .COM files in the subdirectory      SYS$UTILS:[COLORS.MANAGER]k  B If this doesn't match your system requirements, edit the following- files to replace entries beginning SYS$UTILS:p      SET_COLORS.COM       RESTORE_COLORS.COM       COLOR_SYMBOLS.COM     Command Structurer  @ The following commands are defined in COLOR_SYMBOLS.COM, and may be changed as you wish:   F      CO	  Runs Set_Colors.Com (Gets any user some set of colors).  If F           the user has a SYS$LOGIN:SET_COLORS.COM, It will pass all 8 H           parameters to SET_COLORS.COM. This allows the user to have up B           to 8 different color settings, i.e. CO 4 would pass the I           parameter 4 to the user's SET_COLORS.COM which could then type ,           color file 4.   H      OCO  Used if terminal is garbaged - runs Fix_Crt & restores colors.  7      NCO  Gets a new set of random, contrasting colors.   C      CCO  Gets a new set of random, complementary ("artsy") colors.   2      PCO  Lists 64 choices and lets the user pick.  -      XCO  An interactive/visual user chooser.n  B The acronyms (sort of) stand for: Colors, OLD Colors, NEW Colors, 8 COMPLEMENTARY Colors, PICK Colors, and (X)CHANGE Colors.     Installation  I In addition to any required editing of the 3 .COM files, and putting the n, files somewhere, the following are required:   1.  Put the command:+      @SYS$UTILS:[COLORS.MANAGER]SET_COLORS H somewhere in your SYLogin structure.  It must come after the last place D you do a SET TERM/INQUIRE (which sets the colors to Red_Blue_Green).  < HINT: If you run All-In-1 V2.1, you may put this command in = SYS$MANAGER:A1WPSPLUS_LOGIN.COM. It goes only in the section iD SETUP_FOR_VT200: after the loadtcs line and just before "GOTO done".   2.  Put the command:.      @SYS$UTILS:[COLORS.MANAGER]COLOR_SYMBOLS $ somewhere in your SYLogin structure.  5 3.  Edit SYLOGOUT.COM_FRAGMENT into your SYLogout.Comw  3 4.  (Optional) Add COLORS.HLP to your help library.S  F 5.  (Optional) Edit (add) a line "$ OCO" as the last line in any .COM F files you have which handle programs which destroy color setup.  This H will automatically restore your color settings.  Known examples of this # are DECGraph, DECSlide, and VAXSim.u  , 6.  Publish the users' guide for your users.     Hints & Other Info  K oo  OCO is useful in many instances where your terminal gets fouled up by T
 some program.o  J oo  Some third-party terminals and (particularly) terminal emulators may G not like these programs.  We know of some which "lie" to SET TERM/INQ,  C and others which don't properly exit from REGIS mode when sent the  & standard sequence ( <ESC>\ ).  [Sigh!]  F oo [COLORS] contains the FORTRAN programs.  AA_BUILD_COLORS.COM will H compile and link all of them.  Individual link .COMs are also provided. . All of the programs use COMMON.FOR/COMMON.DAT.  I oo  PikColors (PCO) and Color_Changer (XCO) use the SMG$ for screen and o. keyboard management (and link with Color_SMG).  G oo  If you manage several non-clustered VAXen, one potentially useful aE trick is to set up a different set of colors (CURRENT_COLORS_CMD.SCR  E files) on each machine.  Then you never have to wonder which machine i
 you're on.  J oo  Is_ReGIS.FOR is a useful logical function to determine if a terminal F has ReGIS capability.  It could be easily modified to determine other 
 capabilities.d  I oo  NOTE: VT-241 terminals must be SETUP to do Mono + Color Display, or tI the PCO and XCO programs will not work properly.  There does not seem to s& be a convenient way to check for this.    5 Attributions: (All at Los Alamos National Laboratory)w  . Jim Whitfill, System Manager - the .COMs, etc.: Tom Beery - Initial implementation of Color_Changer (XCO).8 Dennis Hall - Initial implementation of PikColors (PCO).     Comments, Bugs, Suggestions:        Dale E. Coy#      Los Alamos National Laboratorys      Group MEE-8, MS/J957a      PO Box 1663      Los Alamos, NM 87545         (505) 667-3270 or 667-7159o      FTS 843-3270 or 843-7159   