OK, so after a couple of silly symptoms, I sort of decided that the system was mad betond reason. I have therefore applied the "master method for troubleshooting": uninstall Java, check that there are no java files left behind, and reinstall. The problem has gone. One more mistery on the list, but doesn't matter.
Thanks to all for your help. Silly symptoms: 1. contrary to what I thought, my home computer was not giving the warning, even after updating Java to the same version. 2. I tested using JmolApplet.jar as Bob suggested and the warning was still there, but still said the problem was with jmolApplet0.jar !! Clearing the Java cache did not fix it. PS: should we still call this "Sun's java" in the recommendations for running Jmol? Orace has taken over, it seems ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users

