Path: utzoo!attcan!uunet!super!udel!gatech!bloom-beacon!think!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Need help with ....
Message-ID: <67619@sun.uucp>
Date: 9 Sep 88 16:52:30 GMT
References: <298@lexicon.UUCP> <6234@batcomputer.tn.cornell.edu> <2241@cadovax.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 23

In article <2241@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes:
> I found that if you get to the DeviceList from a FileLock, it won't get 
> you DF0: DF1: VD0: RAM: etc., you get the logical names of the disk that 
> is in the drive, not the physical device names.  Haven't tried chasing it 
> from the RootNode though, I guess it could be different.  How do you weed
> out devices like SER: PAR: PIPE: etc?  Is it possible to determine the 
> *device* name (not the disk name) from the FileLock in any way?
>Keith Doyle

Well, you can avoid the "other" devices by first checking for a handler
task (disks always have them and devices only sometimes do) and if you 
find it (the handler) try sending it an ACTION_INFO to see if it thinks
it is a disk. The heuristics can get really complicated because the concept
of device "type" is not really embodied very well in the system. (Same thing
with serial type devices try enumerating them sometime :-)) Anyway, there
is a gross way of finding the device from a Volume node, look at the 
task pointer in the volume field an compare it with the various devices
that you found. I am not sure but I think that is how I did it with my 
"AmigaLife" file requester. I'll check tonight to see.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.