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: <416E3FEA.70405@research.canon.com.au>
Date: Thu, 14 Oct 2004 18:59:22 +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: <NUTMEGCQ0UTELuAMXi8000003ce AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <416CD333 DOT 9030907 AT research DOT canon DOT com DOT au> <416CDE5A DOT 2000107 AT research DOT canon DOT com DOT au> <416DEC47 DOT 7090500 AT research DOT canon DOT com DOT au> <416E1625 DOT 7040909 AT research DOT canon DOT com DOT au>
In-Reply-To: <416E1625.7040909@research.canon.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

luke wrote:
[...]
>> I'll let people know how I get on.  Plan: first the FS check, then 
>> I'll try installing a stable known to work Cygwin, then I'll scrub and 
>> reinstall W2K, then I'll give up and try another PC.
> 
> 
> Well, since I know the MD5 checksums are correct on both our local
> stable Cygwin mirror, known to work, and on the nightly mirrored
> "latest" mirror, and since these mirrors work on other PCs, it starts to
> look like the problem is specific to this PC.
> 
> In other words, it appears to have nothing to do with having run "mount"
> from a network install of Cygwin.  (Since all files created by Cygwin
> and all registry entries were deleted, Cygwin stores no other
> information on the system, and yet the problem persisted.)
> 
> I have scrubbed Windows, reformatted the drives, and am re-installing 
> W2K now.  I fully expect this to fail as well.
> 
> In which case I'll just pick a different PC that Cygwin can be installed
> on, and go back to testing what I was originally trying to test!

Basically, that worked.  It appears that Cygwin made some change that
persisted even after deleting all the Cygwin files and registry entries.

Our stable mirror is from some months ago - I got the error in the
postinstall about some missing cygwin gtk dll, but installation
completed okay, and re-running setup seemed to complete quickly (apart
from re-installing gcc, as it always does i've noticed).

The *only* thing I did different was save downloaded files to
c:\temp\cygwin instead of to d:\temp; and I didn't try running "mount"
from a network Cygwin either.  (Though I really don't think that was the
cause: too many Cygwin deletes, registry Cygwin deletes, and reboots in
between - how could the effect possibly have persisted?)

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/