Not quite sure where this goes - it is *probably* not bug (but who knows).
I'm using an external LaCie 2TB "triple extreme" drive to carry various amounts of data between various labs, office and home. The drive attaches via USB, FireWire and FireWire800 and is used in the various locations through different interfaces.
It is NTFS formatted.
The various machines that talk to it run Win2k, Server2k3, and XPpro. Data is written sometimes by some random local user, bu "Administrator" or by a domain user and it is sometimes written through the OS directly (drag'n'drop) and sometimes from cygwin running on various of the machines.
This creates a directory structure where any one node can be owned by any of a wild variety of user names and can have any one of a set of permissions attached to it - sometimes inherited, sometimes not.
Occasionally this leads to situations where a folder is shown as "0+ bytes" (or "xx+ bytes") indefinitely where somehow FolderSize cannot scan the folder (or a subfolder within it) even though I can double-click it and see all the contents and their sizes. That is to say: Foldersize seems to be running with lesser permissions than the user sitting in front of the computer.
The reason that this is problematic is because I cannot find any documentation (and I did read the FAQ) what permissions precisely I have to set to make Folder Size work. What user or group needs to have which permissions? I've been experimenting extensively and there does not seem to be a way to grant Folder Size access to a folder it cannot see. Even giving "Everyone" "Full Access" will not make Folder Size see a directory in question - but creating a new directory and moving the files from the old to the new makes Folder Size pick up on the size just fine.
I think what is needed is some kind of statement what exactly I have to do to run Folder Size as "myself", that is to give it (at least) as much ability to see stuff as I have as the user clicking things on the screen.
