I have a exe file build with Launch4j. The computer I want to execute the *.exe on, has the Java Server JRE installed. Unfortunately the JVM cannot be found and therefore I am not able to execute the program.
The problem seems to be the Java Server JRE. With a standard JRE installation the program runs without problems.
How does Lauch4j detect the location of the JVM? Setting the Windows PATH Environment Variable does not help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The location of JVM is detected using the Windows Registry. The Java Server JRE is not 'installed' from the Windows perspective but rather unzipped and put into a directory, so Launch4j cannot know of its existence. If you made the executable, you can add a bundled JRE path (with the fall-back option) that points to this environment. A relative path is preferred. If not, you can try: java -jar app.exe. Although this might not work correctly because then you loose all the options that Launch4j generates for the launch of this application (for example classpath).
Grzegorz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a exe file build with Launch4j. The computer I want to execute the *.exe on, has the Java Server JRE installed. Unfortunately the JVM cannot be found and therefore I am not able to execute the program.
The problem seems to be the Java Server JRE. With a standard JRE installation the program runs without problems.
How does Lauch4j detect the location of the JVM? Setting the Windows PATH Environment Variable does not help.
The location of JVM is detected using the Windows Registry. The Java Server JRE is not 'installed' from the Windows perspective but rather unzipped and put into a directory, so Launch4j cannot know of its existence. If you made the executable, you can add a bundled JRE path (with the fall-back option) that points to this environment. A relative path is preferred. If not, you can try: java -jar app.exe. Although this might not work correctly because then you loose all the options that Launch4j generates for the launch of this application (for example classpath).
Grzegorz