Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!ulysses!hector!eric
From: eric@hector.UUCP (Eric Lavitsky)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for Workbench 1.x
Message-ID: <10015@ulysses.homer.nj.att.com>
Date: 5 Feb 88 16:37:20 GMT
References: <8802050812.AA17320@jade.berkeley.edu>
Sender: netnews@ulysses.homer.nj.att.com
Reply-To: eric@hector (Eric Lavitsky)
Organization: AT&T Bell Labs, Murray Hill
Lines: 21

In article <8802050812.AA17320@jade.berkeley.edu> FATQW@USU.BITNET.UUCP writes:
>Another one!  How about creating some way for user programs to link into the
>system, so when an AllocMem() is about to fail,  it calls your program, and
>your program might just be able to free up the needed memory.  This is the
>same as the Library/Device principle.  For things that are "useful" but not
>"essential", or can be re-loaded, make it possible to have the system
>automatically free the needed memory.

The hooks were already there - Perry wrote a library that let's your application
do exactly what you describe - it's called the ASDG low-memory server, 
available on Fish Disk #85, or as a bonus when your purchase FaccII - and FaccII
takes advantage of the library of course :-)

>                Bryan Ford                    ////

Eric

ARPA:	eric@topaz.rutgers.edu		 "Lithium is no longer available
UUCP:	...{wherever!}ulysses!eric	  on credit..."
	...{wherever!}rutgers!topaz!eric		- from Buckaroo Banzai
SNAIL:	34 Maplehurst Ln, Piscataway, NJ 08854