Quote Originally Posted by kleinma View Post
The reason I find it acceptable is because I have no issue with the defrag in Vista or Windows 7. In fact, I never run it. Do you like to sit there and stare at a meaningless bar of blue and red, making your mind think your computer just got a massive hardware upgrade because the red sections are now blue?

The defrag in Vista is designed to run in the background. Do you sit there and watch your virus scanner run through every file on your system? This is a system level utility which I don't want to know or care about.. I have better things to do like write software.

My comments are just that I don't think capsulecorpjx, or you, or myself is an expert on NTFS and hard disk fragmentation of the file system. So my apologies in advance if I am wrong at that. So I trust the experts on it, who built the system.

Here is a good read, which will answer/counter most of the questions/arguments about the defrag.

As for why it takes so long, it is SUPPOSED TO... it runs with super low IO and CPU resources because it is designed for background operation so that your computer doesn't get bogged down at all, again, because it isn't supposed to be something for you to be concerned about as the user.
First rule of good user programming is always provide status, the user will not think the thing is in some infinite loop or hung forever.

Second rule is, don't run a program with the lowest possible priority without at least telling hte user, or giving the user the option to run it at a higher priority. Having Defrag running at low priority over many days doesn't even make sense, that means you're letting the user fragment the disk with use, WHILE the utility is trying to defrag it.

Also, not everyone leaves their computer on days in a row, which seems to be what MS Defrag need to actually do the defragging.