Xref: utzoo comp.sys.amiga:47356 comp.sys.amiga.tech:9286
Path: utzoo!attcan!uunet!aplcen!samsung!zaphod.mps.ohio-state.edu!think!snorkelwacker!apple!agate!saturn!helios!terry
From: terry@helios.ucsc.edu (Terry Ricketts)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Buggy Software Fix-It Kit
Summary: try FACC II
Keywords: none
Message-ID: <10296@saturn.ucsc.edu>
Date: 12 Jan 90 17:03:24 GMT
References: <5289@blake.acs.washington.edu> <15486@well.UUCP>
Sender: usenet@saturn.ucsc.edu
Reply-To: terry@helios.ucsc.edu (Terry Ricketts)
Organization: UCO/Lick Observatory, Santa Cruz
Lines: 9


	The problem of memory running low is a problem that plagues all
Amigas. A friend is running a BBS and the software seems to eat a little bit
of memory every time a user calls in. He has to watch it constantly & when
memory starts to get low eithor run 'sweep' or reboot.
	I seem to remember that when I used Facc II (I now use BlitzDisk) there
was a built in facility to check for low memory and warn the user when it
happened. It used a library entry that was called asdglomem.lib if I remember
correctly. I'm sure Perry K. can tell the full story on it.