defragging and optimizing

Might try ScanDefrag or JkDefrag v3.16. Might find some other handy utilities at the sight. It also helps to delete the temp files prior to defragging. Also, before defragging, It may be helpful to run utilities such as RegSeeker to cleanup the Registry, as well as NT Registry Optimizer to then condense the Registry.

None of these thing ensure complete contiguation of all files, but they help. Also, these particular utilities may still leave a few empty areas so that in the future some application files won't become scattered too far and wide when they do become fragmented.

As always, be sure to first create a System Restore point or other reliable system backup prior to installing new programs in case they happen to render unfavorable result. For this you may want to consider The Emergency Recovery Utility NT as it does a much better job of returning the system to a previous state. That is, when used to restore the system, it actually removes files often left behind by System Restore. Also, it creates an exact and complete backup of the System Registry which System Restore in incapable of.

Hope this is helpful.

Charlie

PERFECT DISK DEFRAGMENTER 8 coz its has one of the best procedures and tools for compacting and re-arranging files together. This is much better than Windows Xp Defragmenter, in fact any Windows Defragmenter. This is Certified by Microsoft for Windows and Vista.

Noticeable difference cann be seen by doing once in a month or twice a month. heres the link -> http://www.download.com/PerfectDisk/3000-2094_4-10654012.html

Normally I am not a big fan of defragmenting, but if you're dealing with files that large, you're likely doing some higher end stuff which may benefit from the process.

That all being said, I still wouldn't worry about small bits of fragmentation here and there. There's a difference between trying to optimize things and being obsessively compulsive about it, or anal if you prefer. So long as most files are in big clumps, as opposed to scattered every which way, the performance difference is likely to be negligible. You'd almost certainly spend more time trying to put them all into one contiguous segment then you'd ever "save" in access times.

Also, I know the other person meant well, but the registry has absolutely nothing to do with system performance that is worth mentioning. Registry cleaning and repair programs are completely worthless, and if they're free they're still too expensive. It's just a simple flat file database, the likes of which any first year computer science student should be able to create (and better at that) in their sleep. It's not this mysterious black box component that has all these mysterious and mystical properties like some seem to believe. It's a quick and dirty database for storing program metadata. The idea was to have a central place for program settings, instead of individual INI files... Good idea, implemented about as poorly as could be imagined, in typical Microsoft style.