Global 32bit and 64bit relevance

(imported topic written by rmnetops91)

Is there an easy way to combine this relevance into one string so it will work for both a 32bit and 64bit Windows OS?

exists value “DisplayName” of keys whose (value “DisplayName” of it as string as lowercase contains “lotus notes 7”) of key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall” of registry as string

OR

exists value “DisplayName” of keys whose (value “DisplayName” of it as string as lowercase contains “lotus notes 7”) of key “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall” of registry as string

64bit OS’s generally will have “Wow6432Node” in the SOFTWARE key for 64bit apps. We want to avoid having to put both formats in for every auto-group we have where an installed app may span both 32 and 64 bit machines.

(imported comment written by JackCoates91)

you can nest the queries, though there’s probably a more efficient way to do it:

q: if (exists values "DisplayName" of keys whose (value "DisplayName" of it as string as lowercase contains "pidgin") of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of registry as string) then (true) else (if (exists values "DisplayName" of keys whose (value "DisplayName" of it as string as lowercase contains "pidgin") of key "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall" of registry as string) then (true) else (false))
A: True
T: 1.436 ms

(imported comment written by rmnetops91)

Thanks for the suggestion. We will try it out and compare with any other methods people may post. Efficiency/performance is what we are going for. Anyone else have any other suggestions for us to try?

(imported comment written by jessewk)

between the ‘registry’, ‘x32 registry’, ‘x64 registry’, and ‘native registry’ inspectors you should be able to make it work with a single lookup. But I never remember what works where so you’ll have to experiment.

(imported comment written by rmnetops91)

Using the ‘native registry’ inspector works the way I need it on a single lookup. Thanks!

(imported comment written by JackCoates91)

FYI, the registry wizard was recently updated to let you select between using native or explicitly working with 32 or 64 bit.