X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48D8F8AC.F1774B58@dessent.net> Date: Tue, 23 Sep 2008 07:09:48 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [OT] polite response to rather rude reponse... References: <48D3B01F.5080200@oracle.com> <9721D18815A74E3790E86A5BC19A461A@collinsdirect.com> <48D74687.80002@oracle.com> <48D83EF8.5040401@cwilson.fastmail.fm> <29E315C686404A6D8696F355E283DD56@collinsdirect.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Barry Smith at SourceLink wrote: > > Stop spreading FUD. There is no way a userland app like "run.exe" can > "cause" > > a blue screen. Only something running in kernel space -- like windows core > code, > > or certain device drivers -- can ever do that. > > Then I guess you don't read the cygwin archives, because that's where I read > the > entire thread while I was researching RUN/START execution under cygwin. That doesn't mean that 'run' was at fault. If a user-mode program results in a BSOD that means it exercised a bug in a kernel-mode driver, such as a faulty virus scanner or other "security" type crapware. There is simply no way that a user-mode program can cause a BSOD on its own. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/