Here you will find commonly asked questions of the ResCarta support team...
Latest JAVA ISSUES
We have suggested using Oracle (previously Sun Microsystems) JAVA for many years, but recent events has changed our thinking.
Oracle will no longer provide free continuing support (updates) for OpenJDK LTS versions at https://jdk.java.net
AdoptOpenJDK does provide support at https://adoptopenjdk.net/ .
AdoptOpenJDK is now distributing OpenJDK msi installers. The installers will optionally updated the PATH and JAVA_HOME. We recommend removing Oralcle JAVA with the operating system supported method and installing OpenJDK 11 LTS. Version 7.0.2 of the ResCarta Toolkit supports OpenJDK 11.
AdoptOpenJDK is also providing updates to OpenJDK 8.
The most asked question concerns the use of 32bit JAVA on a 64bit machine. It you are using a 64bit operating system, download the 64bit JAVA from Oracle. The current url for JAVA 8 from Oracle is.
Take care not to update to unsupported versions of 9, or 10
For those running "ix" operating systems ...
$ sudo apt-get install openjdk-11-jdk
$ su -c "yum install java-1.8.0-openjdk"
During the installation of the ResCarta Toolkit you will see that the installer selects 32bit or 64bit options based on your installed JAVA. If you run 32bit JAVA on a 64bit machine you will get poor performance and have access to only one gigabyte of memory.
Most ResCarta problems over the years involve early untested releases of JAVA by Oracle. See the history of releases at wikipedia. If you see a release date within a day or two of another release date, chances are you will be experiencing some malfunction. We advise updating JAVA only if you need to do so for some known reason.
When I attempt to install the ResCarta Toolkit from the Windows .EXE file, I get a BOING!# sound and then nothing?
We have had this reported on certain newer Windows XP systems with more than 2 gigabytes of ram. The work around is to install from the .JAR file. Just download the ResCarta toolkit jar installer and double click like you would the exe file.
We have yet to determine the culprit. We can have the same version, service pack, and updates on two similar but not exact hardware systems and see the BOING!# on one and not the other. Hopefully we can resolve this shortly.
NOTE: It has been determined that the Java virtual machine is taking more memory that it can use. Machines with 2 gigabytes of ram on Windows XP will take 1638 megabytes of ram for the JVM. Any machine running Windows XP with more than 2 gigabytes of ram will exceed the XP JVM limit of 1650 megabytes. We have corrected this problem in version 2.2.1.