Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Setup failure: mount error Date: Fri, 15 Oct 2004 10:08:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <416F8828.3070708@research.canon.com.au> Message-ID: X-OriginalArrivalTime: 15 Oct 2004 09:08:00.0814 (UTC) FILETIME=[78680CE0:01C4B296] > -----Original Message----- > From: cygwin-owner On Behalf Of Luke Kendall > Sent: 15 October 2004 09:20 > Luke Kendall wrote: > > > Anyway, the final experiment I can try now is to run > "mount" from the > > network install, and see it it makes Cygwin uninstallable > again, without > > a Windows reinstall. > > Okay, after doing running the command: > > mount > > from the network-installed Cygwin, on the local machine the > registry is > changed to have keys under HKCU and HKLM Software->Cygnus Solutions-> > Cygwin->mounts v2-> (Default) REG_SZ (value not set). Yes, running *any* cygwin app will re-create the cygwin registry keys with default contents if they don't already exist. Particularly mount, of course, since the main purpose of the cygwin registry keys is to store details of mount points. > Dunno. Maybe this is just a weird PC. I can't reproduce the problem. Yeh, I was starting to think we should just shrug and go "Musta been some kinda bizarro transient h/w failure" unless you can find a way of repeating it. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/