TatSteeL and Davegod75,
I'd say the "lite" version of Diskeeper included with W2K is probably sufficient for many, if not most people, but I would add a provision to that statement. A lot of people buy OEM imaged systems the consumer versions of which invariably come formatted FAT32. For instance, Dell doesn't offer to ship Dimensions or Inspirons formatted NTFS, but they do offer NTFS format as an option with Optiplex and some Latitude models. Also, a user who installs her/his own system may try FAT32 before deciding to move on to NTFS. If a user winds up using the CONVERT utility, s/he winds up with 512 byte clusters. If the partition is large, the overhead for keeing track of 512 byte clusters is humongous, and the fragmentation forced on the MFT by this small cluster size will eventually cause W2K to run VERY slowly.
The point I'm getting at is that the included defragger won't defrag the MFT. Some of the third party defraggers, including the "heavy" version of Diskeeper from Executive software, can be set to defrag the MFT at boot time. Some even have settable automatic thresholds that cause this boot time defragmentation to occur when the MFT has reached the specified level of fragmentation.
I'd also point out that there are small, but significant to some, gains to be had by placing the MFT, pagefile, and directory entries at the front of a partition. Some of the defraggers allow a certain degree of control over file placement, and that can be useful on heavily stressed systems.
But I agree that, for those who use FAT or FAT32, and perhaps for many who use NTFS, the in-built defragger works well enough. On the other hand, I see people adding all sorts of crappy, invasive, OS-farkling utilities to their systems. Defraggers are at least less likely to affect a user adversely than a third party registry cleaner, uninstaller, or a crash "guard" -- particularly when most such utilities allow an inexperienced user enough latitude to cause serious harm to the OS and installed software configurations.
Regards,
Jim