I am really having problems with warp 4 peer to peer and sharing 
drives/subdirectories. After we have shared a drive on the lan, we have 
discovered that newly created subdirectories on these drives are not 
accessible. (subdirectories are visible, but contents are not.) A helpful 
person in this conference previously suggested deleting the share and 
recreating it WITHOUT applying access permissions to the subdirectories. When 
I have tried to delete the share all proceeds just fine until The point at 
which the program attempts to delete the subdirectory access permissions. at 
that point I get a NET2222 error, it won't delete the access permissions, and 
I must suffer through this error message for every subdirectory on the drive 
befor I can exit. The only way we have been able to share a newly created 
subdirectory is to reshare the whole drive and reapply access permisions to 
all subdirectories. This is a big pain for everybody as all the drives must 
be remapped after we do this. Warp 3 connect did not have this problem. we 
create a lot of subdirectories as part of our regular work. As a final 
insult, I called IBM who informed me that I would have to pay them $190 befor 
they would talk to me about this. Is this a bug or a "feature"? 
--- Maximus/2 2.01wb
---------------