HP3000-L Archives

January 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Mon, 8 Jan 2001 10:02:35 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
Dave writes:
> Is there a TSR-like feature in MPE?

It is possible to mark code or data as "resident" meaning it will remain in
memory permanently.  This is required for code that would execute in an
interrupt context for example, including all I/O drivers and much of the MPE
kernel.

There's no other "TSR" equivalent feature that I can think of, mostly
because there's really no place to put such a thing.

> Are there other aspects of MPE (other than being unsuitable for real-time
> programming) that would obviate the need for TSRs?

Nothing other than its being (generally) unsuitable for Real Time
programming :-)

IIRC, MPE was originally designed to support on-line, batch *and* real time
processing, but the real time stuff got dropped before the first real
customer version of the OS.

Generally if you really want MPE to do something there's probably a way to
get it to do it, though perhaps not in a way that's easily describable using
terms from other operating systems.

Mike writes:
> The feature you're looking for is the :ALLOCATE progname command.  However
> it only works on CM programs not on NM.  Use in conjunction with
> :DEALLOCATE and :SHOWALLOCATE.

The :ALLOCATE command permanently "loads" (resolves load-time external
references) a CM program but does *not* in any way reserve memory for it.

G.

ATOM RSS1 RSS2