LV 7.1 EXE which includes "Mean.vi" wont run unless LV7.1 is installed on PC.

[TimTower]

I compiled a VI in LV7.1 under Win2000 SP2. This VI includes "Mean.vi", which is part of Baseanly.llb in Vi.lib. I included LVRT in the compile. When I installed the EXE on a laptop (Win XP sp1), which had never had LV7.1 installed, the EXE was broken. When I clicked the broken arrow, the message was "Cant find Mean.vi". However, if I open a file in the EXE's Data.llb (using the broken VI's File/Open), I can find and open Mean.vi. When I then try to run this, it says a component is missing. It turns out that Mean.vi makes a call to Ivanlys.*, which presume is Ivanlys.dll (in \PF\NI\LV71.\Resource.

Suspecting that AppBuilder had missed this dll, I tried adding it as a support file. AB wont al
low this. I then tried copying this dll to the new laptop�s \Windows\System32 folder, and to the installed LV EXE�s folder. Still no good. Finally, in desperation, I installed LV7.1 full dev system on the new laptop, and now the EXE runs fine.

I suspect that LVRT is not registering and/or installing the dll correctly. How do I fix this problem?

As an aside, it would help it the Exe gave a better diagnostic, like telling one which dll is missing, instead of merely saying, cant find xxx.vi (while in fact the VI was really present).

[Joe_H]

First off are you building and using an installer, If so make sure that the dll is in the installation files, you can do this by going to app builder/installer settings/files if it is not in there it will not work. I had the exact same trouble not to long ago (I use 7.0). try this and see if it works. build an installer along with your exe, make sure the file is were it should be in the installer then run the installer on the machine and it should work.

[TimTower]

Thnks for the feedback. I need to find another PC and test this. I did use an installer, FYI.

I begs the question - one does not know what DLLs are being called. So this can get very tedious - one must try it to find what VIs wont run, then work backwards to find the DLLs. Surely the AppBuilder can find the DLLs and install them itself? I have been using EXEs in LV (with installers) for many years, and have never had to do this. However, it is great to hear there may be a workaround.