README.md
Also in this account: for P/OS v1.7 with the on-pro tool kit (v1)
-----------------------------------------------------------------------
MAKPRORNO.CMD this command file plus the .Mac files in
[307,50] on this tape are all that you need
to build the working group's runoff on a PRO350.
You probably also want the .doc (or the .rno)
file, which is the user manual for it.
I have just built Runoff this way on a Pro, although I have only used it
a few times, it works fine and I am really happy to have it.
-----------------------------------------------------------------------
Some comments on the ease of moving RSX programs to the Pro running
the on-pro tool kit (v1) under P/OS v1.7
-----------------------------------------------------------------------
I also transferred the task image for Adventure from this tape in
[356,51] along with Files.dir and the files it lists. Lo and behold
when you put it all in [200200] (deleting uic mentions in files.dir)
it runs perfectly (although there is a noticable pause before it gets
going) on the PRO under the on-pro tool kit. Putting it in [200,200]
has something to do with default directories - see R.D Kirkman's
article in the DEC professional, Sept 83) task images from RSX only
seem to work when in 200,200 and run from that account (you can use
a command file to do that though)
Since many utilities on the pro tool kit still understand RSXese
when you invoke them with a command file (TKB @ for example) or use
RUN $ (run $pip is the one I use the most), bringing other items from
this tape (and past tapes) onto the Pro should be equally easy. (Note,
that some utilities require reuse of their name in the /command=
e.g. RUN $LBR/COMMAND="LBR RNO/CR:100.:576.:64.=RNO.OBS"
from MAKPRORNO.CMD is the way to get LBR to work).