PK> If you use the connecting and sharing folder to control this, then you
 PK> may have noticed in the help that it advises to create a DRIVE share for
 PK> every drive that contains a DIRECTORY share you also wish to create. The
 PK> key here is that if you wish to allow access to an ENTIRE DRIVE, then
 PK> there are in fact 2 ways to do this, with slightly different but subtle
 PK> methodologies.
I've been playing with the two, and can't force any observable difference in
initial access to new directories. What I can't remember is how Warp handles 
the equivalent of Netware's inherited rights mask. That is, if you have 
particular rights to a directory, is there some control over what gets 
inherited when creating a subdirectory, or do you start with no new rights, 
or do you start with the same rights you have in the parent, or do you start 
with full rights? I could swear Warp Server is more stringent than Warp Peer.
Jeff
--- GoldED/2 2.42.G0615
---------------