Introduction
FAQ
Download
Installation
    Linux/Unix
   Windows 95/98/NT
Getting started
Call for contributions
Contacting the author
Disclaimer
Back to the Main Menu

All contents on this page are copyright (c) 1998, 1999 by Tilo Christ. All rights reserved.
This page was last rebuilt on Mon Mar 22 09:44:55 CET 1999 .

 These instructions have been tested on an Intel Linux box, running RedHat 5.0, and the JDK 1.1.6v1, JDK 1.1.6v4a, JDK 1.1.6v5, and JDK 1.1.7v1a from http://www.blackdown.org.
A third party has confirmed that this is also working on Solaris 2.6 (Sparc and x86).
A similar installation procedure should work on most other Unices too. You are welcome to contribute more specific instructions for other Unix platforms!

Installation of the pure Java code only

Unpack the download archive into a place of your liking. Include the files Java/SyncBuilder.jar and Java/jndi.jar into your CLASSPATH environment variable. Then check for successful installation.

Installation of both Java and native code

Personally, I use IBMīs blindingly fast jikes compiler for Linux . It works great for compiling SyncBuilder . The configuration procedure during the source code installation will try to detect jikes in your PATH and will use it for building the package if it is available.
The Jikes compiler may be downloaded for free at http://www.alphaworks.ibm.com/formula.

Of course, you will also be fine if you use the javac compiler.

Please tell me, if these instructions donīt work for you.

After unpacking the archive do the usual

./configure
make
make install
The install step will most likely require root status. If configure fails to locate your JDK then try ./configure --with-java=<JDK base-directory>.
Include the files Java/SyncBuilder.jar and Java/jndi.jar into your CLASSPATH environment variable. Then check for successful installation.

Checking for successful installation

Make sure the current directory (.) is included in your CLASSPATH environment variable! Then change to the Java/samplecode directory. Execute java dlptest. This will run the Palm device through a short series of tests.

Checking Serial HotSync

This will only work if you did the installation of the native code. When asked for the port on which your Palm device is connected, choose the UNIX device-name of the serial port to which the cradle is connected (e.g. /dev/ttyS0, or /dev/pilot).
While the instructions and explanations are being displayed, be sure not to wait too long to press <RETURN>, otherwise the connection will time out!

Checking Network HotSync

This will work for both the pure Java installation as well as the native installation. You will have to install the Network HotSync software on your Palm device though, and run the pppd (both is described here).
When asked for the port to which your Palm device is connected choose . (dot). You will then be asked to instantiate the Network HotSync. You do this by tapping on the "Modem HotSync" symbol on your Palm device . The pppd should already be running before you start the Java application.

Troubleshooting

java.lang.UnsatisfiedLinkError: no JavaPisock in shared library path
The native code for the Java-binding could not be located. If you have only done the binary installation this will happen anytime you try to access functionality that requires native support code (e.g. synchronization through the serial cable).
If you have successfully installed the source version though then you should try to manually add libsock/_libs and Java/_libs to your LD_LIBRARY_PATH. You might also have to run ldconfig as root, to make the new library known to the system.
java.lang.UnknownError
        at Pdapilot.ServerSocket.bind(ServerSocket.java:xx)
        at Pdapilot.ServerSocket.(ServerSocket.java:xx)
        at pltests.fulldemo.main(fulldemo.java:xx)
The specified port for the Palm device could not be found. The default is /dev/pilot, which is probably not present on your system. You might wish to create /dev/pilot by typing ln -s /dev/ttyS0 /dev/pilot.