Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 15 May 2002 09:04:39 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Latest Setup.exe Fails (Win2k) Message-ID: <20020515130439.GH11699@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.0.20020515132706.00af5298@mail.leegoddard.com> <5.1.0.14.0.20020515132706.00af5298@mail.leegoddard.com> <5.1.0.14.0.20020515144512.02c30e70@mail.leegoddard.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20020515144512.02c30e70@mail.leegoddard.com> User-Agent: Mutt/1.3.23.1i On Wed, May 15, 2002 at 02:53:30PM +0200, Lee Goddard wrote: >In every case, the systsem hangs with the dialogue box saying >"This space intentionally blank" (or such) and the window is shown >as "Not responding" in Windows' task manager, with 100% use >of a 1400 mhz CPU. I hate to chime in with a "me too" but I saw this behavior once myself while debugging setup. I was quite excited that I could finally duplicate the problem but I couldn't break out the hung executable in the debugger and, after killing the process, I could never duplicate the problem again. These are very minor data points but I thought I'd share them. cgf -- 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/