The following was tested on Windows XP Professional 64-bit and Java (32 and 64-bit).

With only 64-bit Java installed, the installer (install4j) fails as it cannot see a Java install. If you try and point it manually at the 64-bit Java install, you get an error message saying that the JVM is damaged.

With only 32-bit Java installed, you can install and run SSL-Explorer perfectly, you do not need the 64-bit Java installed at all.

However, if you want to force SSL-Explorer to run with the 64-bit Java you can do so, but you need to have SSL-Explorer installed first. Stop the SSL-Explorer service, then go to the c:\program files (x86)\sslexplorer\conf directory and edit the file called wrapper.conf.

Find the line starting with wrapper.java.command and edit out the x86 after program files so the line reads wrapper.java.command=c:\program files\java\jre1.5.0_11\bin\java (obviously changing the jre part to suit the version of java installed).

You can now safely remove 32-bit Java if you wish and SSL-Explorer will run happily. Please note however that if you are likely to use anything locally on the SSL-Explorer server that requires the agent to be started (tunnels, applications) then you will still need the 32-bit Java to be installed as the agent requires this.

Therefore we reccommend (in order of preference) either:

A) Using 32-bit Java on its own or

B) Have both 32-bit and 64-bit Java installed if you wish to run SSL-Explorer on 64-bit Java