X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; q=dns; s=default; b=mvJJJpkDOzPKRrUPTu9khFjufMrk9 iQ3ZSMd2dY1kv4TdHrOjc3wcaLTcZanccojuTpu8Jl4xW73bK9NsMUXnC7Z4IMab yTOktQkcMaBIxzk50bsZwHMespf4LK/3uZqHRayI90+o0IfH6em7xjsm1h/78Vys A7gq6F298opAg0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:date:message-id:subject:from:to :content-type; s=default; bh=7W286mCi/iw3u0PsviGdd2sh1lw=; b=k1v I2wH1LQtItEBzM48wzcGepnIsvHSmECwnIuOD8TZrGP1q6lKTCZZLjkp6T/OQJfB NwOl5RVoyRMijQw+gH3bHvkAZ6tp2wuhYJScWKDji+qhq5tXex5KO7D0KU4pzzzQ QeqptNKBS/k+l3h7qiQTM9IDWwqrPnkPJtiBOXIY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ob0-f179.google.com MIME-Version: 1.0 X-Received: by 10.60.40.39 with SMTP id u7mr918600oek.56.1397467435751; Mon, 14 Apr 2014 02:23:55 -0700 (PDT) Date: Mon, 14 Apr 2014 05:23:55 -0400 Message-ID: Subject: Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64) From: Mayank Patke To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 > I already wrote two mails on this to this list. I'm running Windows > 8.1 32 and 64 bit, but on my machines, the find_fast_cwd warning is > not printed, so the find_fast_cwd mechanism works as expected. Right, I saw those in the search results, although I didn't find any instances of someone uninstalling and having the same problem. Though, as you say, it's likely MSYS which is responsible on my system. > To get rid of this message, either I have to know how to reproduce it, > or somebody with this problem would have to debug a teeny little bit > of assembler code inside the Windows ntdll.dll file. I'm willing to debug, but I'd need someone to step me through this. > To be able to reproduce it, I would need somebody who can reproduce the > problem and being prepared to experiment a bit. It *seems* the problem > is introduced by some Windows update package which is not installed by > Windows Update by default. If we can find out which package this is, > I could debug this and get rid of the message. Still willing to help. I'm not sure what level of expertise you're looking for, but I'll do whatever I can to help get this resolved. ~ Mayank Patke -- 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