Comments on: WinDirStat 1.3

By: Oliver

Oliver — Wed, 11 Jan 2012 10:27:09 +0000

I’m aware of that attribute, but a program that is handling files should probably be able to distinguish volume mount points, junction points and symbolic links. And IIRC only symbolic link targets don’t have to exist.

By: Doug

Doug — Sat, 07 Jan 2012 22:13:41 +0000

Can’t you just use the FILE_ATTRIBUTE_REPARSE_POINT 1024 (0×400) attribute from FindFirstFile to detect linked files? And if a file is a link, exclude its size from the total?

By: Phillip

Phillip — Fri, 16 Sep 2011 04:16:16 +0000

I was researching hardlinks and symbolic links as refresher for myself. I had found these on Microsoft's website.

By: Stephen

Stephen — Thu, 18 Aug 2011 10:16:45 +0000

Another useful feature would be a cumulative ‘Last Accessed’ field. This would help a decision to delete/migrate/backup a large directory none of whose files had been accessed for a considerable period.

By the way: thank you for an excellent program.

By: Stephen

Stephen — Thu, 18 Aug 2011 10:12:35 +0000

I agree that ‘perfect’ hardlink support is impossible, and ‘very good’ might be expensive. Here is a suggestion for a compromise that I think would be useful and not too expensive.

Currently you must have a cumulative size counter for each file/folder, as well as various other cumulative counters such as Items. Use instead two such size counters. One is exactly as now. The second accumulates [size/numberOfHardlinks]. There would be a toggle for displaying percentages and the treemap using the original size or the compensated size.

The new figure should be correct at the disk level. It would need to be interpreted with care when looking at subdirectories; but would still be useful.

By: Franck

Franck — Sat, 23 Jul 2011 10:45:04 +0000

Hi, Here a little windows registry script (copy/paste in a file named something.reg) to include windirstat in directory extension explorer of windows (I find this very useful to call windirstat, maybe, it can be included in the installer, because the installation path have to be set ):

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\shell\WinDirStat]

[HKEY_CLASSES_ROOT\Directory\shell\WinDirStat\command]
@="\"c:\\Program Files (x86)\\WinDirStat\\windirstat.exe\" \"%1\""

[HKEY_CLASSES_ROOT\Directory\shell\WinDirStat\DefaultIcon]
@="c:\\Program Files (x86)\\WinDirStat\\windirstat.exe,0"

By: Graeme

Graeme — Wed, 01 Jun 2011 15:12:23 +0000

Superb tool and thanks!

Would like to see the following features given the whole work/life/family/home balance!

1) Command-line support to allow easy scripting (previously mentioned)
2) More extensive user-defined reporting – somewhat like creating filters in SequoiaView (see 3)). Ability to take nightly snapshot bitmaps of the file system – could lead to animation of file system view?
3) File filtering/masking – only shows me multimedia files or documents. Ignored files get accumluated in an ignored bucket for display or treemap block.
4) Option to show Owner, Creator, Modified tipstrip on any file in the map view e.g. who dumped the 14GB file on the local server?
5) User-definable colours on the map.

Just some thoughts!

-Graeme

By: cavallogoloso

cavallogoloso — Wed, 16 Feb 2011 23:32:34 +0000

i mean simply: consider them: calculate the space “if they where real” (for example: one can calculate the space used by files “if i copy all these files out of this disk”) also with an item in the list of extensions dedicated to hardlinks >1 for each datablock

But i am considering that this feature could be useful for a very few people

By: Oliver

Oliver — Thu, 10 Feb 2011 00:52:07 +0000

@cavallogoloso: what do you mean? There is no ideal solution for hardlinks and no one has as of yet come up with a brilliant idea …

By: cavallogoloso

cavallogoloso — Thu, 10 Feb 2011 00:05:18 +0000

check about HARDLINKS management. Is it good now?