-=> /* Quoting Kurt Eichenberger to All */ <=-
 KE> We recently upgraded from warp3 connect to Warp 4. Our
 KE> office is set up with the peer to peer networking
 KE> available with Warp. IN the past we have shared drives
 KE> across the lan, and any newly created subdirectories
 KE> would also be shared and permissions set as per the
 KE> drive. With Warp 4, newly created subdirectories on a
 KE> shared drive are visible, but the files they contain
 KE> are not, unless the whole drive share is deleted and
 KE> recreated. Is this normal? anyway to set it up so that
 KE> new subdirectories are automatically shared? Kurt
I think I know what caused the problem you have.  Warp 3
Connect and Warp 4 have a different interfaces for creating
shares.  It has the same functionality but is a bit
confusing in Warp 4.
In Warp 4, after you create a share of the root drive (i.e.
"C:\") you can then "apply the ACL to all subdir's" (or
similar).  DON'T DO THAT.  At that point just hit CANCEL
and then finish up.  If you apply the ACL's (access control
list or something like that) to ALL dir's and files, ONLY
those are visible and every time you make more you'd have
to reapply the ACL's.  If you just stop at the root (C:\)
every new dir and file that is created continues to be
visible from the peer machine, no problem.  It's working
just fine here and this is the way I did it.
I'd suggest removing your existing shares and recreating
them but hitting CANCEL after the root is shared and not
continuing to apply the ACL's any deeper.
-Frank
(fsexton@xpert.net - http://www.concentric.net/~fsexton)
--- Blue Wave/DOS v2.30
---------------