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 Date: Fri, 17 Jan 2003 21:43:23 +0200 From: Ville Herva To: cygwin AT cygwin DOT com Subject: FindFirstChangeNotification BSODs (Re: please try the latest snapshot) Message-ID: <20030117194323.GG4822@niksula.cs.hut.fi> References: <20030117055216 DOT GA4969 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030117055216.GA4969@redhat.com> User-Agent: Mutt/1.4i On Fri, Jan 17, 2003 at 12:52:16AM -0500, you [Christopher Faylor] wrote: > The latest snapshot should fix some /etc handling problems (thanks to > ideas and code from Pierre Humblet), like the dreaded BSOD. It may also > solve the "pipes are slow" problem. There are also all of the fixes > accumulated since 1.3.18, of course. > > If I don't hear too many whines about this snapshot, it may become > 1.3.19. I've got a contact at Microsoft support who is listening about these BSOD issues (I was quite surprised they actually answered when I submitted a report on cygwin causing BSODs...). They are not quite keen on installing the whole cygwin suite (be it free or not), though. However, if some of you who have played with the /etc FindFirstChangeNotification stuff would have the time and patience to wrap up a small .exe (preferably with source of source) that reproduces the problem, I think they would be very interested (only and assumption based on the pretty good feedback I've gotten so far). I'm afraid I'm too busy and unversed to do that myself.... -- v -- v AT iki DOT fi -- 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/