Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Subject: RE: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
From: Robert Collins <rbcollins AT cygwin DOT com>
To: Randall R Schulz <rrschulz AT cris DOT com>
Cc: cygwin AT cygwin DOT com, Daniel Armbrust <daniel DOT armbrust AT charter DOT net>
In-Reply-To: <5.1.0.14.2.20021124131806.03241008@pop3.cris.com>
References: <00bf01c293d6$c62800b0$78d96f83 AT pomello> 
	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021124131806 DOT 03241008 AT pop3 DOT cris DOT com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-IS5IMgGKWWbj1v1GIBXu"
Date: 25 Nov 2002 07:40:39 +1100
Message-Id: <1038170441.23476.89.camel@lifelesswks>
Mime-Version: 1.0

--=-IS5IMgGKWWbj1v1GIBXu
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2002-11-25 at 08:27, Randall R Schulz wrote:


>=20
> Likewise, it cannot be the locus of a fix for such a problem. While I=20
> certainly cannot speak for others who read this list, I doubt anyone is=20
> going to a) be able to help you much to solve this situation, since it is=
=20
> surely idiosyncratic and specific to your system; b) be motivated to do s=
o.

Randall, I think this is a little to enthusiastic! While setup.exe is
not the root cause of the problem, it may be triggering the fault - and
because (assuming that kb 195857 is the cause (*))
a) cygwin is for windows
b) this fault is apparently endemic to windows
c) MS haven't fixed it

The onus is on us to have cygwin work around the fault. We've done that
before, we'll do it again. Daniels email was informed, researched, and
pleasant - so I'll certainly be assisting (but not admitting to a setup
'bug' per se :}) and I suspect Max will too.

Rob

(*) The technet article doesn't list XP as suffering from the fault,
which I read to mean that the fault is fixed in XP, and (inferring here)
is a kernel issue which would change current published 2K and NT
behaviour, thus will not be fixed on those kernels.


--=20
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

--=-IS5IMgGKWWbj1v1GIBXu
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA94TlHI5+kQ8LJcoIRAk2nAJ9zJDh67R26ZkAWyAv7U+jJuBsbewCfXDkP
rtefqCOk4rERNtZ0EhYvq6Q=
=SI6d
-----END PGP SIGNATURE-----

--=-IS5IMgGKWWbj1v1GIBXu--