Caution: In this restricted "Fossies" environment the current HTML page may not be correctly presentated and may have some non-functional links.
Alternatively you can here view or download the uninterpreted source code.
That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
Operation of LTOOLSgui as a standalone Java application
Running LTOOLSgui as a stand alone application is the preferred solution. To
start it, simply type LTOOLSgui from your command line or double click on
LTOOLSgui.bat in the Windows Explorer. You must have the Java SDK 1.2 (or newer)
or at least the Java Run Time Environment JRE 1.2 (or newer) installed and
accessible via your path setting.
Operation of LTOOLSgui as a Java applet in a web browser
Running as a stand alone application is the preferred solution. However if you really want to run
LTOOLSgui as a Java applet in your web browser, open this page in your
browser. You must have the Java Plugin 1.2 (or newer) installed. Probably, this only works
with Netscape's Navigator or Microsoft's Internet Explorer.
LTOOLSgui requires some information about your operating system and needs
access to your local harddisk. Due to security considerations (Java's sandbox
concept), in a standard installation this is not allowed for Java applets. To enable
the necessary hardware access, you have to modify Java's security policy appropriately. The following
policies are needed:
This code should be placed in a file named ".java.policy" and copied to the user's
home directory. If a file of the same name exists, instead of replacing it, add the
above code to it. For your convenience a .java.policy file is already provided in the
./bin directory of the LTOOLS.
Note: Using a policy as described may pose a security risk to your
system, as any JAVA applet loaded from the Internet will use this policy, bypassing
some of the standard sandbox restrictions. If you want finer control, use the
"policytool" contained in the JDK. Instead of granting access to ALL FILES you
may then restrict access to those files contained in the .\bin" directory, where your
LTOOLS files are installed.