If you have a Java interpreter available elsewhere, you can download
the files available in this directory and run the program using
them:

<ul>
<li>The file <a href="vl.tar.gz"><code>vl.tar.gz</code></a> is now
available for download to a UNIX system. You can then follow the
directions below to unpack it and run it the same way. A <a
href="vl-all.tar.gz">larger VerbLearn distribution</a> including
<a href="source.tar.gz">source code</a> and 
<a href="docs.tar.gz">documentation</a> is also available.<br /><br />

<li>If you wish to try running them on a non-Unix system, be
forewarned that you may be on your own as far as getting it up and
running. The program assumes a particular directory structure for
finding the files it needs. Download the <a href="NTLSystem.zip">NTLSystem.zip</a>
  file, unzip it and you should find the following files:&nbsp;

<ul>

<li>A <code>classes</code> directory containing the Java class files,
which are archived in <code>ntl.jar</code> and <code>swing.jar</code>

<li>A <code>data</code> directory containing two subdirectories:

<ul>
<li><code>dicts</code>: a dictionary directory containing <code>vlFeatures.fdict</code>

<li><code>scenario.sets</code>: a scenario set directory containing <code>oldData.sset</code>

</ul>

<li>A <code>properties</code> directory with two general properties
files, <code>default.properties</code>
and <code>verblearn-default.properties</code>

<li><code>vl</code>: a tiny script showing the command line used for
running the java interpreter for the class
<code>NTLSystem.verblearn.VerbLearn</code>. Note that this is tailored
for use with the EECS instructional system and is included here as a
guideline only.  Note also that the extra </code>-m</code> flags are
used to increase the memory allocated to the VerbLearn program, and
the <code>-classpath</code> path specifies the two .jar files in the
<code>classes</code> directory mentioned above.

</ul>

Once you've copied all the necessary files, you will need to run the
program from within the <code>NTLSystem</code> directory. 
</ul>

<hr>

If you have ssh and x-windows at home (if you can run x-windows
graphics remotely), you may be able to run the programs by remotely
logging into one of the Solaris-X86 servers (rhombus.cs, pentagon.cs, po.eecs,
torus.cs). Be forewarned that it might be <i>very</i> slow because there is a
lot of graphics to display. <font color="red">But warning:</font> incompabilities
between x-windows and the Java interpreter <i>may</i> result in the
program not working remotely. (For instance, a VerbLearn window may
pop up without any content.) The best solution so far is to use the
recommended lab computers in place or to download the materials as
described above.

<hr>

If you want to use Soda machines other than the ones in rooms 275-277,
this might be easily done by altering the <code>vl</code> file in the
<code>NTLSystem</code> directory (or typing a variant of the command
line it contains at your prompt).  The <code>java</code> command path
has been tailored for the Solaris X86 machines in rooms 275-277, but
other machines can obviously run Java programs as well.

<p>See <a
href="http://www-inst.eecs.berkeley.edu/usr/pub/java.help">this</a>
document for help on this matter (though it might be slightly out of
date). (Essentially, depending on what machine you have, you should
substitute an appropriate java path.)