Bug 688484 - Windows installer doesn't detect Java path
Summary: Windows installer doesn't detect Java path
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: Development
Hardware: Unspecified
OS: Windows
medium
medium
Target Milestone: 2.0
: ---
Assignee: Timothy St. Clair
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 08:19 UTC by Martin Kudlej
Modified: 2011-06-27 14:16 UTC (History)
3 users (show)

Fixed In Version: condor-win-7.6.0-2.prerelease
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 14:16:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Martin Kudlej 2011-03-17 08:19:08 UTC
Description of problem:
During installation there is detection of Java path. There isn't correct Java path on 64 bit OSes with 64 bit Java. I think it is because 64 bit Java has default installation location in "Program Files" and not in "Program Files x86".

Version-Release number of selected component (if applicable):
condor-7.6.0-13_20110315.msi
jdk-6u24-windows-x64.exe

How reproducible:
100%

Steps to Reproduce:
1. install 64 bit Java
2. try to install condor
3. installer doesn't detect Java path correctly
  
Actual results:
Installer doesn't detect Java path correctly.

Expected results:
Installer doesn't detect Java path correctly.

Comment 1 Timothy St. Clair 2011-03-21 17:03:09 UTC
Modifications have been made to the installer, but there is still an issue.   

If you create a 32-bit installer (w/binaries target Platform == Win32), windows WIN64DUALFOLDERS will translate any path entries to Program Files -> Program Files (x86) because the WoW subsystem redirects the calls to a different location, even if the registry states otherwise.  Windows in general frowns upon 32-bit + 64-bit program mashing, and literally translates your paths :-/   

The best I can really do here is to put the translated string up and throw a warning on the case where it is not found.  Feedback is desired, prior to setting BZ and MODI.

Comment 2 Timothy St. Clair 2011-03-22 17:59:32 UTC
Upon collaboration with some folks upstream we believe the right thing to do is to check the interpreted registry return value and then check the file system, if fs is incorrect then null out the control and force user to enter.

Comment 3 Martin Kudlej 2011-04-19 08:24:34 UTC
Tested on Windows x86_64/i386 with condor-win-7.6.1-0.2 and it works as it it described in comment #2.-->VERIFIED


Note You need to log in before you can comment on or make changes to this bug.