This value is set to 1 is WU is disabled, and 2-5 depending on what enabled option you use. I store the result in property UPDATEDISABLED, and in the install condition table I test for UPDATEDISABLED<>1 and put a message saying you need to disable it before installing.
Problem is no matter what that value is set to, the condition doesn't trigger. I know it's reading it, because I put in another search looking for a non-existent file, with a message of "Updatedisabled is [UPDATEDISABLED]". When I ran it like that I got messages like "Updatedisabled is #1" or "Updatedisabled is #2" for registry values of 1 & 2 respectively. Not sure where the '#' came from, is that automatically put in front of numeric data ?
Any ideas why this isn't working ?
On a related note, there's IMHO a bug in the System Search UI. If you try to modify an existing entry that has been used in an install condition, it comes up with the 'just stick it in a property' radio button checked. If you select the 'install condition' radio button, the previous one is not used, and you add an additional line to the launch conditions table, even if you cancel at this point.
Quite right, please see the bottom half of the "Registry Table" topic for information about what's going on with the # in front of the numeric (REG_DWORD) value.
RobertDickau wrote: Quite right, please see the bottom half of the "Registry Table" topic for information about what's going on with the # in front of the numeric (REG_DWORD) value.
Is that in the help, or a thread here in the forums ? I searched around but didn't find one here.
Oops, operator error on that last one. I changed the condition to use "#1", and did a build, but failed to notice the build error, because I hadn't remapped the network drive I'm building to. Once I ran it actually using the new version it worked correctly. Thanks!
