This posting is to summarize the problem that Steffen experienced and the solution. The LabWindows/CVI user DLL makes calls into DAQ. The DAQ calls depend on some MAX DLLs. The DLL being loaded was MXSOUT.DLL which depends on MXSXPORT.DLL. When DAQ attempts to load MXSOUT.DLL, it first sets the current working directory for the application, asks NI PAL to load the DLL, and then resets the current working directory back. When NI PAL loads the DLL, it uses LoadLibrary and not LoadLibraryEx. LoadLibraryEx has an option that specifies to look for dependent DLLs in the directory of the loaded DLL. Since this is not the case, LoadLibrary finds the dependent DLLs because the current directory was temporarily set to the MAX directory.
TestStand also sets the current directory when it loads code modules. The this case, a second execution thread had changed the current directory after DAQ set it and before loading MXSOUT.DLL, so the its dependent DLLs were not found. A workaround to prevent this load error is to add C:\Program Files\National Instruments\MAX to the system PATH variable.
Scott Richardson
