X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
From: "Colin Harrison" <colin DOT harrison AT virgin DOT net>
To: <cygwin AT cygwin DOT com>
Subject: Re: [ANNOUNCEMENT] Updated: run-1.1.11-1
Date: Sun, 16 Aug 2009 16:58:37 +0100
Message-ID: <200908161558.n7GFwZ16011900@StraightRunning.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-Smarthost03-IP: [62.3.107.196]
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

Hi,

Chuck wrote:
> However, a lot of folks are used to using the run.exe tool

I for one.

I am getting a stderr/pipe problem with some CUI's ~line 398 in run.c
(1.1.11 run + your patch)
bForceUsingPipes = (os_version >= 0x0501); 
I made this = FALSE to fix for 2003 server..not tried on Windows 7.
I'm still testing (run built with MinGW) so this is maybe a clue or just a
bodge fix!
One failing CUI was plink (an ssh client from PuTTY).

I'll try and get back with more detail or a better fix!

Thanks,
Colin



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