Limitations
Doesn't Show Free Disk Space
Some operating systems can answer a drive's free disk space,
but the current stable Java version doesn't provide
a cross-platform interface for this task.
And so, getting the free space requires optional
platform-specific code, which I cannot easily maintain.
This feature is available in Java 6
and will be added to a future JDiskReport version.
Doesn't Show the Last Access Date
The Java file API provides the time of the
last modification, not the last access date.
Since I want to maintain JDiskReport as
pure-Java application, the tool cannot provide
the date of the last access.
Maximum Number of Files
JDiskReport has very relaxed upper bounds for the
number of files and the total file size.
Anyway, the number of files you can scan is limited
by the maximum memory the Java environment can allocate.
Many Java environments limit the maximum memory to 64MB by default.
If you scan many files you should increase this upper bound.
For example, to set the maximum memory to 128MB
in the recent Sun Java environments invoke:
java -Xmx128M -jar jdiskreport.jar
See the documentation of you Java runtime environment for details.
Doesn't Detect all Kinds of Links
JDiskReport does neither detect file system hard links
nor NTFS 5.0 junction points, as used in Windows 2000/XP.
Also, it cannot determine the correct size of soft links.
This can lead to incorrect size data and size statistics
when links are involved.
Poor Print Layout
The table layout is poor and page breaks too.
Printing Disabled for Deep Statistics
Printing is disabled for nodes deeper than 3 leves from the
scanned directory. This is an unnecessary limitation for
the size statistics that is available for all levels.