LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how to read registry value?


battler. wrote:

In other words the LV registry write functions are made obselete as of Vista..

 

I've found that the Vista Virtualisation method of accepting registery write operations to be unreliable.


Well it has little to do with LabVIEW really. LabVIEW simply calls into the Windows API and if you feel the registry has been made obsolete for use by user applications as of VISTA then you are indeed up to something although you are certainly stressing the truth. You can still use it in user applications but not to put in system wide settings and especially not to hide information.

 

Virtualiation works fine but Vista explicitedly does not virtualize the entire non-HKCU part of the registry but only specific parts of it. One of them ist the HKLM\Software sub-hierarchy except for keys and all its subkeys that have gotten a specific new attribute preventing it to be virtualized. An IT departement could for instance setup a user machine to have all or specific parts of the HKLM\Software registry keys with this attribute. Or an installer could create such a key during application installation.

 

But no, please don't yell that the LabVIEW installer does not support that new super duper feature yet! First it wouldn't help with what you want to do, since it simply prevents virtualization for such keys, causing an access error if you try to write to it without elevated rights and second adding every new feature of MacOS X, Linux, and Windows to LabVIEW as it appears is simply impossible.

 

Rolf Kalbermatter

 

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
Message 11 of 11
(1,047 Views)