labview runtime problem

[steve rino]

I have a VI that works perfectly when i run it from the development environment,
but when i create an executable from it, it nolonger works. Any idead what
the problem may be? BTW I checked the data directory that contains the vi's
that are executed at runtime....they still work within the development environment
which leads me to believe this may be a problem with the labview runtime
engine. Any ideas are appreciated. ~Steve

[Dennis_Knutson]

What about it doesn't work? Is it a problem with dynamically called VIs? Is
you custom run time menu missing? Are you using serial drivers? What version
of LabVIEW are you using? Several issues with using the app builder have
been covered in recent threads but a lot more information is required than
"it no longer works".

"steve rino" wrote:
>>I have a VI that works perfectly when i run it from the development environment,>but
when i create an executable from it, it nolonger works. Any idead what>the
problem may be? BTW I checked the data directory that contains the vi's>that
are executed at runtime....they still work within the development environment>which
leads me to believe this may be a problem with the labview runtime>engine.

Any ideas are appreciated. ~Steve

[kjp]

I can't answer for Steve, but I can give details on how it doesn't work for me.

I have developed a simple application on LabVIEW 6.0.2 and using application builder to make an exe. When trying to run the exe on a different machine, the dropdown arrow on the VISA-Resource control is disabled
and when the application is stopped, pressing the arrow causes the application to generate an invalid page fault at 0177:30164426 in the LVRT.dll

Using NI-Spy it can be seen that when the application starts, the call to viGetAttribute returns an error - VI_ERROR_NSUP_ATTR.

On the target machines we have NI-488.2 version 1.6 and NI-VISA 2.01, and on the development machine NI-488.2 version 1.6 and NI-VISA 2.5. Both machines are running Windows98.

I have tried
installing the run-time version of NI-VISA 2.5, but then the application crashes when it loads.

~Kevin

[Todd Gardner]

Hello Steve,

I think I may have the same problem with LV6.0.0 exes.

LV6.0.0 exe's with VISA controls or Indicators crash and LV6.0.1 exe's with VISA controls or indicators require the full upgraded LabVIEW 6.0.1. I.e. At this point I believe they can not run without having the full LV6.0.0 installed and upgraded to LV6.0.1.

To fix this I had to upgrade to LV6.0.0 to LV6.0.1 which is a free download from NI.

If I missed your question here feel free to email me directly at nicoli@bigfoot.com.

Todd
--
NICI, NICP, Alliance member
Sr. Software Engineer for Aladdin Enterprises

[Todd Gardner]

Hello Steve,

I think I may have the same problem with LV6.0.0 exes.

LV6.0.0 exe's with VISA controls or Indicators crash and LV6.0.1 exe's with VISA controls or indicators require the full upgraded LabVIEW 6.0.1. I.e. At this point I believe they can not run without having the full LV6.0.0 installed and upgraded to LV6.0.1.

To fix this I had to upgrade to LV6.0.0 to LV6.0.1 which is a free download from NI.

If I missed your question here feel free to email me directly at nicoli@bigfoot.com.

Todd
--
NICI, NICP, Alliance member
Sr. Software Engineer for Aladdin Enterprises