Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: Vladimir Levijev To: cygwin AT cygwin DOT com Subject: Re: run.exe fails to run my application Date: Mon, 27 Dec 2004 19:07:18 +0200 User-Agent: KMail/1.7 References: <20041227115638 DOT 14ddbba7 DOT gry AT ll DOT mit DOT edu> In-Reply-To: <20041227115638.14ddbba7.gry@ll.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412271907.19055.dimir@core.ee> On Monday 27 December 2004 18:56, george young wrote: Hi, > [cygwin X-startup-scripts-1.0.10-2] > > I can not get run.exe to run my application. The app runs ok directly > from the DOS prompt(with the annoying dos box). It runs from the cygwin > prompt. But put 'run' in front of the command and I get an error dialog > popup: > > Run.exe > Error: could not start E:\cygwin\usr\local\bin\xapp.py > > "Run" fails the same invoked from either the cygwin or dos prompt. > > Run works fine with xterm. > > The app's directory is in the system path. Same failure happens > whether invoked with full path or just the app name. (assoc and ftype > have been twiddled to get the python script xapp.py run by > /usr/bin/python2.4) > > When I do "run xapp.py" the error message contains the full pathname, > so it is *finding* the executable. The error message is different if > I give it a non-existant file name. > > What could cause this? How can I debug this problem? > > Does run keep a cache of executable names/paths somewhere that I might > need to flush? > > -- George How about making batch file, in a Cygwin.exe style, containing: --Start batch file-- @echo off E: chdir E:\cygwin\usr\local\bin start /min bash --login -c "./xapp.py" --End batch file-- -- [vl AT dimir]# -- 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/