Caffeine Induced

I’ve noticed that when I’m doing development, the D drive gets fragmented very quickly (even in one days time). After a full day's coding, I usually manage to create 1000 or so fragmented files (even when the machine has been completely defragged the day before). This is after doing full rebuilds, re-installations of the appserver (we have an ant target to completely wipe out our Jboss directory and re-install it), pulls from CVS, etc..

Anyway – you can setup Windows built in defrag tool to run on a recurring basis. Here’s how :

Create a batch file (e.g. c:\bin\DefragLocalDrives.cmd) with the contents similar to the following (customize to your local drive structure):

   defrag /v /f c: > d:\temp\Defrag_C.txt

   defrag /v /f d: > d:\temp\Defrag_D.txt

I set mine up to run every morning at 4:30 AM. At first I thought this would be overkill, but I’ve noticed that when doing development I always have some fragmentation, even after only a day’s use.

That’s it…

UPDATE - As Lance Lavandowska kindly pointed out - this only works on XP (defrag.exe is not present on Win2k installations)

http://sourceforge.net/project/shownotes.php?release_id=167306

We're using 2.0.2 on my current project and we love it. It takes a bit of maintenance and troubleshooting here and there (especially as the size of the project and number of tools grows), but it is definitely worth the investment to set your projects up in this.

• HTML 4.01
• CSS 2
• Javascript (Reference and Guide)
• XSLT