Anyway, if you ask HFS to save cfg in a file, it won't delete registry.
So you can have safely user-based settings keeping them in files.
You just have to change the "working folder", HFS will read hfs.ini from there.
Agreed.
The tooltip already shows me the path (second line), just no way to edit it...
you'll find it in beta19
Excellent! I'll test it ASAP...
The lock should appear next to all entries permissions apply to.
i already thought about it and think it would be a mess.
you can't have all information, always, at the same time.
i made a change in the tooltip to get this information.
Tooltip is OK. You can't have everything. But it's open source, I should learn Delphi... B)
Is it possible to add an option to disable inheritation of permissions for some entries?
if it is unprotected, why keep it in a protected folder?
put it elsewhere and hide it
you can have 2 links to the same file, one in the folder and visible, one out of the folder and hidden
Hmm, yes but if you protect the root, there is no 'elsewhere' :?
Why not allow the admin to 'declare' another root (user-based)? That way every user could have its own 'home directory'!
e.g. you create a VFS folder 'UserA' and declare it as root for user A... Endless possibilities...:roll:
(now I know but other's may not)
the "recursion" on a protected structure is the classic behaviour.
it is what you get if you protect a folder on your disk. (...)
Right, every folder in NT inherits rights to subfolders and files. For every subfolder/file, I can disable inheritation and set different rights. Maybe in 3.0... :roll:
(...)but i decided to make a try, and found ..... it is better to not trust M$
I trust only open source completely 8O
But icons I don't use should be thrown out after some time or else the VFS would get bigger every time I add and remove files (I do this very frequently).
this wasting concerns only RAM. did someone noticed HFS wasting too much memory for icons? like 1MB...
I added my WINNT folder to the VFS (real) and opened it in my browser. HFS memory consumption jumped from 4012KB to 7432KB. More than 3 MB... After some time HFS should release the memory if nobody browsed that folder again...
my reply delayed a lot because your message was very long
Yes, we should keep posts shorter... :#)
MarkV
Show Posts
It could become a problem if you serve very large real folders and HFS stays up a very long lime. Damn Windows, I hate memory leaks... Anyway, please leave this code in the program, maybe someone gets better results (maybe Windows needs some time to release memory)
+ $0