On Monday 27 December 2004 19:07, Vladimir Levijev wrote: Hi,
> > 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-- Sorry, corrections: - chdir to path where bash.exe is (E:\cygwin\bin?) - /usr/local/bin/xapp.py instead of ./xapp.py -- [EMAIL PROTECTED] -- 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/