From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: can't access /cygdrive/c/Windows/Sysnative ?
Date: Wed, 21 Dec 2016 18:12:00 -0000 [thread overview]
Message-ID: <4a128e20-666e-5366-d432-456c67270d57@SystematicSw.ab.ca> (raw)
In-Reply-To: <20161221170917.GA16104@ingber.com>
On 2016-12-21 10:09, Lester Ingber wrote:
> In some older cygwin posts, I see cygwin use of Sysnative for 64-bit
> access to System32 files. In my Cygwin64 installation on my Thinkpad
> Windows 10 x64 Pro PC I cannot see Sysnative at all under cygwin.
> However, for example, using windows opened by Malwarebytes I can
> access this directory just fine.
> How can I see/access Sysnative under cygwin?
Run Cygwin 32 - there only used to be 32 bit Cygwin and old posts
assume that environment.
Native 64 bit directories are:
C:\Windows\System32 (64 bit) C:\Windows\SysWOW64 (32 bit)
under 32 bit redirection these become:
C:\Windows\SysNative (64 bit) C:\Windows\System32 (32 bit)
to support poorly written programs that don't use the proper API call
to get the directory name; see:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa384187(v=vs.85).aspx
for full list of paths redirected from 32 bit code on a 64 bit system.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
next prev parent reply other threads:[~2016-12-21 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 17:09 Lester Ingber
2016-12-21 18:12 ` Brian Inglis [this message]
2016-12-21 20:16 ` Lester Ingber
2016-12-22 1:07 ` Mark Geisert
2016-12-22 12:51 ` Andrey Repin
2016-12-22 18:39 ` Brian Inglis
2016-12-22 19:22 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a128e20-666e-5366-d432-456c67270d57@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).