DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 9382439B6812
MIME-Version: 1.0
References: <20210421120457.cd5b6e966288aa62eee1a013@nifty.ne.jp>
 <YH/uPeBvTfxKdRxQ@calimero.vinschen.de>
 <CANV9t=Qv2OdnmADgXpk=oVfdchSB+n67tWUruvbiqOrtzh4=Ww@mail.gmail.com>
 <YIBXLtdkPnfcfimZ@calimero.vinschen.de>
 <CANV9t=RZ9Z3ZoLPQWtTSTvphp10wy3QAYivo+AZo9-2pJ6m+ZQ@mail.gmail.com>
 <YIB82EMHEMc0ziW+@calimero.vinschen.de>
In-Reply-To: <YIB82EMHEMc0ziW+@calimero.vinschen.de>
From: Bill Stewart <bstewart@iname.com>
Date: Wed, 21 Apr 2021 15:03:50 -0600
Message-ID: <CANV9t=Q=9R49kOW-kVZg5=Mz12Gzzhzh2jxF5E4ZT2DnUQw3KA@mail.gmail.com>
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the
 commit 456c3a46
To: cygwin@cygwin.com
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

On Wed, Apr 21, 2021 at 1:28 PM Corinna Vinschen wrote:

This is not the right place to discuss this in detail, but to me, a
> straightforward and sensible approach would have been to give the 64
> bit system dir another name right from the start:
>
>   C:\Windows\System64
>

That would not have worked for backward compatibility reasons.

https://docs.microsoft.com/en-us/previous-versions/technet-magazine/ff955767(v=msdn.10)

The "32" suffix in System32 can be seen as just a label and doesn't
represent the "bitness" of the files within. (As Raymond says, "you should
think of System32 as the somewhat strange name for the 'system DLLs in the
same bitness as the application [in this case, OS] that’s running'
directory").

(You're right - not really the right place to discuss - was just responding
to the evaluative labeling.)

Bill

-- 
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