11-09-2012 08:06 AM
We're trying to use the subject driver on ourLabview 2011 SP1 platform and finding inconsistent behavior depending on what PC it's used on.I got the 2011 driver from
The problem shown most simply is placing the Initialize vi in a blank vi, and finding a broken Run arrow, opening the Initialize.vi and finding a broken run see attached screenshot. This problem occurs on 1 Vista and 1 XP computer, but does NOTpose a problem on 3 other XP and a Win7 computer all using the same Labview version. Any help would be appreciated.
11-09-2012 02:23 PM
Perhaps that machine has an old version of the .net assembly. On both a working machine and the broken one, goto "View", ".Net Assemblies in Memory". That will tell you which version of the assembly has been loaded.
11-12-2012 06:20 AM
Thanks for the suggestion. On both the working and non-working computers there are no .net assemblies in memory. However there is an accompanying problem AND we've solved both. The accompanying problem is LV updates these old drivers to LV2011 after they're loaded, then asks to save them, and we reply yes, then get a message that we can't save them because we don't have rights. The solution, even though it's still strange, is in the properties of the drivers folder. The Read Only property is a green box, and some computers see this as Read Only and some do not. By changing the green box to unchecked, these problems go away. All computers are Windows XP, same version. Weird.