special folders

[Peter T. Evensen]

I don't think even 1 is true.  It is possible for administrators to lock 
even that folder.

If they can download a file to a particular folder, that would indicate 
it is writable.  I assume that the autoloader would need to stick 
around.   There are software packages that lock everything down and roll 
things back to a starting state when a user logs out (with the option of 
preserving some folders/files).

Mark E. Powell wrote:
> Two follow-ups...
>
> -1-  Is it then an absolute that specialFolderPath(26) is writeable on Windows, regardless of personal vs. corporate configuration?  Even if the user has 'hide system folders' on?
>
> -2-  Does the ability to download a file to a particular folder not also mean that that folder is writeable?  For example, in the two-part autoloader architecture, if the user places the loader is put into folder x, is it not guaranteed that I can write the operational stack to that same folder?
>
> Mark
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>