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: <005601c1e978$2d0c1b40$0101a8c0@albion> From: "Cliff Hones" To: References: <20020420070212.GA3256@redhat.com> <20020420163557.GB3256@redhat.com> <20020420223827.GA9745@redhat.com> <008a01c1e8bf$bd036b40$0101a8c0@albion> <002f01c1e932$f05abe80$0101a8c0@albion> <20020421181601.GB1121@redhat.com> Subject: Re: I am not going to let cygwin BSOD my Windows 2000 Server Date: Sun, 21 Apr 2002 22:04:48 +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 cgf worte: > ... > I appreciate your (Cliff) letting people know about your experiences > with Norton on XP. ... Actually it was with NT4SP6. And I can't be sure that it was a bug in the Symantic/Norton code, as the system had been 'repaired' and the Norton s/w was rather old. But it does illustrate that 3rd party background monitors can confuse and destabilise windows systems. -- 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/