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: "Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
Cc: cygwin AT cygwin DOT com
In-Reply-To: <NCBBIHCHBLCMLBLOBONKKEIODIAA.g.r.vansickle@worldnet.att.net>
References: <NCBBIHCHBLCMLBLOBONKKEIODIAA DOT g DOT r DOT vansickle AT worldnet DOT att DOT net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-OAIRv4CRx7iqwcg63hpQ"
Date: 25 Nov 2002 20:46:01 +1100
Message-Id: <1038217563.23988.267.camel@lifelesswks>
Mime-Version: 1.0

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

On Mon, 2002-11-25 at 15:43, Gary R. Van Sickle wrote:


> > I recall being unhappy about having the list of pages in two places, an=
d
> > it's obvious why now.
> >
>=20
> "List of pages in two places"?

In main.cc we list the pages, create instances, and add to the propery
sheet. So there is one list.
The second place is that each page knows what page follows, and will
alter this on occasion.

This isn't a reflection on your framework per se, the old code was
really intertwined, and what you've done is a serious improvement.
=20
> Well, that's not the whole story.  Pre-"Property Sheetization", each page=
 had to
> know what the next page was supposed to be at all times, sometimes in mul=
tiple
> places, and call it up.  Now, they don't have to know any of that, *unles=
s*, as
> you say, the default order of presentation (i.e. the order in which the p=
ages
> were added) needs to be changed dynamically.

Yep. I'd like to remove that 'unless' :}.


> is not yet ready for prime-time.  I'll get something sensical to you thou=
gh in a
> few (>1,<24) hours.

Can't ask for more than that :].
=20
> Didn't know there was a virus-scanner disabling interface that you cold d=
o this
> sort of thing with, that's cool.  I wonder if the virus writers know abou=
t
> it....

Heh, I bloody hope they do. It's the standard NT service control
interface I'm using. 'most' users have access to start and stop
services, outside of certain locked down IT departments. And Services
have DACL's, so ...

Anyway, I *ask* the user about disabling it, hopefully that will stop
some enthusiastic but misguided mcaffee person from considering
setup.exe a virus!

BTW: anyone here who:
*) Is a 'supported' mcaffee user
*) can reproduce the Blue Screen (hint: I think large internet downloads
with connection set to 'ms ie5 settings' followed by the install process
is the trigger)
*) Is willing to submit a fault to mcaffee and ride herd till it gets
fixed?

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

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

iD8DBQA94fFZI5+kQ8LJcoIRAvNqAJ9TK4Sct2Xp+yKNGA1JHa70uZyUTQCgl1eg
63luJRFYKWeam8rdO0ejs5Q=
=T5lc
-----END PGP SIGNATURE-----

--=-OAIRv4CRx7iqwcg63hpQ--