I built a NIDAQ app using Visual C++ 6.0 as a WinNT/Win2K service. The service can be manually started and stopped on all test systems without a problem. When auto-starting the service, the results are inconsistent. On some machines it starts, on others it fails. When it fails, the error code indicates it failed to load a DLL. By process of elimination, it appears that the NIDAQ DLL's are the problem (i.e., the service auto-starts when the NIDAQ code is commented out). This problem happens with NIDAQ 6.9.2 but not NIDAQ 6.7. Are there some service dependencies that need to be specified?