MarvinSpace display problem

Hi,


I use mozilla 1.7


my marvin space can display properly when the url is


http://localhost:8080/jchem/marvin/doc/dev/example-mspace1.html





But when I change the "localhost" to my hostanme "pc6-183.sinica.edu.tw"


It displays a 'X' , seems applet cannot be loaded


like


http://pc6-183.sinica.edu.tw:8080/jchem/marvin/doc/dev/example-mspace1.html





and when I open


http://pc6-183.sinica.edu.tw:8080/jchem/marvin/doc/dev/example-mspace1.html


with ie on windows .It displays that I have no license key


But it wouldn't display that on mozilla with the url http://localhost:8080/jchem/marvin/doc/dev/example-mspace1.html.








other applet works fine,


http://pc6-183.sinica.edu.tw:8080/jchem/marvin/doc/dev/example-sketch1.1.html





How can I solve that ?


Do I have to configure something ?








Thanks for your help

Hi,





MarvinSpace has to install and load the Jogl native libraries to run properly. The installation mechanism of the applet is the following:


1/ MSpace checks whether the required native library is already at the home directory of the client, in chemaxon\lib\jogl.dll on Windows, .chemaxon/libjogl.so on Linux, and .chemaxon/libjogl.jnilib on Mac.


If the native library is already there, the applet can run properly.


2/ If the file was not found the applet tries to save it there. To do this, the native library files have to be on the server. The MarvinSpace installer will search it under the lib directory at the codebase of the applet.


So you should have the native library files at the http://pc6-183.sinica.edu.tw:8080/jchem/marvin/lib/ directory.





Hope this helps.

Hi,


I have put libjogl.so under ~/.chemaxon/lib


The marvin space seems can display properly now.


But the "No vaild license" message is still there on my ie brower


You can check that with ie


http://pc6-183.sinica.edu.tw:8080/jchem/marvin/doc/dev/example-mspace1.html


The no vaild license message won'r show on my mozilla brower .








Thanks for your help.

Have you managed to solve the different behaviour of the browsers?


I think this may due to the caching of browsers.





Regarding the license issue I will contact you in e-mail.