Message-ID: <4B3BF621.4060003@29west.com>
Date: Wed, 30 Dec 2009 18:53:53 -0600
From: Dave Trollope <dtrollope@29west.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 1.7.1: Mintty/bash window start: -bash: regtool: command not    	found
References: <4B31DB5D.20501@veritech.com> <416096c60912230215m5ea84a07hc97fe225c8db3208@mail.gmail.com> <4B38F3CB.1060808@etr-usa.com>
In-Reply-To: <4B38F3CB.1060808@etr-usa.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Hi,

I too have seen this behaviour on both my work and home systems. Whats 
interesting is I ran cygcheck -c on each when exhibiting this problem 
and it said OK for the cygwin package.

Is there a check that needs to be added to cygcheck which reports this 
as a problem? Or perhaps this is not the type of problem cygcheck is 
designed to detect?

Cheers
Dave

On 12/28/2009 12:07 PM, Warren Young wrote:
> On 12/23/2009 3:15 AM, Andy Koppe wrote:
>>
>> I can reproduce this as follows:
>>
>> - Leave a Cygwin session open.
>> - Run setup.exe
>> - Select reinstall for cygwin-1.7.1-1.
>> - Click next
>> - "in-use files detected" appears
>> - Click retry.
>
> I saw the same symptom, but by a slightly different path.
>
> On updating from 1.7.0.68 to 1.7.1 this morning, I ran into the 
> files-in-use case because sometime last week, Xwin.exe died horribly 
> and left a UI-less process running in the background.  When setup.exe 
> complained, I investigated with Task Manager, found Xwin.exe still 
> hanging around, killed it, and told setup.exe to move along.  It 
> completed without complaint, but I still didn't end up with a regtool.
>
> I didn't check for ps or mount, just retried setup with a forced 
> Cygwin package reinstall, and that worked.
>
> Point being, it isn't necessary to lie to setup.exe, telling it it's 
> okay to try again.  It *was* okay in my case, and it still did the 
> wrong thing.
>
>> It can be fixed by reinstalling the cygwin package again, this time
>> without any Cygwin processes running.
>
> Confirmed.
>
> -- 
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

-- 
                      David Trollope
                   dtrollope@29west.com
                    (630) 836-2990x309
                      AIM:dstrollope
                       29West, Inc.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple