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: Thu, 14 Oct 2004 13:33:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <416E3FEA.70405@research.canon.com.au> Message-ID: X-OriginalArrivalTime: 14 Oct 2004 12:33:56.0126 (UTC) FILETIME=[12554BE0:01C4B1EA] > -----Original Message----- > From: cygwin-owner On Behalf Of luke > Sent: 14 October 2004 09:59 > > 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. > 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 -- 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/