Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site wanginst.UUCP
Path: utzoo!linus!wanginst!vishniac
From: vishniac@wanginst.UUCP (Ephraim Vishniac)
Newsgroups: net.micro.mac
Subject: RamDisk technical query
Message-ID: <622@wanginst.UUCP>
Date: Fri, 24-May-85 12:32:30 EDT
Article-I.D.: wanginst.622
Posted: Fri May 24 12:32:30 1985
Date-Received: Sat, 25-May-85 06:27:45 EDT
Distribution: net
Organization: Wang Institute, Tyngsboro, Ma.  01879
Lines: 23

I'm trying to understand what makes a Mac ramdisk "eject-proof."
I had originally been told that ramdisks that the finder thought were
on Appletalk (aka Applebus) would not be ejected.  Comparing the 
Assimilation process ramdisk to the Aztec C ramdisk, however, I see that
the finder believes both to be on AppleTalk.  The Assimilation ramdisk will
not be ejected; the Aztec one will.  I'm also told that the finder ignores
close errors from disk drivers; i.e., a driver cannot simply refuse to eject
a disk.  Is this really the case?

I've examined the drive queue and the volume control block queue in some
detail and been unable to find any useful difference between these two
ramdisks.  I've also examined the ramdisk drivers somewhat; I have
to rely on disassembly to look at the Assimilation driver, of course.

The purpose of this exercise to make sure that a ramdisk driver I'm 
writing for a Mac with megabyte memory will be difficult to dispose of
accidentally.  Can anyone shed some light, or point me to an especially
enlightening passage in Inside Mac (loose-leaf edition)?

-- 
Ephraim Vishniac
  [apollo, bbncca, cadmus, decvax, harvard, linus, masscomp]!wanginst!vishniac
  vishniac%Wang-Inst@Csnet-Relay