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: Daniel Armbrust <daniel DOT armbrust AT charter DOT net>
Cc: cygwin AT cygwin DOT com
In-Reply-To: <000101c293d4$d4d19510$0400a8c0@vortex2533>
References: <000101c293d4$d4d19510$0400a8c0 AT vortex2533>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-chkOp5GYPuakLobI0iHj"
Date: 25 Nov 2002 07:17:15 +1100
Message-Id: <1038169036.23988.82.camel@lifelesswks>
Mime-Version: 1.0

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

On Mon, 2002-11-25 at 03:16, Daniel Armbrust wrote:
> Every time that I run the cygwin installer program, when it finishes
> downloading packages, and moves to the install step, it bluescreen
> crashes my Windows XP machine (service pack 1) with the following error:

Does it creash before or after the dialog box appears that says

  Installation complete
         [OK]

?

If that doesn't show up, then it's not a setup.exe issue per se (or at
least not the interesting and unpleasant kb article you found :}). If
it's not setup triggering that

If you set your machine to write a minidump file (or a normal dump file
on NT 4), you can use the MS debugging tools to get a backtrace of the
failure. That *might* indicate the running program that failed. There
are a number of sub programs (post install scripts) that setup.exe runs,
but it's would surprise me to have those tickle a bug after a download
and not when installing from local dir.

If the NT 4 machine crashes every time, would you be willing to run a
special debug version of setup, that will write it's log entries to the
event log? They should be visible post install then, and you can tell us
what the last ones recorded are.

Oh, and finally, I second Max's comments - blue screen =3D=3D kernel oops =
=3D=3D
OS bug.

Cheers,
Rob
=20

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

--=-chkOp5GYPuakLobI0iHj
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)

iD8DBQA94TPLI5+kQ8LJcoIRAtZiAJwOlXkARyuDY9Yvf9YJlih7Rw9CSwCgg1Iq
ficHTsP64k8O8LV0u6xhH7Y=
=BjpE
-----END PGP SIGNATURE-----

--=-chkOp5GYPuakLobI0iHj--