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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: "Lagstein, Yossi" To: "'cygwin AT cygwin DOT com'" , "'robert DOT collins AT itdomain DOT com DOT au'" Subject: RE: 1.3.4 - touch /etc/abc causes BSOD Date: Tue, 26 Feb 2002 08:56:55 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="windows-1255" It may be Microsoft bug, but since The trigger for the BSOD is cygwin, and I'm unable to reproduce it with non cygwin relegated software, I hope that other people that encounter the same or similar problem may have some idea on how to solve the it Yossi -----Original Message----- From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au] Sent: Sunday, February 24, 2002 10:17 AM To: Lagstein, Yossi; cygwin AT cygwin DOT com Subject: RE: 1.3.4 - touch /etc/abc causes BSOD > -----Original Message----- > From: Lagstein, Yossi [mailto:Yossi DOT Lagstein AT starhome DOT com] > > > I opened a bug with Compaq support, they said it's a software > problem, gave > me the following: > http://support.microsoft.com/default.aspx?scid=kb;en-us;Q130802 > http://support.microsoft.com/default.aspx?scid=kb;EN-US;q165863 > > to read and told me to approach the software vendor (cygwin) > that causes the > BSOD. The software vendor that creates NTOSKRNL.EXE is the one to approach - which is Microsoft. Rob -- 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/