X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org C64753AAB002
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1618999786;
	bh=uOHt2UHOUCayauMBFKoqT91+jFGh1Ssp8Rn7LMm5siw=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=OL8qWbCZNkd67EE2YjegyBIyKSt+6gu/W/BTd8ypyQ8BE9aaLi50wsuFCo28KxCA6
	DxWBF1ZMcg02Fw4Tc/V9/ZIfoCefpkzpnGY5giet5uW8tEI/T3AkxtNibvlDJyiI+Q
	I0MotqlUvsgrIArItNVdcI90yL8lWKXj9HBkDASM=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org D7944388E818
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 13LA939T007397
X-Nifty-SrcIP:	[124.155.50.190]
Date:	Wed, 21 Apr 2021 19:09:12 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: Cannot access system32 directory from 32 bit cygwin after the
	commit 456c3a46
Message-Id:	<20210421190912.27bad7df23365d002f4729ab@nifty.ne.jp>
In-Reply-To:	<b9704ebe-dbb0-26cd-5d64-d7ab3c6faa2f@gmail.com>
References:	<20210421120457 DOT cd5b6e966288aa62eee1a013 AT nifty DOT ne DOT jp>
	<1801483573 DOT 20210421114900 AT yandex DOT ru>
	<b9704ebe-dbb0-26cd-5d64-d7ab3c6faa2f AT gmail DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-3.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A,
	RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Wed, 21 Apr 2021 11:56:50 +0200
Marco Atzeri wrote:
> On 21.04.2021 10:49, Andrey Repin wrote:
> > Greetings, Takashi Yano!
> > 
> >> I noticed the problem that /cygdrive/c/Windows/System32 directory
> >> can be no longer accessed from 32 bit cygwin (WOW64) after the
> >> commit:
> > 
> >> Reverting this commit resolves the issue.
> > 
> >> 64 bit cygwin does not seem to be affected. Could you please
> >> have a look?
> > 
> > How exactly it "can no longer be accessed" ? Is it opening WOW64 System32 or
> > not opening anything at all?
> > 
> > 
> 
> I see no problem on my side
> 
> $ uname -svr
> CYGWIN_NT-10.0-WOW 3.2.0(0.340/5/3) 2021-03-29 08:37
> 
> $ ls /cygdrive/c/Windows/System32 | wc -l
> 2925

Because your cygwin1.dll is older than the commit:
commit 456c3a46386f38887407603b2c64b7f63a4871c5
Author: Corinna Vinschen <corinna AT vinschen DOT de>
Date:   Mon Apr 19 14:49:14 2021 +0200

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -