Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <008a01c1e8bf$bd036b40$0101a8c0@albion> From: "Cliff Hones" To: References: <20020420070212.GA3256@redhat.com> <20020420163557.GB3256@redhat.com> <20020420223827.GA9745@redhat.com> Subject: Re: I am not going to let cygwin BSOD my Windows 2000 Server Date: Sun, 21 Apr 2002 00:03:57 +0100 Organization: Aonix Europe Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Christopher Faylor wrote on Saturday, April 20, 2002 11:38 PM: > ... You might also want to invest in > something like Norton Systemworks which has diagnostic tools that may > help narrow down what's wrong with your system. Hmm. Recently we had an NT system which was frequently BSOD'ing (not Cygwin-related). It had Norton Systemworks installed. When this was uninstalled, the problem went away. I suspect the file deletion recovery extensions were to blame. If you are having stability problems with any Windows product, it is adviasable to (a) (as Chris suggested) ensure you have the latest service packs/hotfixes/security upgrades and (b) remove or disable any 3rd party software which runs in the background (eg Antivirus, filestore extensions, system monitoring etc.). -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/