From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail?
Date: Mon, 12 May 2014 17:13:00 -0000 [thread overview]
Message-ID: <ec5e4625f2bd19a7cc13bf9374bd30f3.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <635595705.20140512163815@yandex.ru>
Hi Andrey,
>> Another issue you might run into ...
>
>> I was surprised to find, that 32-bits bash reported /drv/c/Windows/regedit.exe as a different file,
>> compared to what 64-bits bash reported.
>
> No surprise here. To reach 64-bit regedit (and other utilities) from 32-bit
> application, you have to address it through %SystemRoot%\Sysnative path.
Hold on. I wrote '/drv/c/Windows/regedit.exe' (irrespective of its bit-ness).
BUT! See bottom of this message.
>
>> Note: 32-bits cmd and 64-bits cmd report c:/Windows/regedit.exe as the SAME
>> file. Which, of course, made me wonder ...
>
> I wonder, how do you check that?
C:\Users\Henri> dir /tc /4 c:\Windows\regedit.exe # using 32-bits cmd
Volume in drive C has no label.
Volume Serial Number is 12F0-A5C0
Directory of c:\Windows
14-07-2009 01:27 427.008 regedit.exe
C:\Users\Henri> dir /tc /4 c:\Windows\regedit.exe # using 64-bits cmd
Volume in drive C has no label.
Volume Serial Number is 12F0-A5C0
Directory of c:\Windows
14-07-2009 01:27 427.008 regedit.exe
Size and date/time of creation are the same.
>> Searching the internet again, I got the understanding, that there has been
>> been a time in which a request for c:/Windows/regedit.exe was redirected to
>> c:/Windows/SysWOW64/regedit.exe (in case of a 32-bits application).
>
>> As far as I can tell, this redirection no longer applies (meaning, as far as
>> can tell, MS changed its mind here).
>
> How did you found that?
For instance, here
http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187%28v=vs.85%29.aspx
it said
Access to %windir%\regedit.exe is redirected to %windir%\SysWOW64\regedit.exe (in case of
32-bits application)
The current situation on my W7 does NOT agree with the above statement.
Henri
-----
Here it shows that 32-bits Cygwin "sees" (i.c. ls, stat) a different file at /drv/c/Windows ...
Using my 32-bits Cygwin installation (DOS-box, bash) at e:/Cygwin
@@ ls -l /drv/c/Windows/regedit
-rwxrwx---+ 2 TrustedInstaller TrustedInstaller 398336 Jul 14 2009 /drv/c/Windows/regedit
@@ stat /drv/c/Windows/regedit
File: `/drv/c/Windows/regedit'
Size: 398336 Blocks: 392 IO Block: 65536 regular file
Device: 12f0a5c0h/317760960d Inode: 281474976748756 Links: 2
Access: (0770/-rwxrwx---) Uid: (4294967294/TrustedInstaller) Gid: (4294967294/TrustedInstaller)
Access: 2009-07-14 01:17:08.803392200 +0200
Modify: 2009-07-14 03:14:30.457000000 +0200
Change: 2014-05-11 18:34:40.326326000 +0200
Birth: 2009-07-14 01:17:08.803392200 +0200
Using my 64-bits Cygwin installation (DOS-box, bash) at e:/Cygwin64:
64-@@ ls -l /drv/c/Windows/regedit
-rwxrwx---+ 2 TrustedInstaller TrustedInstaller 427008 Jul 14 2009 /drv/c/Windows/regedit
64-@@ stat /drv/c/Windows/regedit
File: `/drv/c/Windows/regedit'
Size: 427008 Blocks: 420 IO Block: 65536 regular file
Device: 12f0a5c0h/317760960d Inode: 281474976726615 Links: 2
Access: (0770/-rwxrwx---) Uid: (4294967294/TrustedInstaller) Gid: (4294967294/TrustedInstaller)
Access: 2009-07-14 01:27:10.125698800 +0200
Modify: 2009-07-14 03:39:29.639000000 +0200
Change: 2014-05-11 18:35:26.892407800 +0200
Birth: 2009-07-14 01:27:10.125698800 +0200
Note:
- 32-bits Cygwin invokes 64-bits regedit in case of /drv/c/Windows/regedit
(yes, different from the one it "sees" (i.c. ls, stat) !!!!!
- 32-bits Cygwin invokes 32-bits regedit in case of /drv/c/Windows/SysWOW64/regedit
- in case of /drv/c/Windows/System32/regedit: dito
- /drv/c/Windows/SysNative/regedit: does NOT exist!
(the 64-bits version only lives in c:/Windows)
=====
--
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:[~2014-05-12 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:42 Houder
2014-05-10 14:11 ` Chris J. Breisch
2014-05-12 12:50 ` Houder
2014-05-12 12:51 ` Andrey Repin
2014-05-12 17:13 ` Houder [this message]
2014-05-12 13:01 ` Corinna Vinschen
2014-05-12 13:15 ` Shaddy Baddah
2014-05-12 13:23 ` Corinna Vinschen
2014-05-12 18:47 ` Houder
2014-05-12 17:31 ` Houder
2014-05-13 15:10 ` Houder
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=ec5e4625f2bd19a7cc13bf9374bd30f3.squirrel@webmail.xs4all.nl \
--to=houder@xs4all.nl \
--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).