This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: .exe magic


Frank Fesevur wrote:
Larry Hall (Cygwin) wrote:
Here's a naive thought.  See if it makes any sense.  We have lots of
complicated logic to try to transparently handle ".exe" extensions.
We have ".exe" extensions because Windows 9x/Me requires it to execute
binaries.  For the upcoming Cygwin 1.7 release (date TBD), we're dropping
support for Windows 9x/Me.  Does it follow that complex ".exe" logic
could be dropped from 1.7 as a result?

We have quite some Scheduled Tasks that run bash scripts. The command line is like this:
C:\Cygwin\bin\bash.exe --login -c /home/administrator/MySQL-backup.sh


It starts in C:\Cygwin\bin and they work fine right now. I have just tested it (copied bash.exe to bash_test) and it does not seem to be a problem for Scheduled task.

BUT when I open a command prompt, go to c:\cygwin\bin and try start bash_test it does not find it. Just bash starts fine.

  C:\Cygwin\bin>bash
  bash-3.2$ exit

  C:\Cygwin\bin>bash_test
  bash_test wordt niet herkend als een interne
  of externe opdracht, programma of batchbestand.

Well, it will work if you set PATHEXT=%PATHEXT%:. but there might well be other consequences.
--
Michael Hoffman



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]