I mainly use WinDirStat for mapping capabilities. It’s a great overall strategic mapping and planning tool for use when nuking excessive stuff. I also use it to get an overview of how to re-allocate and re-purpose drives.
Cool. That’s the kind of feedback I’d like to have much more. We get the occasional grateful mails or very specific feature requests that do not always make sense to a broad set of people, but this feedback about usage makes it easier to see what to focus on.

I would never use (and properly so) any converter capability, especially ones that convert to a lossy format. Please do not go bloating this program with such items.
Optipng is an external program. The point would not be to incorporate its code into WDS – that’d be silly. Rather a more powerful scripting facility than is currently built in, would allow more versatile use, including customization of some aspects of the program for uses that you or I cannot even think of right now.

Conversion stuff is best left to existing applications that specialize in such operations. There’s a reason why there’s lossless and lossy filetypes – and going back and forth among them is to be done carefully, especially if you work with media files of any sort. And to automate any of this stuff is just asking for disaster.
Not with optipng, though.

I also would never use any cleanup routines or scripts or anything. This activity, like file conversion, is best left to other programs that specialize in such operations. CCleaner is what I use, it’s established, it works, it’s highly customizable without learning a script language, and it’s in use on over 500million PC’s world-wide. So for cleanup ops I’d highly recommend that one. You could call CCleaner right from WinDirStat and run it in a silent command-line mode. Think of it as one big extension module. Now you get the best cleaning from the best mapping program! Amazing! eh?
Well, CCleaner has a different license etc. Also it doesn’t really do the per-file thing but rather has particular locations it checks and cleans. WDS doesn’t have this idea of the system. For WDS it’s all files and folders.

A duplicate search function would be a natural extension of what most folks use WinDirStat for anyways.
In a sense it would be, but again the actual implementation details should be flexible (i.e. scripted).

It would be a great thing to have duplicates flash on the treemap.
Eeek … alright, you have a point, but perhaps that should be something you have to activate willingly and then deactivate again when you want to …

While there are plenty of duplicate search & destroy programs out there already – I feel that WinDirStat could get some added value here.
Well, I was involved in one of them (DFHL), but they all have their caveats. I’ll rather let the user decide (thus the scripting).

And speaking of flashing stuff, what about when clicking on a file – have the outline box flash on the treemap? This would make it immensely easier to find those microscopic files in a sea of monsters.
Nice idea. Could you please add this to the feature request tracker on SF.net, so I won’t forget it?

Well, that’s about all I gotta say, just, please don’t go bloating this program up with non-related features. I understand your desire to branch out (no pun intended) the program’s functionality, but some things are perfect the way they are, and this is one of them.
You misapprehend the question in my original post. This is not at all about bloating the core program but rather making it versatile so that users are empowered to implement things themselves that I didn’t anticipate when I was working on it. I think this is what makes great programs – extensibility.

Secondly, it’s more important whether we could simply abandon the current cleanup actions in favor of a more powerful option. And strictly speaking that more powerful option doesn’t have to be used for “writing” at all, it would just allow more control. And though you have a point with “bloat” in a sense, I think it’s still fine to add features that make the tool more versatile, just not to the core program.

I would never use (and properly so) any converter capability, especially ones that convert to a lossy format. Please do not go bloating this program with such items. Conversion stuff is best left to existing applications that specialize in such operations. There’s a reason why there’s lossless and lossy filetypes – and going back and forth among them is to be done carefully, especially if you work with media files of any sort. And to automate any of this stuff is just asking for disaster.

I also would never use any cleanup routines or scripts or anything. This activity, like file conversion, is best left to other programs that specialize in such operations. CCleaner is what I use, it’s established, it works, it’s highly customizable without learning a script language, and it’s in use on over 500million PC’s world-wide. So for cleanup ops I’d highly recommend that one. You could call CCleaner right from WinDirStat and run it in a silent command-line mode. Think of it as one big extension module. Now you get the best cleaning from the best mapping program! Amazing! eh?

A duplicate search function would be a natural extension of what most folks use WinDirStat for anyways. It would be a great thing to have duplicates flash on the treemap. While there are plenty of duplicate search & destroy programs out there already – I feel that WinDirStat could get some added value here.

And speaking of flashing stuff, what about when clicking on a file – have the outline box flash on the treemap? This would make it immensely easier to find those microscopic files in a sea of monsters.

Well, that’s about all I gotta say, just, please don’t go bloating this program up with non-related features. I understand your desire to branch out (no pun intended) the program’s functionality, but some things are perfect the way they are, and this is one of them.

I am running Win7 64 SP1

Does the software not like win7 ?

Thanks , still cool and useful never the less.

Download this : http://assarbad.net/stuff/localsystem.zip

Then I found these instructions:

Right click on your WinDirStat shortcut > Properties, on that page > Start in: Copy the info on that line.
Start the executable (as Administrator) named “CMDasSys.exe” after unpacking the archive ( localsystem.zip ) to some temporary location.
Enter this in the dos window:

cd ( space after cd ) paste & hit > Enter.
Now type windirstat.exe to that line & hit > Enter.
WinDirStat will now fire up. Run WinDirStat and you’ll see everything. Delete the crap.
When finished with Command Prompt, close it.

I got rid of 90 Gb of images and music from the previous XP install.

Cheers..