Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!shelby!polya!gilham
From: gilham@polya.Stanford.EDU (Fred Gilham)
Newsgroups: comp.sys.amiga
Subject: Re: Resident
Message-ID: <9738@polya.Stanford.EDU>
Date: 5 Jun 89 19:39:33 GMT
References: <16912@louie.udel.EDU>
Sender: Fred Gilham <gilham@polya.Stanford.EDU>
Reply-To: gilham@polya.Stanford.EDU (Fred Gilham)
Organization: Stanford University
Lines: 22

In article <16912@louie.udel.EDU> OHA101%URIACC.BITNET@mitvma.mit.edu (F. Michael Theilig) writes:
>
>      Could someone enlighten me to the advantages to
> resident?
>

The main advantage is that you execute the program "in place".  If you
use a ram disk, you copy the program into memory (from memory) then
execute it.  Thus while executing the program, you have two copies of
it in memory.  If the program is resident, there is never more than
one copy in memory.  You can perform the trick in 1) when multiple
instances of the program.  Imagine that you are "more"ing several
files at the same time.  You can be using a single copy of the code to
do all this, with each execution instance creating its own windows,
buffers etc.

In spite of this, I run most of the little programs from c: out of
rad: so they are there when I reboot.  I use `rez' for larger
programs, but note that `rez' does not ensure that you can run a
single program more than once (I think I tried it with `less' and it
screwed up).
-Fred Gilham