02-26-2009 08:26 PM
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.
Solved! Go to Solution.
02-27-2009 02:00 PM
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!
02-27-2009 03:29 PM
Hi Kyle
Many thanks for the response. I guess that's a solution - knowing its an issue to be investigated.
regards
Andrew
11-19-2009 10:21 AM
11-20-2009 10:09 AM