I'm wondering how others use the differing program launch location for many
programs, between Win7 32-bit and 64-bit. This seems like such a basic issue
that there has to be a standard approach ...

e.g. Many programs install to "C:\program files" for 32-bit and "C:\program
files (x86)" for 64-bit. The latter location matches up to ${programfiles32}
but presumably that value is non-existent or null on a 32-bit system.

The enterprise I'm working in, years ago, created an environment variable to
set on each system, for the location for 32-bit program installs. Using this
value (PRGSRC) the system has the setting enabling %PRGSRC% to use as a launch
path. So %PRGSRC% corresponds to "C:\program files" on 32-bit systems, and
"C:\program files (x86)" on 64-bit systems, and a launch may point to something
like %PRGSRC%\myapp.exe .

Now I have a request from the Windows admin team to stop using custom
environment variables in Zenworks packages. And since this is an extremely
common situation, I'm wondering how other Zenworks environments handle it.
e.g. is everyone just building a separate launch for 32-bit vs 64-bit programs
when the program installs on 64-bit systems to "C:\program files (x86)"? Is
there a standard way to do this that I'm missing? Any suggestions that don't
plant the custom environment variable?


-- DE