Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Authentication-Warning: pent584.us.dg.com: bcurran owned process doing -bs Date: Tue, 4 Sep 2001 10:03:11 -0400 (EDT) From: Bill Mills-Curran X-Sender: bcurran AT pent584 Reply-To: Bill Mills-Curran To: Don Sharp cc: gnuwin32 Subject: Re: tcsh problem In-Reply-To: <3B94DC2F.86ECB4D3@iee.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Don, It's a long, sad story. It involves getting old and feeble, and poor assumptions... If you don't care to read about stupid assumptions, then just delete this email... When I had originally started debugging the problem, I did not know about "cygcheck". I also assumed that the problem might be with my installation of cygwin, which was totally contained on my C: drive. What got me is that the offending extra CYGWIN1.DLL was "secretly" installed on a shared filesystem (my T: drive). It was put there by someone else , and I don't know why it's there. I'll be finding that out soon. :-) There was a strange series of events that caused me not to find the extra CYGWIN1.DLL when I finally did learn about the "cygcheck" command. (I think my T: drive was not always mounted.) When I sent my email to this group, I assumed that I didn't need to check the output of cygcheck again -- after all, "I had done my homework already". Ooops. Thank you all for your help. Bill On Tue, 4 Sep 2001, Don Sharp wrote: > Date: Tue, 04 Sep 2001 14:50:39 +0100 > From: Don Sharp > To: Bill Mills-Curran > Cc: gnuwin32 > Subject: Re: tcsh problem > > > 586k 2001/08/09 t:\ADE\bin\CYGWIN1.DLL - os=4.0 img=1.0 sys=4.0 > ^^^^^^^^^^^^^^^^^^^^^^ cygwin number one > > > "cygwin1.dll" v0.0 ts=2000/8/3 20:53 > > 115k 1999/09/14 C:\Cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0 > > "cygitcl30.dll" v0.0 ts=1999/9/13 22:46 > > 63k 1999/09/14 C:\Cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0 > > "cygitk30.dll" v0.0 ts=1999/9/13 22:47 > > 474k 1999/09/14 C:\Cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0 > > "cygtcl80.dll" v0.0 ts=1999/9/13 22:31 > > 19k 1999/09/14 C:\Cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0 > > 24k 1999/09/14 C:\Cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0 > > "cygtclreg80.dll" v0.0 ts=1999/9/13 22:31 > > 768k 1999/09/14 C:\Cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0 > > "cygtk80.dll" v0.0 ts=1999/9/13 22:36 > > 786k 1999/09/14 C:\Cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0 > ^^^^^^^^^^^^^^^^^^^^^^^^^ cygwin number two > > "cygwin1.dll" v0.0 ts=1999/9/13 23:44 > > What say you now bill? > > Cheers > > Don Sharp > > > Bill Mills-Curran wrote: > > > > Michael, > > > > I have evidence that suggests otherwise, but I'm open to suggestions > > for further testing. The evidence I have is: > > > > - Windows "find" shows only 1 > > - No problems occur at the DOS shell, nor in sh or ksh. > > - The problem is intermittent, although it's usually there. > > > > Thanks, > > Bill > > > > On Tue, 4 Sep 2001, Michael Erdely wrote: > > > > > Date: Tue, 4 Sep 2001 09:14:14 -0400 > > > From: Michael Erdely > > > To: cygwin AT cygwin DOT com > > > Subject: RE: tcsh problem > > > > > > You CLEARLY have two copies of cygwin1.dll. > > > > > > -ME > > > > > > > > > -- > > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > Bug reporting: http://cygwin.com/bugs.html > > Documentation: http://cygwin.com/docs.html > > FAQ: http://cygwin.com/faq/ > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/