Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!sdcsvax!ucsdhub!sdsu!lindwall
From: lindwall@sdsu.UUCP (John Lindwall)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Virtual Memory
Summary: bazooka gum
Message-ID: <3818@sdsu.UUCP>
Date: 25 May 89 23:08:28 GMT
References: <8905222150.AA05890@jade.berkeley.edu> <6959@cbmvax.UUCP> <16173@louie.udel.EDU>
Organization: San Diego State University, Math/Sciences Dept.
Lines: 18

In article <16173@louie.udel.EDU>, new@udel.EDU (Darren New) writes:
> What about applications that use AvailMem to keep from allocating
> so much ram that requesters fail (is there a better way, BTW?)?
> What about programs like DPIII which could use VM for the images, but
> would really like to read-ahead the images during playback? 
> What about a program running when your swap-disk has been ejected?

And what about applications that use the ol' flush libs trick?  You know,
you attempt to AllocMem multi-megabytes of ram just before terminating so
that any unused Libs and other resources get flushed.  You expect the
AllocMem to fail but by flushing all unused resources, the user will not be
tricked into thinking the application ate the ram.  With a VM system, the
AllocMem will succeed!

Oh well, I guess that won't be so bad.

John Lindwall
johnl@tw-rnd.SanDiego.NCR.COM