As of Janel 4.0.0, I noticed that if both 32- and 64-bit JDK are installed in Win64, the 64-bit version of Janel always detects the 32-bit JDK first and thus refuses to run. Is there any check to prevent this? Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks a lot for the patch. However, I noticed that in 64-bit Win 7 and only 32-bit JDK is installed, Janel didn't give an appropriate warning, only "Error while locating JVMs". The user might be confused since he/she thought that JDK was already installed. So, I'm wondering if you could add some message to that effect?
Thanks a lot.
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You're welcome! Thank you for the suggestion to use a more specific error message. Historically the reason a generic error message is used when a JVM cannot be found is because at times it is impossible to blame just one thing for why Janel was not able to find an appropriate JVM. For example if using a 64-bit Janel and the .lap file says use at least Java 6 and there is an unused 32-bit Java 5 JVM - is the problem with the JVM that it is a 32-bit or is it because it is Java 5? It's both. But I will take the suggestion into consideration.
Thanks again,
Tim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
As of Janel 4.0.0, I noticed that if both 32- and 64-bit JDK are installed in Win64, the 64-bit version of Janel always detects the 32-bit JDK first and thus refuses to run. Is there any check to prevent this? Thanks.
Hello,
There is no check to prevent this. This bug in Janel will be fixed in Janel version 4.0.1.
Thanks for the bug report!
Tim
Janel 4.0.1 is now available with the fix for this.
Tim
Hi Tim:
Thanks a lot for the patch. However, I noticed that in 64-bit Win 7 and only 32-bit JDK is installed, Janel didn't give an appropriate warning, only "Error while locating JVMs". The user might be confused since he/she thought that JDK was already installed. So, I'm wondering if you could add some message to that effect?
Thanks a lot.
Rob
Hi Rob,
You're welcome! Thank you for the suggestion to use a more specific error message. Historically the reason a generic error message is used when a JVM cannot be found is because at times it is impossible to blame just one thing for why Janel was not able to find an appropriate JVM. For example if using a 64-bit Janel and the .lap file says use at least Java 6 and there is an unused 32-bit Java 5 JVM - is the problem with the JVM that it is a 32-bit or is it because it is Java 5? It's both. But I will take the suggestion into consideration.
Thanks again,
Tim