Re: [Wrapper-user] Fwd: RE: No args wrapper startup [jredman@ergotech.com]

[Leif M. <le...@ta...>]

Jim,

> Beyond the obvious observation that batch files are ugly, we have at 
> least on sitution where a batch file will not work.  The OPC standard, 
> which we support, mandates that one of the registry keys associated 
> with an application is an executable, not a batch file.
>
> In our case, it is the end users choice whether to install a service 
> or not.  For some customers the applications will not run as a 
> service, the application will grab the executable from the registry 
> and run it and check that the application is still alive.  Others want 
> a service.   Some want a real user interface, etc. etc. Hence the 
> attraction of the wrapper, it does all these things.

When the wrapper is installed as an NT service, it no longer uses the 
batch file.  The Wrapper
installs an entry in the registry which points directly to the 
Wrapper.exe.  The full entry looks
like this:
 c:\fullpath\bin\Wrapper.exe -s ..\conf\wrapper.conf
It sounds to me like if your tool is pulling the exe name out of the 
registry to run in console
mode, you should be able to do something similar by specifying the 
following in the registry
 c:\fullpath\bin\Wrapper.exe -c ..\conf\wrapper.conf

Cheers,
Leif