Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!jesup
From: jesup@steinmetz.steinmetz.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: Does RAM: ever retry?
Message-ID: <7069@steinmetz.steinmetz.UUCP>
Date: Mon, 24-Aug-87 03:24:03 EDT
Article-I.D.: steinmet.7069
Posted: Mon Aug 24 03:24:03 1987
Date-Received: Tue, 25-Aug-87 01:25:54 EDT
References: <510@sugar.UUCP> <6619@eddie.MIT.EDU> <535@sugar.UUCP>
Reply-To: jesup@kbsvax.steinmetz.UUCP (Randell Jesup)
Organization: General Electric CRD, Schenectady, NY
Lines: 26
Keywords: RAM: out of memory RETRY CANCEL AllocMem

In article <535@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>In article <6619@eddie.MIT.EDU>, gary@eddie.MIT.EDU (Gary Samad) writes:
>> "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. 
...
>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

The 1.2 Ramdisk has a 'ripcord' of 30K of ram.  If it finds it can't get
enough memory, it releases it's 'ripcord' and puts up the disk full
requestor.   It won't agree to be un-full until it can get a ripcord
back.  This was to solve problems of copying too much to the ram disk
and having the system crash.  Without the 30K, it's hard to let the user
know the ramdisk is full and let the user correct the problem.

	Randell Jesup
	jesup@steinmetz.uucp
	jesup@ge-crd.arpa