This is the mail archive of the
mailing list for the Cygwin project.
Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail?
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: "Houder" <houder at xs4all dot nl>, cygwin at cygwin dot com
- Date: Mon, 12 May 2014 16:38:15 +0400
- Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail?
- Authentication-results: sourceware.org; auth=none
- References: <849f1f5420ebf77d7a591d6c9b6bfa4b dot squirrel at webmail dot xs4all dot nl> <536E339A dot 6030200 at breisch dot org> <6f9d939cc604437def11828435a67f96 dot squirrel at webmail dot xs4all dot nl>
- Reply-to: cygwin at cygwin dot com
> 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.
> 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?
> 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?
Andrey Repin (firstname.lastname@example.org) 12.05.2014, <16:34>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple