03-22-2022 02:44 PM - edited 03-22-2022 02:52 PM
And where did you get that FTDI DLL? Did you install it with an installer or just copy it in your CVI application to be installed with your exe? I would pretty much bet that that DLL is your culprit!
If you have a DLL you want to place on another system you NEED to install it and that installer needs to make sure to install the necessary runtime libraries and other possible dependencies. And that means that the installer should be created by the DLL creator! Copying DLLs to another system is ALWAYS a bad idea. You do not know what its dependencies may be and even if you track them down it may not be enough on a different system.
Normal Windows installations most likely use some tool, command line or something else (maybe some hidden clippy or something like that 😀), that was compiled with Visual Studio 2010, so the according runtime is by chance installed (unless someone does a custom install and manages to convince the Windows installer to NOT install that tool, which normal users can't but an overzealous IT department might be able to do that when installing Windows Enterprise).
03-22-2022 02:51 PM
I have confirmed the same issue with LTSC and a sample user interface project that comes with. LabWindows 2017.
Avoid LTSC. It's just not worth it 🙂
And I agree about the DLL issues. We've been using the 2010 installer (building it in to our LabWindows installer) per suggestions in this forum (not related to any other DLL).
Only upon the discovery that this version is no longer supported by Microsoft, and does not list Windows 10 as a compatible platform, did I return to this rabbit hole today.
03-28-2022 12:18 PM
For anyone who needs this info in the future…
msvcp100.dll
msvcr100.dll
There is a link elsewhere in this forum the the 2010 VC++ restributable (which is how I found it).
There is a newer Service Pack 1 available from Microsoft:
https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
it is no longer supported, but the newer version doesn’t contain these DLLs.
Windows 10 comes with these DLLs built in, and are newer.
It is unclear what requires it, but I’ve managed to deselect alot of the items in the LabWindows 2017 installer and it no longer asks for it.
Good luck!