LabVIEW
Bug Reading Registry in LV2012 and LV2014, Ending bracket is missing
Hi Melanie,
i readout several hundreds entries and around 10 to 20 like this style from "SymbolicName".
Every SymbolicName is without the last "}". I only notice is because i use RegEx to get the
part inside the { } and that didn't work 
and i was wondering why (the RegEx was ok).
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\
The underlined part changes but the key "SymbolicName" always exist below "Device Parameters".
I use Windows 7 x64. For now i check if the last char is a "}" and if not i add it.
Stefan
Do you use backslash code display in the string control? All the Symbolic Names for USB devices in my system start with \??\USB# not \\??\\USB#.
It may be that the installer which wrote those values to the registry has somehow messed up. Looking at the low level inplementation of the Read Registry Value VI there is a potential that the installer attempts to write \??\USB.... to the registry and correctly updates the size for that string but really writes \\??\\ into it due to wrong unescaping in its installer routine. This would result in the registry to contain a string that is in fact 2 characters longer than it indicates to be.
LabVIEW retrieves a buffer and cuts it to the number of bytes the registry entry indicates and then tries to search for the zero char. Since the registry entry believes to be smaller than it is, this results in a early terminated string, with the last character missing.
The real problem is in fact the installer for that driver, which messes up with unescaping of the backslash character. The problem makes itself apparent in LabVIEW since the LabVIEW Read Registry function takes the returned parameters literal, where as it should probably be more lenient on string values and simply search for the zero terminated string end, ignoring what the registry entry tells it the length to really be.
