X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4B38F3CB.1060808@etr-usa.com>
Date: Mon, 28 Dec 2009 11:07:07 -0700
From: Warren Young <warren AT etr-usa DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: Cygwin-L <cygwin AT cygwin DOT com>
Subject: Re: 1.7.1: Mintty/bash window start: -bash: regtool: command not   	found
References: <4B31DB5D DOT 20501 AT veritech DOT com> <416096c60912230215m5ea84a07hc97fe225c8db3208 AT mail DOT gmail DOT com>
In-Reply-To: <416096c60912230215m5ea84a07hc97fe225c8db3208@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

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