Path: utzoo!mnetor!uunet!unisoft!gethen!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.atari.st
Subject: Re: RTX, MT-C shell, TOS compatibility?
Message-ID: <129@bdt.UUCP>
Date: 7 Feb 88 21:03:34 GMT
References: <8802051700.AA01475@decwrl.dec.com>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 36

In article <8802051700.AA01475@decwrl.dec.com> goldstein@aim.dec.com (fred, k1io@FN42jk, +1 617 486 7388) writes:
> [much removed]
>So, will MTC-shell and/or Micro-RTX do the following?
>
>Run existing non-GEM programs, like MicroEmacs?
>	In the background?
RTX will indeed run non-GEM programs in the background.  This includes
commands like compilers, makes, arc, kermit, and most other *.TTP or
*.TOS programs.  Interactive programs like MicroEMACS are not very useful
in the background however.  But they can be used from an auxiliary terminal,
while something else is going on the the ST console.

>Run exisitng GEM programs, like Uniterm?
>	With others in the background?
>	Switch between GEM programs?
>	Switch between non-GEM and GEM programs?

RTX will run existing GEM programs. These must be run from the main console
screen (of course).  Only one GEM program may used at a time; RTX does
not re-implement the GEM calls, only the BIOS and GEMDOS calls.  Non-GEM
programs may be running concurrently with the one GEM program.  There is
also a way to switch between non-GEM programs and the GEM program, via
a Desk Accessory (which is also a way to "simulate" multiple GEM programs).

>What limitations are there?  Thankx.
>          fred

The main limitiations are memory and "ill-behaved" programs.  RTX is a
"in memory" system (i.e. it doesn't swap).  Also the ST has no hardware
memory management, and only the "low memory" protection.  When RTX runs
out of physical memory, no more processes can be started until one
finishes.  As for "ill-behaved" programs, we're mostly talking about
programs that forsake the OS calls for "speed" or some other reason.
If the application makes TOS calls, it will usually run.  If it hacks
hardware directly or otherwise bypasses the OS, then most likely will
not run.