09-27-1997,Frank Sexton wrote to Kurt Eichenberger:
FS> In Warp 4, after you create a share of the root drive (i.e.
FS> "C:\") you can then "apply the ACL to all subdir's" (or
FS> similar).  DON'T DO THAT.  At that point just hit CANCEL
FS> and then finish up.  If you apply the ACL's (access control
FS> list or something like that) to ALL dir's and files, ONLY
FS> those are visible and every time you make more you'd have
FS> to reapply the ACL's.  If you just stop at the root (C:\)
FS> every new dir and file that is created continues to be
FS> visible from the peer machine, no problem.  It's working
FS> just fine here and this is the way I did it.
Something doesn't jive, Frank.  I just went thru this exercise. 
Shared a drive (I:\), went thru the whole ACL routine.  New directories
are shared just fine with no mucking around.  The biggest change I
found was that W4 creates the blasted share with access NONE as the
default!  The documentation I've read indicates that a shared directory
(the root in this case) and all subordinate directories are shared. 
You CAN set privileges on subdirectories but a quick test on this I:
drive indicated that all subordinate directories inherited the same
access as the top-most directory defined for the share.  I haven't
tried re-defining the root to see if it over writes previous access
levels for subordinate directories but the docs I'v read indicate that
it will.  Gotta try that some time - that could get really sticky! 
HPFS386 will preserve previous access definitions, so who knows?
That said, you suggestion is probably the simplest one: delete the
share and recreate it.  I don't think the abort of the ACL creation is
needed since without an ACL entry - that's all kept in a file - you
haven't really defined the share.  I would emphasize, tho, that you
MUST set the access level since the default access is NONE.  That's
about as useful as write-only memory :}
Will Honea
whonea@codenet.net
--- Maximus/2 3.01
1:128/166)
---------------