Community Forums
Page 2 of 2 FirstFirst 12
Results 6 to 8 of 8

Thread: How to set running JVM for installer that built without bundle JVM

  1. #6
    Join Date
    Mar 2006
    Paris, France


    The list of VMs that this LaunchAnywhere Executable will allow the Java application to be run against. The value for this property can be any space- or comma-delimited combination of the following: 
    ALL (any VM)
    JDK (any Java JDK)
    JRE (any Java JRE)
    The value of this property will also override the value listed in if the VM listed in that property is not of a valid type. The order of the valid VM list specifies the precedence in which VMs found on the system should be chosen if a valid VM is not listed in
    So in your case I would say the best try would be 1.5*, but I don't think there is any 32 / 64 bit distinction, I think it'll maybe up to the installer, if it's a 32 / 64 bit one, it'll choose the right JVM (nevertheless, I think that bundling the correct JVM will save you from troubleshooting the countless different situations you may encounter, as you can never predict what spooky situation will be on customer's machine).

    You also may want to check these documebnts: (this one applies to IA 2009, though)

  2. #7
    Join Date
    May 2010
    On windows 64bit box, The register table information for 32bit program will be located at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node, 64bit program still at HKEY_LOCAL_MACHINE\SOFTWARE. System path for 32bit program is c:\windows\ SysWOW64, the patch for 64bit program is c:\windows\system32.
    Due to that, sometimes I must select 32 bit JVM or 64 bit JVM. look at following scenario:
    If a 32 bit software has been installed on 64 bit windows. the register table information is at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CompanyA. To read the register information, if the installer is invoked by a 32bit JVM, the code only need to reference "HKEY_LOCAL_MACHINE\SOFTWARE\CompanyA", but if invoked by a 64 bit JVM, the code must reference "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CompanyA". that cause the installer code to be complex to support both 32 bit JVM and 64 bit JVM.

  3. #8
    Join Date
    May 2010
    Hi pv7721,
    Due to above reason, I have to distinguish 32bit and 64 bit JVM. Do you have a better way?


Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts