LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Shared Variables in run-time exe on Windows 2000

Solved!
Go to solution

Does anyone know if there are issues with Shared Variables on Windows 2000? I can't seem to get LabVIEW executables which use Shared Variables to work on a Windows 2000 machine with just the run-time engine.  Everything works perfectly on XP on a machine with just the LabVIEW run-time engine installed (using LV 8.5).  Shared variables are supposed to work under 2000.  I attach example code which is based on one of the NI examples for Shared Variables - Publisher and Subscriber - with some extra stuff I added for diagnostics.  On Windows 2000 you can only run one or the other exe.  It seems that as soon as the second one gets to the part on the diagram with the shared variable node it hangs.  The shared variables are actually getting written to because if you close the Publisher and then run the Subscriber exe it reads the last set values correctly.

On Windows 2000 I've tried it with Administrator account and turned off virus checkers, firewalls.  Maybe there is some other Windows 2000 setting that causes this problem with both exes trying to access the shared variables.  I don't have the development environment on the Windows 2000 machine as the purpose of this exercise is to see if its worth using shared variables.  Windows 2000 computers are still common in the Test and Measurement world.  A search on Developer Zone doesn't say there are any particular problems with Windows 2000. 

Any suggestions appreciated.

0 Kudos
Message 1 of 5
(3,476 Views)
Solution
Accepted by topic author Andrew Madry

Hi Andrew,

 

Thanks for the feedback!  Your feedback will help us to improve LabVIEW for our customers.  This bug has been reported to R&D (#45493) and they are currently investigating this issue.  For now, the best workaround appears to be using a different OS, as this seems to only occur in Windows 2000.  Thanks for the feedback!

Message 2 of 5
(3,454 Views)

Hi Kyle

 

Many thanks for the response.  I guess that's a solution - knowing its an issue to be investigated.

 

regards

 

Andrew

0 Kudos
Message 3 of 5
(3,448 Views)
Does this mean that your program was working with a windows 2000 machine with Lab View 8.6, but did not work when you only had the run time engine installed?  I am having this same problem.  Have there been any new work arounds since February?
0 Kudos
Message 4 of 5
(3,064 Views)
I posted the wrong CAR ID before, it's #45943.  It also is still under investigation.
0 Kudos
Message 5 of 5
(3,048 Views)