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:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=MPS35B
	Ni0MuukkbBT3X6ByFkcYOTiX2iOVZ/g07acOb7YnPMBDfp7ni2+tZaWGZk8SxnU8
	qQsWv7S1KrQ03z6/Iwca28s0aZjHVcr5vkgSyvVqrXbd4h9gI1P9zJvfvNrGfsJj
	z9vUa2dYXuEtto9i0CJOg53pkFI2o9C8Pjkws=
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:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=O2li+gPMB2S0
	dDlMJ0hYRkqomVQ=; b=ZEzmIWeJyxZjmoNrXT5lsw5uwjsiT0Ubw3wXLYqVrM6N
	XS26z8FFkiHEGQ8f+SizQ9SGNX3WGTqjXSOHfIES6XTZAofOe6L3uzVr5VBe2OkG
	XleVrOq2PUktXjBFhf55AW3ljtnsLwt9n5bsTOZx4OhOVx0H6p8NOvVwh5OZdDw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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-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
Date:	Wed, 27 Feb 2019 06:57:15 +0100
Message-ID:	<c978171577607c8e7e66dc708735d888@smtp-cloud9.xs4all.net>
From:	Houder <houder AT xs4all DOT nl>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
References:	<35062835-c3cd-799e-d13a-16f954db2a19 AT yahoo DOT com> <5c75e50c DOT 1c69fb81 DOT 2a448 DOT 90cf AT mx DOT google DOT com> <302c5d5e-be0d-74f9-9f9e-4b359683d092 AT yahoo DOT com> <31aa038e-4130-435a-092e-4f0e24f1f67b AT yahoo DOT com>
In-Reply-to:	<31aa038e-4130-435a-092e-4f0e24f1f67b@yahoo.com>
User-Agent:	mua.awk 0.99

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

- Raw text -