Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!aurora!ames!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Does RAM: ever retry?
Message-ID: <535@sugar.UUCP>
Date: Sat, 22-Aug-87 17:42:21 EDT
Article-I.D.: sugar.535
Posted: Sat Aug 22 17:42:21 1987
Date-Received: Mon, 24-Aug-87 03:45:09 EDT
References: <510@sugar.UUCP> <6619@eddie.MIT.EDU>
Organization: Sugar Land UNIX - Houston, TX
Lines: 22
Keywords: RAM: out of memory RETRY CANCEL AllocMem
Summary: I AM freeing up contiguous space...

In article <6619@eddie.MIT.EDU>, gary@eddie.MIT.EDU (Gary Samad) writes:
> In article <510@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> }seems to help. I can see large chunks of contiguous space showing up on my
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Try unloading one big program rather than a lot of little programs.  Then
> "RETRY" will work.  It appears to require a 30K contiguous chunk to continue
                                              ^^^^^^^^^^^^^^^^^^^^
> correctly.  I've actually had over 100K available and gotten that RAM: 
> requester.  By deleting something like ln (the Manx linker) or sometimes
> emacs I can get it to continue.

30 K at a time? That's gross and disgusting. Is there anything that allocates
smaller memory chunks without requiring a lot of RAM? I've tried VD0:, but it's
too big: takes so much off the top that I don't have enough room left for
Manx. It shouldn't be impossible. I can load NewClock and Gauge both and still
have enough RAM: to work in.

Also, I'm sure I'm freeing up more than 30K at a time. I can watch RAM:
allocate memory as it requires, and it's allocating chunks way smaller
than the ones I'm freeing. Something odd is happening here.
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter (I said, NO PHOTOS!)