From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61026 invoked by alias); 27 Feb 2019 05:57:20 -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 61016 invoked by uid 89); 27 Feb 2019 05:57:20 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=nights, leader, H*F:D*nl, person X-HELO: lb3-smtp-cloud9.xs4all.net Received: from lb3-smtp-cloud9.xs4all.net (HELO lb3-smtp-cloud9.xs4all.net) (194.109.24.30) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Feb 2019 05:57:18 +0000 Received: from tmp.vlRXfMBDiE ([83.162.234.136]) by smtp-cloud9.xs4all.net with ESMTPSA id ysDQg5x3YI8AWysDRgeofI; Wed, 27 Feb 2019 06:57:15 +0100 Date: Wed, 27 Feb 2019 06:55:00 -0000 Message-ID: From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64 References: <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> <5c75e50c.1c69fb81.2a448.90cf@mx.google.com> <302c5d5e-be0d-74f9-9f9e-4b359683d092@yahoo.com> <31aa038e-4130-435a-092e-4f0e24f1f67b@yahoo.com> In-Reply-to: <31aa038e-4130-435a-092e-4f0e24f1f67b@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-SW-Source: 2019-02/txt/msg00472.txt.bz2 On Tue, 26 Feb 2019 18:01:27, Jerry Baker via cygwin" wrote: > Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7 > system. The only difference I can think of is that the i7 system is a > member of a domain. (first I would suggest a good night's sleep :-) If you really believe it is the cygwin1.dll that causes the failure, and you also believe that your system fails because it is in a domain ... Why not test (using bisect) the cygwin1.dll 's at cygwin.com/snapshots? (do not the ones between 20190126 and 20190130, because, as far as I can remember, these are not OK). Start at the beginning of 2019, I would suggest ... Use a fresh minimal! installation (download from a mirror, not from your local repo). Minimize your path to "Cygwin-only" ... .. etc. (you are an experienced person, you should know what to do!). If you find the culprit, tell us. The project leader of Cygwin will be much interested!. Henri -- 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