Robert Hanson wrote: > Yes, the issue is definitely the Java version.We changed to 1.5 > recently. Actually, from what I could tell, we were using 1.5 > functionality already for several months. It looks like Eric is > probably using Java 1.4. > > Eric, if that's the case, first thing to do is check your Java version -- > > Running one of the versions of Jmol that DOES run for you, check the > Java console. Jmol reports the Java version in the first few output > lines of program execution. If it says 1.4, that's your problem. Java > 1.4 was retired about a year and a half ago and is two versions back. > > I'm of the opinion that it is reasonable to expect users to upgrade > Java. That said, does it mean, Eric, that the applet also doesn't run > for you, or in that case is the browser doing a better job of keeping > up with Java updates? > To check the java version just open up a terminal (Application->Terminal) and type
java -version The version on my work machine is java version "1.5.0_22" and that failed with the error messages I quoted. Rich ------------------------------------------------------------------------------ _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
