X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=hc0T8KUID08+Hqey
	kIPAoIWT62rRm/2jgspnvm2206xP9gZDwUysDtgJvwAVQgdHcn5aSSRfMST+6qMu
	/M/MtIhGqiiI/c7wiHNE9GwlcULMxVHjHB6OcsXdvmTK1DYg3Iy0qwuFe5KqFM34
	MalJsN/FRyO4VHkUaJU/cetJIvA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=ZxFbFoOq077DLr3vqbJRWd
	khxE4=; b=OA0czVz4xIkRPw3ruThsIct2qg5fafa3GvTFbZSu+CXRAvYJpG9zNZ
	mtylYabKDNcVkLOgqOuqZKaB3Er8KAaEBn7mlNPx+0OwOIauxU1Fh3Q3CO/ytsqL
	FkYDZrlEC/l0+SbdjuN1efq3PIjfyXTpAR9WNe7bs6p5DjQZ/DoB0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_80,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtpback.ht-systems.ru
Date: Mon, 12 May 2014 16:38:15 +0400
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <635595705.20140512163815@yandex.ru>
To: "Houder" <houder AT xs4all DOT nl>, cygwin AT cygwin DOT com
Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the   invocation of regedit (from bash) to fail?
In-Reply-To: <6f9d939cc604437def11828435a67f96.squirrel@webmail.xs4all.nl>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Houder!

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


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 12.05.2014, <16:34>

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