X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48D83EF8.5040401@cwilson.fastmail.fm> Date: Mon, 22 Sep 2008 20:57:28 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/20080708 Thunderbird/2.0.0.16 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem to open big selfextracting Zip files from bash -- on task now References: <48D3B01F DOT 5080200 AT oracle DOT com> <9721D18815A74E3790E86A5BC19A461A AT collinsdirect DOT com> <48D74687 DOT 80002 AT oracle DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Barry Smith at SourceLink wrote: > I just read a thread where Cyg-X RUN.EXE would cause a blue screen crash, 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. -- 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/