Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <416F0CF4.8010602@research.canon.com.au>
Date: Fri, 15 Oct 2004 09:34:12 +1000
From: luke <luke AT research DOT canon DOT com DOT au>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Setup failure: mount error
References: <NUTMEGp8eurQQtHT1Dd0000048b AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
In-Reply-To: <NUTMEGp8eurQQtHT1Dd0000048b@NUTMEG.CAM.ARTIMI.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dave Korn replied to:

>>Basically, that worked.  It appears that Cygwin made some change that
>>persisted even after deleting all the Cygwin files and registry entries.
> 
> 
>   ?!?!?!?  This seems highly improbable.  What else _could_ there be?  Maybe
> something different in the environment vars between the two machines was
> causing it?  Maybe some different software that was installed on the failing
> machine was causing dll hell or something?
> 
>   Ever heard of InCtrl5?  Dead useful app, see if you can find a download of
> it on the web somewhere.  Could be very useful if a situation like this ever
> arises again: it takes a snapshot of your entire system (files and
> registry), then you run an installer, then you run InCtrl5 again and it
> takes another snapshot and compares the two, so you can see exactly all the
> changes that an installer has made to your system.
> 
>     cheers, 
>       DaveK

All this happened on a PC with no OS installed until I installed W2K.
The purpose was to test Cygwin.

So the very next thing (the only thing) I did was (try to) install
Cygwin.

But thinking about it last night, there was one other difference: I
created a file c:\cyg.bat that simply set PATH to include the directory
where I keep various helper Cygwin scripts (like the .bat to drive the
install via setup).

Perhaps that somehow got run by setup or by one of the post-install
scripts instead of some (internal) Cygwin command called "cyg"?

I can test both theories by trying to reproduce the problem.

luke

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