On Wed, May 1, 2013 at 8:49 AM, John Guad wrote: > On Tue, Apr 30, 2013 at 6:10 PM, Christopher Faylor wrote: >> On Tue, Apr 30, 2013 at 08:58:17PM -0400, Christopher Faylor wrote: >>>On Tue, Apr 30, 2013 at 05:46:08PM -0700, John Guad wrote: >>>>I googled that message about base mismash and all the evidence points >>>>to cygwin1.dll being the issue but there's nothing useful about fixing >>>>it. The only instance of that dll on this machine is the one >>>>downloaded and installed by the setup.exe program, so it doesn't make >>>>sense to think it's a bad version. >>> >>>People often say that but most of the time they find that there is >>>another version of the dll lurking somewhere on the system, like in >>>c:\windows\system32 . >>
I did a search using the built-in windows search tool ('search companion' ... gotta love XP), selected target "all hard drives" which in my case is just one - "c:\", search term "cygwin", and it tells me that there is one and only one "cygwin1.dll" file anywhere on my machine, located in c:\cygwin\bin. >> I forgot to mention: >> VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV >>>Problem reports: http://cygwin.com/problems.html >> >> You should be able to run the cygcheck program from a windows command >> shell without causing the kind of problem that you're reporting. >> Running the cygcheck program ("cygcheck -s -v -r > cygcheck.out") results in an empty (zero byte) file. No output. Any other ideas or suggestions? thanks, John -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple