|This page is hopelessly outdated. Please do not use it!|
All the documentation included with the Pilot for connecting it to a desktop computer refers to PCs and Macs. Unix users are dutifully ignored. So a wonderful bunch of people has set to develop all the software necessary to use their Pilots without having to connect or use inferior computing platforms.
However, as the software is still under development, the documentation is sparse, and the procedure to make things work is sometimes not very clear. Since I have been asked a lot of times how to do it, I put together this page, which contains instructions based on my experience.
Please note that I use Solaris 2.5.1 on a Sparc machine, so my instructions are specific to this platform. The instructions should be general enough to work on almost any Unix platform, but you may have to discover some details by yourself. Of course, if you do, please send them to me! Then we can make this page better by adding system-specific details.
In Sparc[5,10,20] and Ultra machines: you have two serial ports, which are labeled "A" and "B" in the back of your machine, and they are 25-pin female connectors.
In a Sun IPC (maybe IPX and Classic also, if someone has access to one of those please confirm) the serial ports are labeled "1" and "2" (if memory serves me correctly, that is my home machine) and they are 8-pin female mini-DIN connectors, such as those found in Macs.
For a Sparc/Ultra, you can get a 9-pin-male to 25-pin male converter, or use the 9-pin-male to 25-pin-female one included with your Pilot, and get a 25-pin-male to 25-pin-male gender changer.
For Solaris, they will usually be /dev/ttya or /dev/ttyb.
For Linux, they may be /dev/cua0 or /dev/cua1.
To compile and install pilot-link:
gunzip -c pilot-link.x.y.z.tar.gz | tar xvf -
You can give options to configure to change parameters such as the base directory where things will be installed (/usr/local by default) and others. Do a ./configure --help for all the options.
./pilot-xfer port -l
where port is the device to which your Pilot cradle is connected. Put the Pilot in the cradle, press the HotSync button, and if things are ok, you will see a listing in the screen of all the databases installed in your Pilot.
make Perl make Java make Tcl make Python
You can also cd to each directory, make and make test. Usually the test program will ask you to put your Pilot in the cradle and press the HotSync button, and will read some databases or something like that.
I have only been successful with the Perl and Java bindings. The Tcl keeps crashing when I run the test, and I haven't tried Python.
pilot-xfer port -i file.prc
Where port is the device file for the port where your cradle is connected.
Most programs in the pilot-link package understand the following environment variables, so if you set them, you can usually leave the arguments out when invoking the commands:
PILOTPORT for specifying the port where the cradle is connected.
PILOTRATE for specifying the rate at which to transfer data. The default is 9600 baud, which can be slow. I normally use 38400, which is the higher with which most people report success.
pilot-mail /dev/ttya -m ~/Mail/topilot -d delete -k delete
Actually, I specify all the information in the appropriate environment variables, which are given in the help screen.
I know of no easy way of downloading email from a standard Unix mailbox to the Pilot. A temporary workaround could be, if you have the MH software installed, to use the inc command to convert the mailbox to an MH mailbox and use pilot-mail as described above.
"last","first","title","company","work","home","fax","other", "email","address","city","state","zip","country","custom1", "custom2","custom3","custom4","note","0"
this is, the order in which the fields appear in the PhoneBook application, each value in double quotes, separated by commas. The "note" is the optional note you can add to each record. The "0" at the end, I suppose, is for marking it as non-private. Every record has to be in a single line, but you can have as many records per file as you want.
You can use this, for example, if you already have an address book in some other format, to put it all in your Pilot.
There is one slightly non-intuitive thing with this program, and it is that the -r option is used to "read from the file, and write to the Pilot", while the -w option means to "read from the Pilot, and write to the file". I found it confusing, you may not, but be careful not to wipe out things inadvertently.
This is where PilotManager comes in. It is a graphical application (written in Perl/Tk) developed by Bharat Mediratta, that provides a framework for running conduits that synchronize different types of data. Currently, conduits exist for backing up the contents of your Pilot, for installing new files, and for synchronizing the Date Book (transferring data in format of Sun's calendar manager) and Memo Pad (storing the files as ASCII files in a specified directory).
One problem with PilotManager is that currently it runs only under Solaris. Sources are provided, but you are mostly on your own if you want to port it to other system. In the latest version (1.100-BETA-6), the SyncCM conduit requires the CSA library and rpc.csmd server included Solaris 2.6, and which is optional in Solaris 2.5.1. So you may have to install it first if you haven't.
However, if you have a Solaris machine, good news! PilotManager is very easy to install and run:
PilotManagerfile, and change the first line to reflect the location of your Perl interpreter.
cdto the directory where you unpacked PilotManager.
cd lib/perl5/[arch], where [arch] will be
sun4-solarisor something similar, depending on your architecture.
mv 5.003 `perl -e 'print $]'`
PilotManager. If everything is ok, you should see the main window. Select the "Properties" menu item, select the appropriate port and speed you want to use, select and configure the conduits you want to run.
Last modified: Mon Aug 2 14:51:44 EST 1999