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
Date:	Sat, 25 May 2002 10:46:16 +0200
From:	Pavel Tsekov <ptsekov AT syntrex DOT com>
Reply-To:	Pavel Tsekov <cygwin AT cygwin DOT com>
Organization:	Syntrex, Inc.
X-Priority:	3 (Normal)
Message-ID:	<773354854.20020525104616@syntrex.com>
To:	Lee Goddard <home AT LeeGoddard DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re[2]: Latest Setup.exe Fails (Win2k)
In-Reply-To:	<5.1.0.14.0.20020524190851.00aedd78@mail.leegoddard.com>
References:	<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020524152505 DOT 00af85d0 AT mail DOT leegoddard DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020524152505 DOT 00af85d0 AT mail DOT leegoddard DOT com>
	<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20020524190851 DOT 00aedd78 AT mail DOT leegoddard DOT com>
MIME-Version:	1.0

Hello Lee,

Check http://cygwin.com/ml/cygwin/2002-05/msg01547.html - it seems this
problems is very similiar to one you've experienced, huh ? I notice
two common things which look disrturbing to me:

1. Both of you choose the local package directory to resied on
the Desktop.

I've tried this on my WinXP Home notebook (Intel PIII mobile) and
it doesnt seem to cause a crash on my system however.

2. You both have Athlon systems.

I don't want to think that this has something to do with setup
failing  at all, but... who knows :)

I'll try to search the archive for reports  of setup.exe version
2.218.2.9 similiar to your and see if they are also Athlon users,
or what else is common between this reports.

Meanwhile I sugest you:

1. To try the snapshot from http://www.cygwin.com/setup-snapshots/ and see if it fixes the problem

2. I can build a debugguable setup.exe (2.218.2.9) for you and email
you with it. You can then run this setup.exe from within gdb and help
isolate the code that causes the 100% CPU utilization. I'll provide
you with help, if needed, how to debug (in off-list mail).

[snip description]

>>LG> Do I need an INTEL or something horrible?
>>
>>Nope!

I'm not so sure right now :)) Help us to find out :)


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

- Raw text -