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

Thanks Bob, I should have realized using ->dl_Task message passing was a good
idea, as I have to use this method to get a correct DiskType reading on the
devices.  For those locking disks using this method -- remember, don't
include a lock or a name as the (first and second?) arguments,
leave them NULL.

And if ->dl_Task == NULL and ->dl_LockList != NULL, do a 
DupLock(->dl_LockList).  Hope this helps somebody.

For format (haven't gotten to DiskCopy), pass the device name as the name
argument.  This definitely is what is there for bad disks.  For good disks --
I don't know WHAT to pass.  But the lock on that disk seems sufficient.

Any comments on that?   :-)

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