This is the mail archive of the 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]

RE: Proper way to start dos/win executables?

Cygwin knows about the .cmd and .bat extensions and
invokes cmd.exe by default when you type something

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.


-----Original Message-----
From: Downey, Brian []
Sent: Tuesday, August 28, 2001 7:18 AM
To: ''
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:
Bug reporting:

Unsubscribe info:
Bug reporting:

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