Gnome-Pilot
-----------

This is a ultra short thingie about Gnome-Pilot.

Gnome-Pilot is a package with a daemon (gpilotd) that monitor for
pilot connects on one or more devices (cradles/XCopilots/xxx). It has
a conduit system, and is accompanied by a few conduits, basically for
installing files and backing up db's from the pilot.

A few more interesting conduits exist, eg. the email conduit.

Requirements
------------

If you at any point get something about a missing "pisock" library, you
need the pilot-link package, go to ftp://ryeham.ee.ryerson.ca/pub/PalmOS/ 
for newest .tar.gz of pilot-link.

Compiling from CVS
------------------

As other gnome software, run autogen.sh with appropriate flags and
then "make".

For users with RedHat systems, who have used precompiled rpms, you'll
probably want to run autogen.sh like this
 $ ./autogen.sh --prefix=`gnome-config --prefix` --sysconfdir=`gnome-config --sysconfdir`
Or use the build.sh script in the gnome-pilot dir. 

Compiling from tar.gz
---------------------

There should be a configure script included, run with appropriate
flags and then "make". 

Again, you might want to add "--prefix=`gnome-config --prefix`"
and "--sysconfdir=`gnome-config --sysconfdir`" to the configure flags.

Installing
----------

If you installed from a rpm, you're already past this, if from source;
after a successfull make, run "make install".

Setting up
----------

Run gnomecc (the control-center), and under Peripherals->PalmPilot
choose "Pilot Link". 

Your machine is assigned a random SyncId number, this number isn't
important, it just has to be unique for each machine that you sync
with (so no, it doesn't have to be a unique number in the world).

Choose a device, typically /dev/pilot, which is a link to
eg. /dev/ttyS0 or another serial port, can also be a device used by
XCopilot for testing.

Click "Try", the "get from pilot" and "send to pilot" buttons in the
pilot info box should now activate, plus gpilotd is restarted with the
new device. If you have used your pilot with windows software, the
pilot will probably already have a ID number and a name. If, click
"get from pilot" to retrieve. A box should pop up, asking you to press
do, do this. Note "Pilot Name" is a symbolic name to reference your
pilot, leave it as "My Pilot" or whatever, its like the name of your
machine.

If you haven't used the pilot under windows, you can use the default
settings, which are your uid as Pilot ID and your name as in
/etc/passwd as user name. Clicking "send to pilot" stores the settings
in the pilot.

XCopilot testing
----------------

XCopilot is a pilot emulator for X Windows. It can be found at
http://xcopilot.cuspy.com/. To use XCopilot, you'll need a copy of
your pilots rom image. In the pilot-link package, there is a small
utility called getrom, and a Pilot program to extract the rom.

Run XCopilot with the -serial option, it will write something like
"Serial I/O on /dev/ptyqe". Now set gpilotd to use /dev/ttyqe for
device (or "ln -sf /dev/ttyqe /dev/copilot"). You can now sync your
XCopilot, great for testing/debugging.

Conduit configuring
-------------------

You can now configure the conduits. Each capplet should at least show
a "Enabled" button. If the setting is lost after terminating the
capplet, something is wrong...

Something is wrong...
---------------------

When bugreporting, use http://bugs.gnome.org, also do the following :
do a "killall gpilotd;killall -9 gpilotd;rm ~/.gpilotd.pid". This
should really kill gpilotd. Now run gpilotd from a console, and
capture the output, great help for the author. Also do a "ps ax|grep
gpilotd" to ensure no processes are running.

Now retry the capplet/applets/whatever, and at least now the gpilotd
output will be visible. Please include the output and your
configuration files (in ~/.gnome/gnome-pilot.d) in the bug report.

Also, check the homepage at http://www.gnome.org/gnome-pilot.

Even more important, if you have problems, check the gnome-pilot
mailing list, address and subscription info can be found at
http://www.gnome.org/mailing-lists/index.shtml. Asking for help
on this list rather then mailing the authors list may be quicker
way for yielding a response.

Thats it for now...

Eskil - 1999. (deity@eskil.dk)
