home *** CD-ROM | disk | FTP | other *** search
- # JEXT.NCF file for starting Jext on NetWare 5 by Marc Savereux
- #
- # - This script should be placed in the SYS:\SYSTEM directory or in any
- # other directory that is part of the NetWare host's search path.
- #
- # - This script assumes that the full path to the extracted Jext.jar file
- # has already been added as an additional classpath line entry in the
- # SYS:\ETC\JAVA.CFG file prior to the loading of the JAVA.NLM or running
- # the STARTX.NCF script file.
- #
- # For example, if the full path to the Jext.jar file created by the
- # extraction of the Jext.zip file is 'SYS:\JAVAUTIL\JEXT\LIB\jext.jar',
- # then an entry like the one below would be added to the JAVA.CFG file:
- #
- # CLASSPATH=$CLASSPATH;SYS:\JAVAUTIL\JEXT\LIB\jext.jar
- #
- # Note: This script has only been tested with Support Pack 2A and 4 for
- # NetWare 5.0.
- #
- # Load the NetWare JAVA.NLM executible if it isn't already loaded.
- #
- # Note: If JAVA.NLM is already loaded, a syntax error message will appear
- # on the NetWare console. This message can safely be ignored.
- #
- # Starting the JAVA.NLM is the minimum requirement to using Jext on
- # NetWare 5, however, I have found that using the STARTX.NCF script
- # sets up a more stable environment than JAVA.NLM alone. So, in the
- # long run, I would recommend either having STARTX as part of the
- # scripts called by the AUTOEXEC.NCF script, or issuing the STARTX
- # command at the NetWare console a minute or more before issuing a
- # java com.chez.powertrain.Jext.jext command.
- #
- # If the STARTX.NCF script is always going to be run prior to using
- # Jext, then the JAVA command below can be commented out.
- #
- JAVA
- #
- # Execute the Jext application.
- #
- java org.jext.Jext
-