	VAX Fpaint installation, build procedure, and suggested definitions
	-------------------------------------------------------------------

	To restore the Fpaint tape, create and set default to an empty
	directory and follow the restore procedure below:

	  $ alloc $1$mua0:
	  $ request/reply "Mount FPaint tape on drive 0"
	  $ mount/for/den=1600 $1$mua0: FPaint Tape
	  $ backup/rewind/interchange tape:fpaint.bak-
	    /select=[skunk_works.fpaint...] [...]
	  $ dismount tape
	  $ dealloc $1$mua0:


	At this point, the FPaint files have been restored from tape into
	some directory, say Dua0:[FPaint_System].


	If, for some reason, the FPaint system need be rebuilt from the
	sources, type @Build_VAX_Fpaint_System.


	Assuming the FPaint directory name is Dua0:[FPaint_System], the
	following symbols and logicals need be defined for each user
	accessing Fpaint ( possibly through system or group tables,
	otherwise in each login.com ).

	   Define Fpaint_Directory Dua0:[Fpaint_System.MakScr.VAX],-
	    Dua0:[Fpaint_System.BldScr.VAX],-
	    Dua0:[Fpaint_System.Library.VAX]
	    Dua0:[Fpaint_System.Doc]
	   Fpaint :== @Fpaint_Directory:_Fpaint.com
	   BldScr :== run Fpaint_Directory:BldScr.exe


	To execute Fpaint, the following command is typed:

	   Fpaint <filename>[/nosource].

	   e.g. Fpaint Screen

	        Fpaint Scr1/nos


	To execute BldScr independently of the FPaint command file,
        the following is typed:

	   BldScr

	The user will be prompted for the screen file name.


	The application must be linked with Fpaint_Directory:FPaint.olb/lib
	or Fpaint_Directory:SMG_FPaint.olb/lib.


	Programmer documentation is located in [.doc].

 	    FP_Editor.doc - Using the screen editor and subprogram generator.

	    Screen.doc - Accessing the screen packages from an application.

	    Lib.doc - Description of useful routines in Fpaint.olb.

	    VXYY_Release.notes - FPaint changes since version X.YY.
