Any ideas? What am I missing?
Using string table entry in script
Posted 21 March 2001 - 19:55
Posted 21 March 2001 - 20:04
For example, if you created a string table entry called "REGISTRYKEYNAME" with a value of "SOFTWARE\\Company\\Product", should have @REGISTRYKEYNAME in the function.
If that's confusing, or if your problem still isn't solved, please feel free to email me.
Posted 21 March 2001 - 22:29
string table entry is
MY_KEY \\SOFTWARE\\Company\\Product
Then I've got the script...
RegDBGetKeyValueEx (@MY_KEY, szName, nvType, svValue, nvSize)
Doesn't work. :(
Posted 21 March 2001 - 23:41
I tried a test similar to what you've said, and it worked just fine. I even added a line:
MessageBox(@MY_KEY, INFORMATION);
which caused a message box to popup with the value that I had put into the String Table entry for MY_KEY. The only difference (and this shouldn't be a problem) is that I used \ instead of \\ in the Value in the String Table.
Just a sanity check--if you go to General Information under Organize Your Setup, and then you go to the String Table for English, and scroll all the way to the bottom of the list, you do find MY_KEY there, right?
Posted 22 March 2001 - 08:31
Quote |
The only difference (and this shouldn't be a problem) is that I used \ instead of \\ in the Value in the String Table. |
This is indeed a significant difference: Use double backslashes in string literals you write in script:
szKey="Software\\Company";
But don't use such excape sequences in the string table:
MY_KEY Software\Company
Also don't have a leading backslash in the key name. SO your string table entry should look like this:
MY_KEY SOFTWARE\Company\Product
Posted 22 March 2001 - 15:00
Posted 22 March 2001 - 18:32
Quote |
My understanding is that she has created a String Table entry, MY_KEY, which is not being recognized in the script. |
Oops, should have read the original post more thoroughly. In this case I suspect that she may not have perfoemd a media build after adding the string table entry.
Posted 23 March 2001 - 20:26
So if it really was only a \\ problem, it's strange that the debugger showed the property as "not found"...
Thanks again for your help!