Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.1.0.14.2.20020901171800.028cf6d8@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Sun, 01 Sep 2002 17:23:56 -0700 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: BSOD using vi? In-Reply-To: <3D72A459.1090701@sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Rob, Cygwin installs no drivers or kernel-mode code which could itself be the culprit of a BSOD. That doesn't mean software running under Cygwin won't trigger an otherwise latent bug. Personally, I find Windows 2000 very reliable, but that is not necessarily true. Poorly written drivers can render Win 2K (or any OS) unreliable. This is an opinion, but virus protection that runs in an active-scan or "always-on" mode is not desirable. How many valid positives does it detect? Don't you know when you've downloaded suspect content? Check such files manually and leave it at that. Randall Schulz Mountain View, CA USA At 16:35 2002-09-01, Rob Philip wrote: >I just installed cygwin and am way happy with it - however, whilst editing >my X0.hosts file, immediately upon my :wq command, Windows 2000 BSODded on me. > >I was editing in an Xterm window, BTW. > >I also saw a BSOD at an earlier point when "closing" the x-windows window. > >I'm running W2K, Service patch 3, plus Zonealarm, the symantec anti-virus >stuff. > >Thoughts? -- 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/