Hi
I found the following related to NT services, it's quite old and might differ a bit from the current way a windows service work but I suspect this might be related to your problem:
This transformation is actually a two-step process, the first of which is the
actual conversion of your program, which should be in the form of an executable
at this point, into an NT service. This is usually done through the use of
another program (SRVNY.EXE) that is a part of the NT resources kit.
The
second, more difficult step involves ensuring that your newly-created NT service
will load after the NI-DAQ kernel service is loaded. This can be accomplished by
making sure that the libraries from the DLL are loaded after the NI-DAQ kernel
is loaded.
The most common error encountered in this process is a "cannot
open DLL" error. Two things that you may consider in an attempt to avoid
encountering this error:
1. Load NDAQ32.DLL dynamically. By using a load
library function following a delay, you will give some time for the NI-DAQ
service to load.
2. Modify your service key in the Windows NT registry and
make it dependent upon the NIDAQ32k service. By doing this, you will force it to
wait long enough for the NI-DAQ kernel to be loaded.
In your registry,
edit the following key: HKEY_LOCAL_MACHINE » SYSTEM » CurrentControlSet »
Services. The NT service that you just created should be listed here, along with
Nidaq32k service. In order to make your service dependent upon Nidaq32k, add
this line to your service key: "DependOnService: REG_MULTI_SZ: Nidaq32k". This
should make your service wait for NI-DAQ.
