P/OS task image

Thread View: comp.sys.dec.micro

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by "Bruce R. Mitchell / WNIMHACK%WS... Fri, 11 Jan 1991 00:27

#864

Author: "Bruce R. Mitchell / WNIMHACK%WS...
Date: Fri, 11 Jan 1991 00:27

25 lines
1479 bytes

 
 
Billy D'Augustine in a message of 9-Jan-91 inquires about the compatibility
of RSX task images and the P/OS operating system.
 
RSX-11M-Plus supports two variants of task headers; resident and nonresident.
Without going into unnecessary detail on the differences between the forms,
only nonresident header task images will run under P/OS.  M-Plus permits
overriding the header form with the INStall switch
 
/XHR=(yes, no)
 
but P/OS does not support this.  Therefore, any task image brought into a
P/OS system from an M-Plus system must have been built with the TKB /XH
switch to force external headers.
 
The usual symptom of this problem is that P/OS complains with an error message
of the form:
 
INS -- Task has a resident header 
 
Glenn Everhart very correctly also points out that Kermit does not create a
contiguous file, and that PIP /NV/CD/CO must be used to create a new,
contiguous task image from the received file.

Re: P/OS task image

#865

Author: William Thomas Daugustine
Date: Fri, 11 Jan 1991 23:31

28 lines
1703 bytes

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
^^^^^^^^^^^^^^^^^^

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads