According to numerous reports confirming each other the browser support for Java 3D through the Java Plugin
available for download from is unrealible. Therefore instead of applets to run in browser
windows here stand alone applets are offered for download as packed The file name denotes the name of the program to be called on the Windows DOS console i.e. Unix shell upon issueing

java -classpath %j3dclasspath% app

where app, template parameter. For example, app = Valent in case of the file to be unpacked.
Each must be unpacked in its own directory (called folder under DOS).

In order to execute the downloaded applets Java 2 JDK including its extension Java 3D must
be downloaded from Before calling the applet it might be necessary to issue


explicitly on the DOS console i.e. Unix shell. The environment variable javacdir is the full path of the directory
(expression used under Unix/Linux systems) in which the program java i.e. java.exe resides. In author's case


Under Vista the Java 3D installer incorrectly defined the system environment variable classpath. The author has overridden
that error by defining the user environment variable classpath which is the installation dependent
string encompassing full pathes of all the Java 3D relevant & files.jar.
This environment variable for the current user (that will run the Java3DAPI applet) is defined via clicking
Start & than Settings & than System Maintenance & than System: search for Environment Variables
activates the link to the User Account Environment Variables Page where j3dclasspath is to be set. Its value under the
account of the author reads (no carriage returns, no spaces, merely the single character string):

j3dclasspath = .;"C:\Program Files\Java\jre6\lib\ext\";
"C:\Program Files\Java\jre6\lib\ext\";
"C:\Program Files\Java\jre6\lib\ext\dnsns.jar";
"C:\Program Files\Java\jre6\lib\ext\j3dutils.jar";
"C:\Program Files\Java\jre6\lib\ext\sunmscapi.jar";
"C:\Program Files\Java\jre6\lib\ext\vecmath.jar";
"C:\Program Files\Java\jre6\lib\ext\dns_sd.jar";
"C:\Program Files\Java\jre6\lib\ext\j3dcore.jar";
"C:\Program Files\Java\jre6\lib\ext\localedata.jar";
"C:\Program Files\Java\jre6\lib\ext\sunjce_provider.jar";
"C:\Program Files\Java\jre6\lib\ext\sunpkcs11.jar";
"C:\Program Files\Java\jre6\1.5.2\lib\ext\java3dcore.jar";
"C:\Program Files\Java\jre6\1.5.2\lib\ext\java3dutils.jar";
"C:\Program Files\Java\jre6\1.5.1\java3dcore.jar";
"C:\Program Files\Java\jre6\1.5.1\java3dutils.jar";
"C:\Program Files\Java\jre6\1.5.1\vecmath.jar"

Under Linux the installer correctly set the environment variables. Already the login shell defines them. Accordingly
neither the loader java required the option classpath explicitly nor issueing the path call before calling it was required.

In order to avoid typeing both commands explicitely on the Windows promt since August 2014
the Windows command script with extension cmd app.cmd (app, template parameter) is enclosed. Execute app.cmd
either by clicking onto its cog-wheel icon in the Internet Explorer window of the folder in which
the unpacked class files, itself & the ASCII inputFile1, inputFile2,..... if supplied, reside or by issueing


on the Windows command promt. The script to be called on the Unix shell is its trivial equivalent.
Since according to the author's experience under Unix/Linux the user needn't define
environment variables J3DCLASSPATH & JAVACDIR it should read

#! /bin/ksh
java app
# option -Xmx if documented in app.cmd
# parameter(s) inputFile(s) providing coordinates of structure definition points
# &/or rotation matrices & translation vectors if documented in app.cmd