X-Spam-Check-By: sourceware.org Date: Mon, 4 Dec 2006 19:30:56 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Vista x64 STARTUPINFO Issue Message-ID: <20061204183056.GE9829@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <45746641 DOT 30603 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45746641.30603@cygwin.com> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Dec 4 13:17, Larry Hall (Cygwin) wrote: > McArdle, Christian wrote: > >As I understand it, cygwin doesn't yet work on Vista x64. Does anyone know > >if a fix is under development? > > > >>From what I have read, it is related to Windows no longer using the > >>STARTUPINFO reserved parameters to pass information onto the new process. > >>I have no idea exactly how cygwin does this, but I've done similar things > >>in a more portable fashion using named pipes (named after a newly created > >>GUID), so whether that would be a solution or not, I don't know... > > From the above, it's seems like you've read this thread but if not, this is > the current state of affairs: > > > > If you have some ideas that you'd like to propose, feel free. :-) Looks like I have solved this issue today, but I'm still testing. Stay tuned. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/