This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Proper way to start dos/win executables?
- To: "'Downey, Brian'" <Brian_Downey at quickenloans dot com>, "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Subject: RE: Proper way to start dos/win executables?
- From: Troy Noble <troy dot noble at channelpoint dot com>
- Date: Tue, 28 Aug 2001 08:28:41 -0600
Cygwin knows about the .cmd and .bat extensions and
invokes cmd.exe by default when you type something
like
bash% $SCRIPT_DIR/start1.cmd
So you shouldn't need the leading exec.
If that doesn't work, try explicitly starting cmd.exe
using the start.exe that comes with NT/Win2K such as:
bash% cmd.exe /C `cygpath -wa $SCRIPT_DIR/start1.cmd` arg1 arg2 ...
but I don't think that'll be necessary "under normal circumstances".
the cygpath converts the $SCRIPT_DIR to a form that
cmd.exe will understand when it tries to open start1.cmd.
Troy
-----Original Message-----
From: Downey, Brian [mailto:Brian_Downey@quickenloans.com]
Sent: Tuesday, August 28, 2001 7:18 AM
To: 'cygwin@cygwin.com'
Subject: Proper way to start dos/win executables?
Hi everyone..
I have a question regarding the starting of a windows executable from within
a cygwin shell script.
The problem I'm having is allowing the passing of modifiers to the original
.exe without using a windows .cmd or .bat file. For example I need to start
a java runtime with these modifiers:
java -Xms64m -Xmx64m ObUpdateGUI "ObUpdateGUI"
Currently, the command resides in a windows .cmd file. When I attempt to
call this from my script using this:
exec $SCRIPT_DIR/start1.cmd &
It simply runs java from within the cygwin shell and halts the processing of
the script. I tested out calling "notepad.exe" directly without a .cmd file
and this seems to work. Is there a better way to do this other than using
.cmd files? Would it also prevent the script from halting upon execution?
Thanks in advance!
Brian Downey
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/