Changes
→Starting wpkg using cygrunsrv.exe
You can get cygwin1.dll from any Cygwin mirror, it's located in cygwin/release/cygwin (for example, cygwin-1.5.19-4.tar.bz2).<br>
cygrunsrv is located in cygwin/release/cygrunsrv (for example, cygrunsrv-1.16-1.tar.bz2).
Here's one working example:
<pre>
cygrunsrv -I wpkg -p '/cygdrive/c/WINDOWS/system32/cscript.exe' -a'c:\wpkg\wpkg\wpkg.js /quiet /synchronize' -c '/home/Administrator/wpkg/wpkg'
cygrunsrv -S wpkg
</pre>
Those arguments are:
; -I [name] : Install a service named [name]. In this example, we're calling it wpkg.
; -p [/path/to/executable] : Path to the command to run -- in this case, cscript.
; -a [arguments to executable] : Arguments for the executable -- in this case, the path to wpkg.js and how we want it to run.
; -c [directory] : Go to this directory before starting the program.
There are a few things to note:
* The <code>-p</code> argument gives the path to cscript in the format Cygwin uses to get to Windows drives. In this format, the C: drive can be reached at <code>/cygdrive/c</code>, the D: drive can be reached at <code>/cygdrive/d</code>, and so on. Also, unlike Windows, Cygwin is case-sensitive -- so <code>/cygdrive/c/Windows</code> is ''not'' the same as <code>cygdrive/c/WINDOWS</code>.
* The <code>-a</code> argument is given in Windows format. Also, it is ''very'' specific to the (stupid) way I have wpkg set up on this machine.
* I'm unsure if the <code>-c</code> argument is necessary, but it works for me. It's given in Cygwin/Unix format, and is again very specific to the stupid way I have things set up. I'm unsure what to put here if all you're doing is copying around the Cygwin DLL.
== Starting wpkg using srvany to create a system service (advanced) ==