|
From: Glen <gle...@mo...> - 2005-02-15 15:16:33
|
The --x options are simply to delineate them from normal application parms... So the customzied wrapper that I am using can still be used in the standard way... Jim Redman wrote: > Glen, > > Glen Marchesani wrote: > >> * An altered wrapperw.exe that runs as a console application and >> looks for a .conf file in the same directory with the same base >> name as the wrapperw.exe. So if the wrapperw.exe is renamed to >> myprog.exe it will look for myprog.conf. Also any command line >> arguments are passed directly into the java app. This allows one >> to use myprog.exe as a windows explorer file handler with minimum >> effort. If you use the wrapper.exe as is you would have to go >> into the registry and add the appropriate command line parms (-c >> myprog.conf). I implemented this as a completely new executable >> since all the options (-c -t -p -i -r -?) are still there just as >> (--c --t --p --i --r --?) > > > I've just implemented the same feature, by just recreating the argv[] > if argc < 3. I'm not sure what the significance of the --x options > are. In this case, our interest is in being able to run java apps a > .exe's and get away from bat files. We have some directories with > multiple apps. > > I'd be happy to provide the code if it's of interest. > > Jim > |