Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!sdcsvax!ucbvax!UCONNVM.BITNET!STEIN
From: STEIN@UCONNVM.BITNET
Newsgroups: comp.sys.apple
Subject: Re:  Finder, Ramdisk
Message-ID: <8710200816.aa07332@SMOKE.BRL.ARPA>
Date: Tue, 20-Oct-87 08:45:00 EDT
Article-I.D.: SMOKE.8710200816.aa07332
Posted: Tue Oct 20 08:45:00 1987
Date-Received: Wed, 21-Oct-87 20:45:50 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20

>Dickson@Hartford repeated the problem many, including myself, have had with
>the new Finder not copying properly and added a new one, the Finder didn't
>recognize his ramdisk the first time he used it.

  I was told to forget about dynamic memory allocation under the finder and
set min and max ramdisk sizes equal if I'm going to copy files using Finder.
That's solved my copying problems, but I'm not thrilled with it.  I hope Apple
corrects the bug in its next update of Finder.

  If the ramdisk has the same name as a volume in a disk drive, Finder will not
locate it when booted (it will only allow one volume with a given name on the
desktop at once) and there seems to be no way to get it recognized later
without rebooting Finder.  I've also found that if I've accidentally shut off
my machine with the ramdisk as a boot drive, Finder won't locate the ramdisk
the next time I turn on my machine.  (Sequence:  turn on machine, machine
doesn't boot because the ramdrive is empty, go back to the control panel and
set boot drive to SCAN, reboot, ramdisk isn't found, turn off machine, turn
back on, ramdisk reappears.)
't
t