DIRSIZE v1.0 : Directory Size Lister I. Introduction. DIRSIZE.EXE is a small, but useful, utility that lists the size of the given directory, all of it's subdirectories and gives a grand total for the path. In this way you can tell how big directory is and what it's subdirectories are. I have found this useful for cleaning up my hard disk or doing backups. II. Copyright. Since the world is as it is, I, Thomas Petrocelli, hereby claim copyright on this program, effective May 7, 1991. This program can be distributed freely, but no charge, other then the cost of media, may be exacted for it. I make no claims as to the usefulness or efficiency of this program. I do not guarantee that it is free of errors or bugs. I will not be responsible for any damage that occurs through use or misuse of this program. Use at your own risk. Distribution of this program does not imply any relationship regarding training or support. I am not obligated to fix bugs, or even inform anyone of them. Basically, you're on your own. I hate this legal stuff, but one has to watch one's back these days! III. Support. What? For this little thing? If there is a bug, let me know via the BIBMUG or Apollo III BBS's in Buffalo, New York. Maybe I'll fix it. IV. How It Works. To use DIRSIZE, type C:> dirsize on the DOS command line. This will then produce a listing of the total size of all files in the path given, plus it's subdirectories, plus a grand total for all of them. If no path is given, then the root path (\) will be assumed and all directories on the disk will be listed. If you wish to have output sent to a file or printer, just use the DOS redirection character >. For example : C:> dirsize \junk > testfile will list the sizes of the directory \junk and all subdirectories to the file testfile. If you used LPT1 or PRN instead, then the output would go to the printer. Output can also be pipelined using the | character, for use with programs like more. V. Help! For help type : C:> dirsize -h A short help message will appear. VI. Miscellaneous Stuff. This uses the same recursive method as my LST program. A directory tree is built recursively and dynamically. While this doesn't use THAT much memory, it does need some. If you get one of those cryptic "out of memory" messages, then that's probably why. I've noticed some weirdness with pipelining (|) . I haven't figured this out yet. Sometimes when you pipeline to a program, it generates an "illegal output file" type message. Since the program outputs to standard output, I don't see why this happens. The same is true for LST v3.0 . If I figure it out, a .1 rev will come out, eventually.