Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
cc:	irwin AT bongo DOT local
Subject:	Re: bash page fault on Win98SE when running non-Cygwin programs
Date:	Sat, 18 Jun 2005 12:05:03 -0400
From:	irwin AT bongo
Message-Id:	<E1Djfod-0008Aq-Bt@bongo.local>

On Fri, 17 Jun 2005 21:49:39 -0400, Christopher Faylor wrote:
>Corinna managed to narrow down the problem with 16-bit programs so there
>will be a fix in the next snapshot (and eventually in 1.5.18) but
>without specific information about failing 32-bit programs there will be
>no fix forthcoming for that problem.  Since all of cygwin consists of
>32-bit programs, this problem cannot be too prevalent.

As it turns out, the 32-bit program that I thought was causing the problem was
actually running a a very old EMX (remember EMX?) binary, which was the real
culprit. My apologies for the misdirection.

>Please try the 2005-Jun-18 snapshot when it eventually shows up at
><http://cygwin.com/snapshots/>.

The cygwin1 DLL in this snapshot has fixed the problem, at least for the 16-bit
programs I have tried. My thanks to you and Corinna.

>In case it isn't obvious, this is a Windows 98/Me bug, not a Cygwin bug.
>That hardly matters, since we still have to deal with it, but I thought
>I should mention this fact in the interests of full disclosure.

A Windows bug? I'm shocked. Shocked!

/Irwin Meisels
irwinm at rogers dot com

--
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/

- Raw text -