Hello all,
we have a decades-old legacy VC++ application, running perfectly under any Windows version up to 7 with the traditional ni-DAQ drivers, including version 7.5 (nidaq32.dll is of size 2818048 bytes), while the DLL is implicitly loaded at start of the program.
Now we have been porting this C++ project under Windows 7 to using both the new ni-DAQmx drivers and the traditional DAQ. While explicitly LoadLibrary( 'nicaiu.dll') works fine and our code successfully uses the new driver, the traditional driver can't be loaded in the same way.
The call to LoadLibrary( 'nidaq32.dll') returns a valid library handle, but at the same time GetLastError() returns 2: ERROR_FILE_NOT_FOUND (although, of course, C:\Windows\System32\nidaq32.dll exists). Afterwards, subsequent calls to GetProcAddress() return null pointers and another GetLastError() says 126: ERROR_MOD_NOT_FOUND.
Using the program Dependency Walker, version 2.2.6000 to profile the DLL usage of our application reveals that one of the DLL dependencies, 'nipxi5600u.dll', could not be met. When starting our old program with implicitly loading 'nidaq32.dll', this miss is not an error, because 'nipxi5600u.dll' is never used (We don't have that hardware, PXI5600, anyway).
But when explicitly calling LoadLibrary( 'nidaq32.dll'), this miss gives a fatal error. Our program recovers with the traditional DAQ not loaded, but is of course not able to perform anything afterward.
Why is this dependency 'nipxi5600u.dll' incorporated in 'nidaq32.dll', while not distributed together with the TDAQ driver? Of all that many NI devices, this looks like the only one mentioned in the dependency list of 'nidaq32.dll', although one does not own that device and that particular driver is not distributed along.
Is it an error that 'nidaq32.dll' expects this 'nipxi5600u.dll'? Is there any viable workaround?
With best regards,
C. Spanheimer
