04-09-2020 09:06 AM
Hi everyone,
I have a frame grabber device installed that comes with a driver DLL which is placed in Windows/System32. There was no issue loading it with LabView 2013 and 2014 on Win 7. However, with LV2018 on Win 10 my VI would not find the driver anymore. Pathes in the VI seem to be correct as well as the Windows env variables, including the Windows/System32 folder.
If I create an executable out of the VI the same error shows up.
The interesting bit here is: I need to copy the driver DLL locally to the executable AND start the executable in Win 7/8 compatibility mode to eventually make it work. The executable is either LV.exe when using the VI or the compiled VI.exe.
Unfortunately, I cannot work in Windows compatibility mode due to other constraints.
I wonder what the Win compatibilty mode does? Does it load additional software and resolve potential dependency issues?
Did anyone experience anything similar and could provide some help here? LV support could not help on this, I called them already.
Thanks a lot in advance!
Solved! Go to Solution.
04-09-2020 09:57 AM
I wonder if this has anything to do with the new feature where LV 2018 RT will force all pre-LV 2018 executables to run in the LV 2018 RT? (Believe it or not, they list this as a FEATURE. Nevermind that there were recent changes that cause some compatibility issues.)
04-29-2020 07:34 AM
Thank you Billko for you response. Good thought in fact. Eventually it turned out to be an issue with the 3rd party driver library. It has been recompiled and does not cause this issue anymore. So this one can be closed.
Thanks again!
04-29-2020 10:27 AM
Don't forget to mark your last post as the solution, just in case someone else has the same issue. 🙂