Jeff Dunlop wrote in a message to Mike Bilow:

 JD>> I would like to detect whether a device found by
 JD>> DosQueryFSInfo is read-only.

 MB> Call DosQueryPathInfo() against the root directory of the device.

 JD> Thank you for the detailed example, but this seems
 JD> incomplete. Wouldn't a Netware volume with root access
 JD> denied but RW access allowed for particular subdirectories
 JD> look the same?

I don't know.  NetWare has a somewhat oddball mechanism for handling such
things, the "inherited rights mask," that hardly anyone ever
uses.  In other words, NetWare is unusual in that it allows explicitly
controlling how things propagate downward, and which permissions are
inherited.  This simply does not translate well to most operating systems,
including OS/2.

I do not believe that OS/2 will see any directory as read-only, as distinct
from a file, unless the whole file system is read-only, as it is in CDFS. 
The reason for this is that applications cannot modify a directory directly
under OS/2, but must go through the file system driver.  Some operating
systems, wuch as VMS, will allow opening a directory as a file and reading
its contents as data, but this is unsupported under OS/2.

NetWare provides different permissions for directories than for files, and
the exact way in which the differences are interpreted in OS/2 is up to the
NWIFS.IFS remote file system driver.  For example, suppose that someone had
write permission for a file but not for the directory in which it resides;
this would be meaningless.  Or consider the case where someone had create
but not delete prvilege in a directory; there is no consistent way to
translate this into a single "read-only" bit.

My best advice is to test this and see what happens.
 
-- Mike


---