This applet has been tested with HotJava 1.0, if you are using Netscape then refer to CommDiagForNetscape.html, not CommDiag.html (this file).

Applet security levels are configurable within the HotJava browser. But, be sure to remove interclient.jar from your local CLASSPATH to avoid certain security exceptions.

The most common reason for the error "Java SecurityManager does not allow socket connections to server on port 3060" is that interclient.jar is being picked up from your local classpath. See the InterClient API reference for class BadInstallationException for further details.

This applet will not initialize using Microsoft's Internet Explorer.

The Netscape Communicator 4.0, is not yet enabled for the AWT 1.1 event model (aka Java Beans event model), therefore this applet will throw an exception as it tries to initialize in your browser's Java console. Netscape's JDK 1.1 patch should fix this problem.

This html file include a reference to the interclient.jar Java archive file. This archive file includes a CommDiag utility which uses the AWT 1.1 event model.

Without Netscape's JDK 1.1 patch, you should use invoke the CommDiag for Netscape applet thru CommDiagForNetscape.html. The applet interbase.interclient.netscape_utils.CommDiag uses the old AWT 1.0 event model.

See help/help.html for further details on deploying applets.