I have been using JKdefrag for years. I even use it on Windows 7. It's fast, reliable, uses very little resources (for the job it has to do.) Before Windows 7 if a user wanted to defragment all drives or partitions it was necessary to do each one, one at a time using Windows built in defragmenation software. An absolute and annoying stupidity, indeed. JKdefrag therefore was liberation from what I considered to be 'stupidware'. Recently I downloaded MyDefrag, authored by the designer of Jkdefrag, This basically puts all of the separate JKdefrag segments into one box. Whereas in the past I only used the basic JKdefrag file, here we have a compiled package. It offers built in script options. One of those options is defragmenting by file path... This, the program warns, will take a great deal of time. (It does.) For the novelty of trying this, I am defragmenting three of my computers in this manner today. But before I even began even trying this option, I had my doubts. What would it really accomplish, and was there a reason to do this ? And that is the reason for this post. I seem to have done quite well in the past with normal defragmentation (compiling files in one segment with the general intentions of putting the finished library in a similar space on my harddrive, instead of hither-schither, everywhere and anywhere.) I find myself wondering what is to be gained by sorting all of my files by directory and file path. I would tend to think that my computer is going to run rather quickly with the files simply defragmented, and that in the end humans are more obsessed with having all things in the same box more than it would have any significance to my computer to do so. This sort of reminds me of the way dog and cat owners buy foods for their cats based on their human preferences, while in the end their pet just wants the food that stinks the most. Can anyone educate me regarding this?