Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!web-2a.berkeley.edu!c60c-1ea
From: c60c-1ea@web-2a.berkeley.edu (Yen Yuanchi Hsieh)
Newsgroups: comp.sys.amiga.tech
Subject: Re: InfoData->id_VolumeNode->ln_Name ??
Message-ID: <24171@agate.BERKELEY.EDU>
Date: 8 May 89 22:09:21 GMT
References: <0285.AA0285@recondo>
Sender: usenet@agate.BERKELEY.EDU
Distribution: usa
Organization: University of California, Berkeley
Lines: 24

In article <0285.AA0285@recondo> sirius@recondo.UUCP (Michael Stilson) writes:
>Subject: Re: InfoData->id_VolumeNode->ln_Name ??
					^
  As far as I know, id_VolumeNode points (via BCPL conventions) to a
DeviceNode structure, not an exec Node structure.  You're undoubtedly going
to the wrong place with your dereferencing.  I'm suprised you never Guru'd
with 000...003.xxx...xxx  ...  :-)

>While working on a little utility, I wanted to include the volume name.  So...
>I looked through the structures, and found what I __THOUGHT__ I was looking
>for.

Okay, see above...
Look up structure of DeviceNode in dos.h, or dosextens.h, or something like
that.

>... or am I missing something really obvious here?

  Yes.

-------------------------------------------------
David Navas   c60c-1ea@WEB.Berkeley.Edu
Ideas?  What ideas?  If I had any idea I'd have
an idea, I wouldn't have posted this nonsense.