It seems that there are two camps on this one: 1) Those that use Diskeeper (as we do) don't find the need to stop anything. Diskeeper will not be affected by other processes accessing any file. The only affect Diskeeper has while running is a slowdown in disk performance. We schedule it for every night at 1:00am (when only the spammers are running!!).
2) Those that use the internal defragger that feel the need to stop services for safety. I didn't think this was necessary on the internal defragger, but I don't use it, so don't take my word for it. The internal defragger should be Diskeeper Lite, written by Executive software and licensed to MS. Conclusion: Using full Diskeeper has fewer issues to be dealt with and the defrag process can be isolated from other processing. Use full Diskeeper, its worth the money! Todd Holt Xidix Technologies, Inc Las Vegas, NV USA 702.319.4349 www.xidix.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick Klinge Sent: Friday, February 20, 2004 10:45 AM To: [EMAIL PROTECTED] Subject: RE: [IMail Forum] Defrag on Win2000 A reply to my previous post. Looks like the formating got messed up so here's a zip file instead. Got to love it.. ~Rick > > Neil, > > Right, wrong, or indifferent here is what I use. I have > purposely prefixed spaces " " before any executables > (executable. com) in order to hopefully bypass any spam or > virus filters. Please give this thoughtful consideration if > you make these files and omit the space. All comments and/or > suggestions are welcome. > --- [This E-mail scanned for viruses by Declude Virus (http://www.declude.com)] To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
