LabVIEW Player

[James Goodley]

I have LabVIEW 6 and I am trying to use LabVIEW player. I have made a
new library with all the
subs including even the NI library ones eg white noise generator and
sine wave generator ,FFT etc

I sign the directory and it does not complain. When I run LabVIEW player
I select the main
program and up it pops. Then I try and run it and it says 'white
noise.vi' is not executable
and the same with all the other library files. I was unaware I had to
save all the library files
in the first place but it complained when I did not. What therefore is
the right procedure.
I have a program with several subs which call library functions - FFTs,
sine wave generators
etc.

Many Thanks

[Labviewguru]

James,

I have seen a similar issue with regards to running in a runtime environment. Perhaps my experience can be of value.

Try doing a save all on the top level VI. Be sure that none of them are read only or archive, which often happens in distribution, especially to a CD. Try writing a batch file that sets the attributes (attrib *.* -r -a /s).

This may help. Please let us know how you do.

Good luck

Almost forgot, check your hierarchy and check the option to view the full VI path. Go over each element and be sure it is in your library or directory structure. It is quite possible that you are calling something from within the labVIEW directory unwittingly and this can be very problematic.

[James Goodley]

Hi there

I tried what you suggested and it works! (the attrib thing) Many thanks.

James



Labviewguru wrote:

> James,
>
> I have seen a similar issue with regards to running in a runtime
> environment. Perhaps my experience can be of value.
>
> Try doing a save all on the top level VI. Be sure that none of them
> are read only or archive, which often happens in distribution,
> especially to a CD. Try writing a batch file that sets the attributes
> (attrib *.* -r -a /s).
>
> This may help. Please let us know how you do.
>
> Good luck
>
> Almost forgot, check your hierarchy and check the option to view the
> full VI path. Go over each element and be sure it is in your library
> or directory structure. It is quite possible that you are calling
> someth
ing from within the labVIEW directory unwittingly and this can
> be very problematic.