Well, here's a "bug" of sorts: the program spends more time thinking about what file to move next than it does actually moving the files. I am puzzled immensely by this, as I would expect that a computer that can calculate 16.7 million digits of Pi in 3.8 seconds could figure out what file to move next in less time than that, but sometimes there is no disk activity while D is running for upwards of a second, then just a quick blip, and another wait. When a large file is being moved, the disk stays busy, but then it goes right back to thinking only. It doesn't take a genius to figure out that if it takes 500ms to figure out what to do next after each and every file move, it will take a very long time to defragment most hard drives. Is there any way to tighten this down?
640GB Samsung, Vista SP2