In an environment where all users are just that - not power users nor as
limited as guests - how can you provide an play pen where users of the same
PC can share information using the resources of just that PC? The issue is
that user A can read files created by user B but cannot update them or delete
them.

I have a simple minded application that wants to use some small files to
provide base functionality for when the server goes down. Call it poor man's
replication.

File system security for true users just does not seem to permit this.

An installation by a power user might solve the problem because then a
folder could be left hanging wide open. But in an xcopy install world (what a
promise that was:-( how can this be pulled off?

I misread the discussion of isolated storage and hoped that would provide a
way to have this capability. Unfortunately its just another way of hiding
stuff in the the user's document and settings directory. HINT HINT TO MS
Lurkers, putting this in all users with full permissions to dot net programs
with credentials independent of user to have full access to them would be
wonderful.

Presumably when framework 2.0 comes out I could mastre ACL's to do the job.
Problably going to have to find that C# code that's floading around to do it.

Suggestions please?
--
Regards,
Al Christoph
Senior Consultant and Proprietor
Three Bears Software, LLC

Hello!
You wrote on Tue, 30 Aug 2005 18:30:02 -0700:

AC> Presumably when framework 2.0 comes out I could mastre ACL's to do the
AC> job. Problably going to have to find that C# code that's floading
AC> around to do it.
AC> Suggestions please?

You can check SolFS ( http://www.eldos.com/solfs/ ). This is a virtual file
system that supports encryption and, alsough it's not integrated with
Windows NT Security model, you can easily implement user access rights with
it. And it can work in different limited environments since it stores the
storage file wherever you want.

With best regards,
Eugene Mayevski