--- Glenn Holmer <[EMAIL PROTECTED]> wrote:
> Alexander Busch wrote:
> > Hi,
> >  
> > having j2re1.3.1 running I am trying to run an app that requires the 
> > javax.comm package.
> >  
> > I have taken a look at rxtx, and also downloaded the sparc version of 
> > the package, in order to somehow be able to do as described in the 
> > install instructions. However, I have to admit, that these instructions 
> > are not really clear.
> > Can anybody help me and tell me what files I need exactely, where to 
> > find them, and how to set the classpath correspondingly? Is there any 
> > good installation instruction?
> 
> I've attached the document we use at work for instructions.
> Hope this helps.
> 
> -- 
>   ==================================================
>    Glenn Holmer (Linux registered user #16682)
>   --------------------------------------------------
>    "You may think this is the finest pearl
>     But it's only cardboard balls, seamed in glue
>     Overwhelming technique; done through diligence"
>   --------------------------------------------------
>                -Captain Beefheart, "Best Batch Yet"
>   ==================================================
> 
<HR>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<HTML>
  <HEAD>
    <TITLE>Installing Java Comm Drivers</TITLE>
    <style type="text/css">
      body        { font-family: sans-serif; font-size: 12pt;
                    margin: 2em; background: white }
      h3          { font-weight: bold; text-decoration: underline }
      code        { font-weight: bold }
    </style>
  </HEAD>
  <BODY>
    <h3>Installing Java Comm Drivers for Linux</h3>
    <ol>
      <li>Extract the Solaris version of the comm drivers 
          (<code>javacomm20-x86.tar.Z</code>) to <code>/java</code>.</li>
      <li>Copy <code>comm.jar</code> to 
        <code>/usr/lib/java/jre/lib/ext/</code>.</li>
      <li>Copy <code>javax.comm.properties</code> to 
        <code>/usr/lib/java/jre/lib</code>. Change the driver line to read 
        <code>Driver=gnu.io.RXTXCommDriver</code>.</li>
      <li>Extract the low-level "RXTX" drivers (<code>rxtx-2.0-4.tgz</code>)
        to <code>/java</code>. <u>Make sure you have the version that uses
        <code>javax.comm</code> (not <code>gnu.io</code>)</u>. This refers
        to the packages that the Javacomm classes appear in, not the 
        low-level driver referred to in the previous step.</li>
      <li>Change directory to <code>/java/rxtx-2.0-4</code> and build the
        low-level drivers as root (make sure your system has the standard 
        build tools installed): make sure <code>JAVA_HOME</code> is set, 
        then run <code>./configure</code>, <code>make</code>, and <code>make
        install</code>.</li>
    </ol>

    <h3>Installing Java Comm Drivers for Windows</h3>
    <ol>
      <li>Extract the Windows version of the comm drivers
        (<code>javacomm20-win32.zip</code>) to <code>C:\java</code>.</li>
      <li>Copy <code>comm.jar</code> to 
        <code>&lt;java-install-dir&gt;/jre/lib/ext/</code>.</li>
      <li>Copy <code>javax.comm.properties</code> to 
        <code>&lt;java-install-dir&gt;/jre/lib</code>.</li>
      <li>Copy the low-level driver (<code>win32com.dll</code>) to
        <code>&lt;java-install-dir&gt;/bin</code>.
    </ol>

    <p>Because of the locations these files are installed to, there is no
    need to add the drivers to your classpath.
  </BODY>
</HTML>

Just FYI.  If you set $JAVA_HOME and extract the CommAPI from Sun, The
configure script will place comm.jar and the javax.comm.properties file
 in the correct locations and put the correct text in the properties file.
Either method is fine.

The CommAPI documentation from Sun was intended for JRE/JDK 1.1.  There
was no ext directory at that time.  This often causes confusion with new
java users.

__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to