Omaha configuration parameters now use Wow6432Node (32-bit registry) on 64-bit instal...
commitf7c566f7c49967f6bd468400acf9515766a67c42
authorwfh@chromium.org <wfh@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 28 May 2014 01:54:38 +0000 (28 01:54 +0000)
committerwfh@chromium.org <wfh@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 28 May 2014 01:54:38 +0000 (28 01:54 +0000)
tree8ebfc81fb9410b19708817a89fb121f0108c981f
parent3adff91954d847094b62d4960a5255418123d251
Omaha configuration parameters now use Wow6432Node (32-bit registry) on 64-bit installs.  GCAPI configuration parameters also use these same accesses since they read/write the same data.

Also, force installation of Win64 into C:\Program Files (x86) until the code is added to support moving the files to the right place during upgrade and downgrade.  Uninstall information will remain stored in the 32-bit registry (even on 64-bit) until the installation location is changed.

This fixes system installs on Win64.

BUG=338706
R=grt@chromium.org

Review URL: https://codereview.chromium.org/300593002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273108 0039d316-1c4b-4281-b951-d872f2087c98
18 files changed:
chrome/installer/gcapi/gcapi.cc
chrome/installer/gcapi/gcapi_last_run_test.cc
chrome/installer/gcapi/gcapi_reactivation.cc
chrome/installer/gcapi/gcapi_reactivation_test.cc
chrome/installer/mini_installer/mini_installer.cc
chrome/installer/setup/install_worker.cc
chrome/installer/setup/setup_main.cc
chrome/installer/setup/uninstall.cc
chrome/installer/util/app_command.cc
chrome/installer/util/compat_checks.cc
chrome/installer/util/google_chrome_distribution.cc
chrome/installer/util/google_update_settings.cc
chrome/installer/util/helper.cc
chrome/installer/util/install_util.cc
chrome/installer/util/installation_state.cc
chrome/installer/util/installer_state.cc
chrome/installer/util/product.cc
chrome/installer/util/shell_util.cc