X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 1 Sep 2008 12:01:18 +0100 From: "Robert McKay" To: cygwin@cygwin.com Subject: Running 64bit processes from 32bit Cygwin In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 1903a209533e5454 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hi all, I have a problem with running powershell scripts from within cygwin.. basically no matter what I do it always ends up running the powershell process as 32bit when invoked from within Cygwin. This normally wouldn't make a difference, but I need to use a powershell extension that only exists for 64bit powershell. There isn't really anything powershell specific about this question though; Can anyone tell me for sure that it's impossible to run a 64bit windows process from 32bit Cygwin? Or rather.. is it possible to spawn a 64bit process from Cygwin and have it not be trapped inside WoW64 emulation? It seems as though once you're inside WOW64, you can't readily escape from it? I wonder if it would be possible to ask the explorer process to spawn something for you (possibly via a com message?) rather than using WinExec(). If so a utility to facilitate such process spawning would be a very useful addition to Cygwin. Rob. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/