Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!agate!web-1a.berkeley.edu!c60c-1ea
From: c60c-1ea@web-1a.berkeley.edu (Yen Yuanchi Hsieh)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Disk Questions for WorkBench replacement project
Message-ID: <21279@agate.BERKELEY.EDU>
Date: 7 Mar 89 23:10:03 GMT
References: <21173@agate.BERKELEY.EDU> <821@microsoft.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 32


In article <821@microsoft.UUCP> you write:
:>c60c-1ea@web-4g.berkeley.edu (David Navas) wrote:
:>> 1)  How does one go about locking the correct disk if two or more
:>> have the same number.

:>I'd suppose it would just keep a lock on the drive.  It's been so long,
:>I forget what WB's bahaviour is in this area.

   Fortunately, I've fixed (hopefully) that problem by doing some real nasty,
   stuff with the DeviceList.  I just pull the correct volume-node to the top
   and then do my regular Lock call.  I don't even want to think what will happen
   with 1.4 ....
:>> 2)  in order to call format or diskcopy correctly, is any special
:>> information passed on to these programs?

:>I think Workbench just Execute()s them.  Note that this is not what happens
:>when you double-click (argc == 0 and all that).
:>-- 
:>	-Colin (uunet!microsoft!w-colinp)

   Actually, Workbench does pass a very funny pointer in place of the Name ptr
in the second (of two) arguments for format.  (IE, it does NOT merely Execute()
it).  The other Name is something like "sys:system/format", and the locks
are NULL, and lock to disk to be formatted (NULL if disk is bad).  Here's the
thing folks, this variable is NOT device dependent, or disk dependent.  The pointer
usually only changes when a DISKINSERTED message is sent, although the information
which is referenced by this mystery pointer has a tendency to do very unstable
things.  What IS this thing?  It's driving me up a wall..


David Navas c60c-1ea@WEB.Berkeley.Edy