| John Seal 2006-03-28, 7:04 pm |
| Hello.
We have a Tcl server daemon (no GUI) that receives ::comm messages on a
well-known port and forwards data to a 3rd-party application running on
the same WinXP box. It runs fine for a logged-in user, but we need it
to start at boot time and be running even when no user is logged in.
I'm aware that we could actually make it a Windows service, but I'm
interested in finding out if there are issues with running tclsh during
WinXP startup (and maybe learn something more about Tcl or WinXP).
One of our developers created some kind of hook in something called MMC,
which I'm not familiar with. MMC wouldn't launch our .tcl file
directly, so he wrote a 2-liner javascript to launch the .tcl file. The
javascript works when logged in, but not at startup. We are certain
it's running at startup, because if we change the launch command to
something erroneous, we get the dialog box during startup.
The server creates a log file when it runs, and that log file isn't
being created. Since launching the javascript launches the server when
we're logged in, and we're certain the javascript is running at startup,
then something must be preventing the server from running during
startup. We have checked the sequence, and the javascript *is* being
run *after* networking has been established.
Any ideas?
The developer suggested making the server a starpack. I think that
would work, but I want to know what's going on first.
|