Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!portal!cup.portal.com!Azog-Thoth
From: Azog-Thoth@cup.portal.com (William Thomas Daugustine)
Newsgroups: comp.sys.dec.micro
Subject: Re: P/OS task image
Message-ID: <37894@cup.portal.com>
Date: 11 Jan 91 23:31:44 GMT
References: <D7CEC1CBB55F20419A@MSUS1.MSUS.EDU>
Distribution: usa
Organization: The Portal System (TM)
Lines: 28


Many thanx to the people who replied to my question about running
RSX tasks under P/OS. And my apology for replying publicly to the
net (our mail router isnt functioning properly; I can recive mail,
but cannot reply)

Anyways. The command PIP FOO.BAR/CO/NV=FOO.BAR works just fine. 
I assume that the /CO stands for CONTIGIOUS, waht does the /NV
stand for? (btw: I accomplished this using the DCL command 
COPY/CONTIG, which I assume spawn PIP with the above parameters)

Now comes the fun part:-) Trying to build up a software base. 
An unfortunate observation. It seems that quite a bit of 
tasks need a resident image installed in memory to run, and some
look for other task files. When P/OS aborts, it doesnt specify
_which_ file it is looking for. For instance, a version of ADVENTURE
aborted with some mumbo jumbo, and reported a directory spec: [001001],
which I would assume is looking for some kind of message data base.
(dont bother trying to make sense out of this psycobabble:-) I am 
just making an observation)

Does anyone have the DECUS P/OS sig stuff? Theres quite a bit of stuff
for the P/OS listed in the Pro 350 section. But unfortunatly, I cannot
justify spending over $200 for this software

Billy D'Augustine
billy@westmark.com
^^^^^^^^^^^^^^^^^^