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
Message-Id: <5.1.0.14.2.20020521201433.022e6e48@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Tue, 21 May 2002 20:22:41 -0700
To: Sebastian Schuberth <s DOT schuberth AT tu-bs DOT de>, cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: Crash during setup
In-Reply-To: <MPG.1754e49390e79c6d989680@news.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Sebastian,

Patience is one suggestion. I have a fast machine with fast disks and a 
fast, dual-channel SCSI I/O adaptor (and the install cache and the Cygwin 
working directories are on separate disks and those disks are on separate 
I/O channels) and still it takes a long time for Setup to determine what to 
offer to install. There simply are a lot of separate I/O operations to 
perform to prepare the installation list.

There have been reports that indicate CPU saturation while the 
"intentionally blank [sic]" page is displayed. That's not the case for 
normal operation, of course. Use the "Processes" tab of the "Windows Task 
Manager" to check for this condition. If the CPU utilization is low, then 
Setup is probably still comparing your install cache to your active 
installation.


Randall Schulz
Mountain View, CA USA


At 15:11 2002-05-21, Sebastian Schuberth wrote:
>Hi there,
>
>I'm trying to run Cygwin setup 2.218.2.9 on Win2k but it always crashes at 
>the same point: After selecting the mirror and downloading setup.ini a 
>page saying "This space intentionally left blank" appears and the program 
>does not respond to input anymore. The only way to close it is to kill the 
>task. Any hints how to avoid this?
>
>--
>
>Sebastian Schuberth


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