Disk Defrag

My main machine was getting pretty fragmented, so I ran graphical disk defrag program provided with XP. After it ran, my disk still had 27% file fragmentation and it was recommending that I needed to defrag again. In my online search for a better defrag utility, I discovered that there’s command line defrag utility. I tried it out, and now I’m at 0% fragmentation. I’m not sure why the command-line utility did so much better than the GUI version, but safe to say I’ll be using the command line version from now on.

I was going to try out the SysInternals PageDefrag utility to defrag my system files, but they’re already contiguous. Not sure if they were that way before or if the windows defrag tool took care of them too.

Posted by devhawk.net on March 3, 2004.

4 Comments

Matt Berther · March 3, 2004

I use Raxco's Perfect Disk (http://www.raxco.com) for the offline defrag capabilities and for scheduling defrags. The *best* tool available for defrags, IMO.

Pablo F Matute · March 3, 2004

I have a good experience with Executive Software's Diskeeper (http://www.executive.com/coverpage.asp) No regrets yet

Steve Tibbett · March 5, 2004

Set up a scheduler task to run the command-line defrag every day at 3am (or some time when you're not on the computer, if you're a late night sort) and you'll never have to worry about it again. I have it output to a file so I can see how fragmented my system is when I get curious.

redvamp128 · March 10, 2004

it is possible that because of the anylize components were in use to render what it is doing. Video Drivers using the render as well as the anylize to show in graph process. This would be my logic the command line calls upon less resources so thus would leave more possible to defrag.I have also seen that by using a second OS to defrag the first idefrags more than when not in the OS. Also it could be a flaw in the program. I have seen that as well in command line utilities as well. It could represent 0% as being with resources current in use. Not to mention the one in the OS could start at true 0% before proccess running. Or it may ignore things like page file sizes and security description.