-=> /* Quoting Will Honea to Frank Sexton */ <=-
 
 WH> The biggest  change I found was that W4 creates the
 WH> blasted share with access NONE as the default!
Very True.  Good point.  Guess that could be the problem. I
AssUmed that the original poster had not selected the
default NONE because he WAS sharing the drive successfully.
The only thing wrong was that newly created directories
were not automatically shared.  It never occurred to me
what would happen if you left NONE selected but then DID
create an ACL list.  I'll bet you're right.
 WH> That said, you suggestion is probably the simplest
 WH> one: delete the  share and recreate it.  I don't think
 WH> the abort of the ACL creation is needed since without
 WH> an ACL entry - that's all kept in a file - you haven't
 WH> really defined the share.  I would emphasize, tho,
 WH> that you MUST set the access level since the default
 WH> access is NONE. That's about as useful as write-only
 WH> memory :}
Agreed.  I found it much faster to just cancel after the
root (and to change the default NONE to ACCESS, or
whatever).  For one thing, applying the ACL list took
forever on each drive :-).  Without it, they work fine
anyway.  As long as you don't leave it set to NONE for
sharing.
-Frank
(fsexton@xpert.net - http://www.concentric.net/~fsexton)
--- Blue Wave/DOS v2.30
---------------