Notes to using basic under pro POS operating system
         
        The following information has been furnished by H. Stephen Spacil on
        installing MRH BASIC on a PRO. Thanks H. !!
         
        Installation was done on a PRO-380 under P/OS v3.0 plus the Pro Tool
        Kit v3.0.
         
        (All  POS command files  have been  combined in the file POSALL.CMD)
         
        Comment out the reference to SPAWNB in IMPUR.MAC. (There is some un-
        known difference  between IAS/RSX  spawn and P/OS spawn, and it does
        not yet work.)
         
        Edit  BASPRE.MAC  to  only  define the following conditionals:

	RSX11M	(Generate RSX11m version)
	SNGUSR	(Generate Single user version)
        M11EXT	(RSX11m supports task extend if running out of room)
	DEFVAR	(Automatically create undefined variables)
	FULTXT	(Create full text error messages for 11m/Pos)
         
        Compile the MACRO sources using POSASM.CMD.
         
        Link the objects using BASPOS.CMD. If necessary,  BASPOS.CMD may be
        edited to change task name or increasing the size of  the file  I/O
        buffer, (which now defaults to a maximum of 133 bytes/record.)
         
        Copy BASPOS.TSK to the tool kit directory, "APPL$DIR:"
         
        Install BASPOS using the command:
         
        	INSTALL/NOREMOVE APPL$DIR:BASPOS
         
        To avoid problems with just running BASPRO, and to enable passing a
        command line to it, one can use BASIC.CMD, which should be moved to
        LB:[1,2].  The 'P1'  parameter will be passed to BASPRO on startup.
        Note  that  no spaces  may be in the parameter,  so "@BASIC ?4*3+2"
        will give you the answer of "14" but "@BASIC ? 4*3+2" will not.
         
        Also  note that if BASPOS is not installed, the last line of BASIC.
        CMD must be changed to
         
        	RUN/COMMAND:"BASPOS 'P1'" APPL$DIR:BASPOS
         
        This will also be slower, due to the time involved in installing the
        task.

	Finally not that if one wants to just have a version  that is  acti-
	vated by a RUN command,  (and  does  not  try to get a command line,
	one  can define the variable PRO to disable the attempt to obtain an
	initial command line from the system.