The Java alternatives system helps manage different Java installations by configuring default versions for tools like Java Compiler (javac), Java Runtime Environment (java), and Java Web Start (javaws). In order to update Java alternatives on a Linux-based system, you can use the `update-alternatives` command. Here is a step-by-step process to update these alternatives. This command helps manage different Java installations by configuring default versions for tools like Java Compiler (javac), Java Runtime Environment (java), and Java Web Start (javaws). Any ideas anyone? Thanks.Updating Java alternatives on a Linux-based system can be done using the `update-alternatives` command. It looks to me like Frostwire is looking in the wrong place for Java. Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode) Java(TM) SE Runtime Environment (build 1.6.0_05-b13) (FrostWire is tested against and works best with with Sun's JRE, Java 1.4+) Maybe you're using the wrong version of Java? So what do I do to tell Frostwire to use the 32-bit Java? Line 134 is 'java -version' which I marked in the code, just here, not in the real file. $EXECUTABLE -jar FrostWire.jar $ARGUMENTSĮcho '******************************************************************'Įcho 'Something went wrong with FrostWire.'Įcho 'Maybe you're using the wrong version of Java?'Įcho '(FrostWire is tested against and works best with with Sun's JRE, Java 1.4+)'Įcho 'The version of Java in your PATH is:' If ] thenĮcho $MSG8 '$java -ea .Log=.impl.NoOpLog =. Potential_java_dirs=(`ls -d1 '$JAVADIR'/j* | sort | tac`) MSG10='Java exec not found in PATH, starting auto-search.' MSG8='OOPS, unable to locate java exec in ' FrostWire works best with Sun JRE available at '

MSG7='OOPS, you don't seem to have a valid JRE.

MSG4='You need to upgrade to JRE 1.5.x or newer from ' MSG3='OOPS, your java version is too old ' # this should allow starting limewire from This script must be executed in your FrostWire

Update alternatives java