can't access /cygdrive/c/Windows/Sysnative ?

can't access /cygdrive/c/Windows/Sysnative ?

[Lester Ingber]

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?


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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Brian Inglis]

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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Lester Ingber]

So, I guess that I should have seen that the Windows 10 Ubuntu bash.exe
is actually written as a 32 bit code (they didn't use the 64-bit code
as on my other true Ubuntu x64 platform?) from the PE32+ info?:

12:08:44pm ingber@lesterX1:/cygdrive/c/Windows/System32# ls -l bash.exe
-rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57
bash.exe
12:08:48pm ingber@lesterX1:/cygdrive/c/Windows/System32# file bash.exe
bash.exe: PE32+ executable (console) x86-64, for MS Windows

Thanks.


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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Mark Geisert]

Lester Ingber wrote:
> So, I guess that I should have seen that the Windows 10 Ubuntu bash.exe
> is actually written as a 32 bit code (they didn't use the 64-bit code
> as on my other true Ubuntu x64 platform?) from the PE32+ info?:
>
> 12:08:44pm ingber@lesterX1:/cygdrive/c/Windows/System32# ls -l bash.exe
> -rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57
> bash.exe
> 12:08:48pm ingber@lesterX1:/cygdrive/c/Windows/System32# file bash.exe
> bash.exe: PE32+ executable (console) x86-64, for MS Windows

No, that last line is saying x86-64 code (i.e. 64-bit) using PE32+ executable 
file format, like all 64-bit executables on 64-bit Cygwin (and 64-bit Windows 
for that matter).

..mark

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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Andrey Repin]

Greetings, Lester Ingber!

> So, I guess that I should have seen that the Windows 10 Ubuntu bash.exe
> is actually written as a 32 bit code (they didn't use the 64-bit code
> as on my other true Ubuntu x64 platform?)

No, UoW bash is completely different beast. Neiter Win32, nor Win32+.

> from the PE32+ info?:

> 12:08:44pm ingber@lesterX1:/cygdrive/c/Windows/System32# ls -l bash.exe
> -rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57
> bash.exe
> 12:08:48pm ingber@lesterX1:/cygdrive/c/Windows/System32# file bash.exe
> bash.exe: PE32+ executable (console) x86-64, for MS Windows


-- 
With best regards,
Andrey Repin
Thursday, December 22, 2016 15:35:55

Sorry for my terrible english...


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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Brian Inglis]

On 2016-12-21 13:16, Lester Ingber wrote:
> So, I guess that I should have seen that the Windows 10 Ubuntu
> bash.exe is actually written as a 32 bit code (they didn't use the
> 64-bit code as on my other true Ubuntu x64 platform?) from the PE32+
> info?:
> # ls -l bash.exe
> -rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57 bash.exe
> # file bash.exe
> bash.exe: PE32+ executable (console) x86-64, for MS Windows

which is exactly the same as Cygwin 64 bash:

$ file /bin/bash /proc/cygdrive/c/WINDOWS/system32/bash
/bin/bash:                              PE32+ executable (console) x86-64, for MS Windows
/proc/cygdrive/c/WINDOWS/system32/bash: PE32+ executable (console) x86-64, for MS Windows

as they are both Windows console exes: Windows "bash" is just the 
launcher for the console in which WSL/UoW/BfW runs -- trust MS to 
pick another wrong and confusing name to be "cute" -- like calling 
mintty "bash".

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

Re: can't access /cygdrive/c/Windows/Sysnative ?

[Brian Inglis]

On 2016-12-22 11:39, Brian Inglis wrote:
> On 2016-12-21 13:16, Lester Ingber wrote:
>> So, I guess that I should have seen that the Windows 10 Ubuntu 
>> bash.exe is actually written as a 32 bit code (they didn't use the 
>> 64-bit code as on my other true Ubuntu x64 platform?) from the
>> PE32+ info?:
>> # ls -l bash.exe
>> -rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57 bash.exe
>> # file bash.exe
>> bash.exe: PE32+ executable (console) x86-64, for MS Windows
> 
> which is exactly the same as Cygwin 64 bash:
> 
> $ file /bin/bash /proc/cygdrive/c/WINDOWS/system32/bash
> /bin/bash:                              PE32+ executable (console) x86-64, for MS Windows
> /proc/cygdrive/c/WINDOWS/system32/bash: PE32+ executable (console) x86-64, for MS Windows

The PE32 format is to allow execution from or by 32 bit world; the 
+ hints it contains 64 bit code, as does the arch x86-64.

From Cygwin 32 the 64 bit WSL/UoW/BfW "bash" launcher is not visible 
as the 64 bit system directories are not in the PATH:

$ file `which -a bash`
/usr/bin/bash: PE32 executable (console) Intel 80386, for MS Windows

> as they are both Windows console exes: Windows "bash" is just the 
> launcher for the console in which WSL/UoW/BfW runs -- trust MS to 
> pick another wrong and confusing name to be "cute" -- like calling 
> mintty "bash".

...forgot to add WSL/UoW/BfW bash, which is yet another 64 bit 
executable in ELF not PE32/+ format:

$ file `which -a bash`
/bin/bash: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=54967822da027467f21e65a1eac7576dec7dd821, stripped

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