Maybe hardlink support can be implemented as an option/checkbox and be disabled by default. Advanced users who are willing to sacrifice some of the “snappy behaviour” and low memory footprint can enable it if required (you might add the notion “experimental” or “slow” or something like that), and Joe Sixpack isn’t bothered with unneeded functionality.

Well, the interesting fact is that you would rather gain snappy behavior by “caching” stuff (i.e. more use of RAM, less use of CPU).

However, in fact some information is just “more expensive” in terms of CPU, IO and RAM. In case of MFT parsing, the hard links don’t add any such problems. But MFT parsing introduces other issues (the MFT is more or less a plain list, not a hierarchy like the directories are on disk … thus all contents need to be put into the right form before being able to evaluate it).

My biggest concerns with MFT parsing are about potential security issues (unprivileged user unable to use it or so) and the extended use of memory. But the advantages outweigh all of that so far.

For now, good night (2:08am here)

Maybe hardlink support can be implemented as an option/checkbox and be disabled by default. Advanced users who are willing to sacrifice some of the “snappy behaviour” and low memory footprint can enable it if required (you might add the notion “experimental” or “slow” or something like that), and Joe Sixpack isn’t bothered with unneeded functionality.

Keep up the good work!

The only method I see is MFT parsing and, as mentioned elsewhere, I am working on that.

// Oliver

in windows vista and windows 7, the winsxs directory is almost entirely made of hardlinks.

scanning such a system partition with windirstat yields totally false reports.

I do have a wish list.

1. I would like some way to export file structure to Visual Understanding Environment (VUE) an Open Source project located here http://vue.tufts.edu/index.cfm

2. Also you might find this project interesting if you ever thought to go the 3d route. http://www.tibsoft.com/index.php?page=steptree
StepTree v1.8. I like this approach but I think you could take it to the next level as your software is by far the best. I believe the future of file management will end up as a kind of mind map structure with a zoomable interface or ZUI.

3. If you are implementing a way to save search’s a favorites menu would be nice for organizing those search’s.

Thanks again
David Prouty

Someone needing this assistance would be able to run and save the scan, but wouldn’t know which files were safe to remove. If they could get those files to me, I could drill through them and compile a list of files to remove, then remove them in one shot, and then possibly re-run the scan overnight if necessary. If my only option were to run the utility, wait on-site perhaps a long time for it to come up, then delete files on that system itself, it would be much more difficult to use the utility.

Thanks for making it available (and easily portable). It’s on my shortlist of maintenance utilities in my flash-drive toolkit.

some features I wish for are:

Save scans
Save the bitmaps
Some way to report on file properties like: a report of files last accessed before June, 17 2002.
or reporting on file ownership to learn how much data is owned by user X on a volume.