Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!labrea!jade!ucbcad!zen!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Does RAM: ever retry?
Message-ID: <3665@zen.berkeley.edu>
Date: Thu, 10-Sep-87 06:16:51 EDT
Article-I.D.: zen.3665
Posted: Thu Sep 10 06:16:51 1987
Date-Received: Sat, 12-Sep-87 07:19:04 EDT
Sender: news@zen.berkeley.edu
Organization: Tubular Transport Devices, Ltd.
Lines: 37
Keywords: ram, out of memory, bugs

> [Long discussion about RAM: and out-of-memory]

I get around RAM:'s low memory handling by using VD0: instead. 
VD0: is great (yes... I paid, how about you?)
RAM: seems to have a problem or two with memory.  For an example, try this:


Bug Creation Procedure:  [ I thought bugs evolved? :-) ]

Kick with V1.2 Kickstart (33.180, release).
Work with Workbench 33.56 (Comes with the A500/A2000)
Open the Workbench disk.
Drag the Clock into the RAM disk.
Close the Workbench drawer.
Open the RAM disk.
Note how much memory you have free.
Select the Clock icon.
Select "Duplicate" from the menu.
Wait.
You get a "Volume RAM: is full" requester.  Huh??

Doing an "avail" from a CLI reveals that memory is indeed all full...
something ate all the free ram; on my A1000 that's about 1.5 Megabytes!!
Clicking cancel brings it all back.  Strange, eh?

Related bugs:

You can rename two files in RAM: to have the same name.
If the first copy into a RAM: runs out of memory, the block count
will be screwed.  Type "info" to crash your machine with a divide
by zero error.


|\ /|  . Ack! (NAK, EOT, SOH)
{O o} . 
 (")	bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce
  U