From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124921 invoked by alias); 12 Nov 2015 04:04:33 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 124905 invoked by uid 89); 12 Nov 2015 04:04:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 12 Nov 2015 04:04:31 +0000 Received: from [192.168.178.105] ([84.142.144.78]) by mrelayeu.kundenserver.de (mreue005) with ESMTPSA (Nemesis) id 0LmgTP-1aWsoq0w2V-00aFng for ; Thu, 12 Nov 2015 05:04:27 +0100 Subject: Re: Cygwin DLL V2.3.0 on XP 64-bit professional not working at all To: cygwin@cygwin.com References: <5643EAE9.8040803@georg-rehfeld.de> <20151112024759.27BCC070.helmut.karlowski@ish.de> From: Georg Rehfeld Message-ID: <56440FBB.4040509@georg-rehfeld.de> Date: Thu, 12 Nov 2015 04:04:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151112024759.27BCC070.helmut.karlowski@ish.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:+k0nGmcV/YE=:pvqWTiARIv3bibuSSZHD10 fSMMgB+cs/rDntogMFEYjE4oga4egck6Dpouz4hHWbU3wOjM2PcuetY68eptW0f+Lk/eBZ4lp rsCsNSwxc7QjqewMSFyXfNA1IV/5NE3NM8LB7Y0EsZrFAREtDiKvi70ov1WHhOq4CiHlJojs2 7u/jiZqZWOjH38DKWS2JRpi2GwIm1MBZ645nHuLGiQ0zBHsNpBrCUSoN6/ZvWJ6Jm7v/7LkIN giACoBzRTIxsYLhaZuXAlbmM1RjhslECBmO7mW0Ssz6vKxbVCPWnq3lTRkjFvcjFvfUCA8GC9 dA+Gx93OH7Bq7+wpIrscZvJdilZ7h5ULABGQKEvQ1npcgsbRx2u/yxrLGEsZBnHvWJArvDE9e M+SEX7oKU9VhTY4HtlqDJbUI/NjbDXyEZKnkSUr4BrwZxr7sDgeSr4/fK0FZB6kahZpVFNSb5 P34gS1yD95d4fb+hE1OV0yVYAfDEitYexto1PBPhIdTb+BKbsAl+KgHJnxYuDqNCABhtyitku 1boO7kgXuYqOl5SMUmafaDTxgbN9P35wLDj3WZQu6IDLH/TPJzYX6hZeLkcTIvMG2DABfZrTV 56/GRMqTgGwNZ/n2SibOxAKwrz4ECLdsFCXgm0S5zw6V6Ub3Z3geRD4QSSCHUgxjlVvCW6515 ab8ValhtLqo3HvmPaqVZHUABnZ14XG2c/Vta8dqcvPXH0Br5ibIuYaEuc+hTSx71pNCBWqZnG LkllT3N1KzUTEMmo X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00191.txt.bz2 ----- >> Finally I restored the complete cygwin folder from a backup. Now Cygwin >> works again as a charm. I conclude, that my system itself is OK and >> something or the other might be broken in the current Cygwin version? > > I once had this fork-error after a cygwin-update on windows 10. I > rebooted windows and all worked normal. Maybe that's what happened to > you also? Thanks for the suggestion, but missing reboots are not the problem for sure. As indicated I tried the base installs several times, always alternating between 32bit and 64bit, always using a different mirror and rebooted often (~10 times in the last day). Missing reboots also should not cause the post install errors on the 32bit version IMHO. Side note, if you wonder: XP 64 never got a service pack 3, only SP2. And my system IS up to the last MS update. Might be, I finally should update to W7 64, if XP 64 isn't supported (any longer) by Cygwin. Best regards, Georg -- ___ ___ | + | |__ Georg Rehfeld Woltmanstr. 12 20097 Hamburg |_|_\ |___ rehfeld@georg-rehfeld.de +49 (40) 23 53 27 10 -- 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