X-Spam-Check-By: sourceware.org Date: Wed, 22 Nov 2006 09:29:34 -0500 From: Scott Hepler To: cygwin AT cygwin DOT com Subject: Re: DLL problems on fresh install Message-ID: <20061122142934.GA6442@tiny.vermontel.net> References: <20061122083831 DOT GU4035 AT tiny DOT vermontel DOT net> <20061122130711 DOT GG8333 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061122130711.GG8333@calimero.vinschen.de> User-Agent: Mutt/1.5.9i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, Nov 22, 2006 at 02:07:11PM +0100, Corinna Vinschen wrote: > On Nov 22 03:38, Scott Hepler wrote: > > Hi folks: > > > > Sorry to bring what is apparently a FAQ, but I'm stuck. > > > > I had an existing Cygwin install (1.5.?) which I upgraded to 1.5.21-1 via > > setup.exe. I started getting that infamous error: > > > > -snip- > > 7 [main] ? (336) C:\cygwin\bin\bash.exe *** fatal error - system shared > > memory version mismatch detected - 0x75BE0074/0x2D1E009C. > > -snip- > > [...] > > Can anybody help me stop this wandering, please? > > Since you said you searched the machine for another cygwin1.dll, but the > above message is quite clear, I'm wondering if you have some 3PP software > on your machine which installed a cygwin1.dll under another name > together with their 3PP stuff (obfuscating rulez). Did you really search > everywhere? Even in C:\Windows? Ah, good point. I used Windows' Search tool to look, and one never knows where that looks. So, I searched the PATH manually, and found nothing obvious. Do you have any good tips for finding renamed .dll's? A size range perhaps? Or an alternative search tool other than 'find', since that doesn't work right now, obviously :( The problem with this theory is that it was working fine just before the upgrade, and not working just after. Is it possible that this message is a red herring, hiding some other problem? Thanks for the help -- I have hope again! -s. -- Scott Hepler System Administration and Security Web Development -- 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/