The latest documentation for this package is available on the
web at:

	http://pilotmanager.sourceforge.net/



                           PilotManager Installation

UPGRADING FROM 1.107

   Please note the following changes if upgrading from PilotManager version
   1.107:

     * Remember to back up your data before upgrading, as new bugs may have
       been introduced. pilot-xfer -u may be helpful for backing up the
       contents of your Palm; files to back up on the unix side include all
       of the ~/.pilotmgr directory, and any files used by the applications
       you sync with, e.g. netplan.dir/username if you use SyncPlan.

     * PilotManager still requires The Tk and PDA::Pilot perl modules, but
       they are no longer distributed with it. You may need to install them
       separately (see PREREQUISITES).

     * The shell script Setup has been replaced by a perl script Setup.pl.

     * When you unpack the tarball, you will no longer see a PilotManager
       executable. Do "perl Setup.pl" to generate PilotManager.

     * The setup script now accepts an optional -conduitdir argument. If you
       use third-party conduits that are distributed separately from
       PilotManager, you can now install them in a separate directory, and
       give the name that directory as the -conduitdir argument. This will
       subsequently allow you to upgrade PilotManager without reinstalling
       the third-party conduits. See installation instructions below for an
       example.

     * In past versions, if there were conduits that failed to load properly,
       you needed to delete or rename them or else PilotManager would print
       error messages every time it started up. This is no longer
       necessary--PilotManager doesn't attempt to load modules that haven't
       been activated in the Preferences dialog.

PREREQUISITES

   If you're impatient, you can skip this section and just try installing and
   running PilotManager. The necessary prerequisites are already installed on
   some systems. If you get errors about missing perl modules, come back here
   to resolve them.

   Earlier versions of PilotManager were distributed with the perl modules
   Tk, MD5, IO, and PDA::Pilot. These are not part of PilotManager, but
   rather libraries written by other authors that are maintained separately.
   These packages are no longer distributed with PilotManager. If you get
   error messages about one of these packages being unavailable, then you
   will need to install it yourself.

     * This version of PilotManager uses Digest::MD5 instead of MD5. You
       probably already have Digest::MD5, because it's included in the base
       perl distribution nowadays. If you have an older perl that doesn't
       include it, you can download it from http://search.cpan.org/.

     * The IO module is also included in recent perl distributions, and the
       same instructions apply.

     * The Tk perl module (not to be confused with the Tk C libraries--the
       former is a perl interface to the latter) is included in some perl
       distributions, e.g. ActiveState, and RPM packages (often called
       perl-Tk) are available for many linux distributions. If you don't have
       it, then download it from http://search.cpan.org/. PilotManager 1.108
       is known to be compatible with Tk-804.027 and Tk-800.026. The Tk
       documentation recommends using Tk-800.026 if your perl is older than
       5.8.0.

     * The PDA::Pilot module is part of the pilot-link library from
       http://www.pilot-link.org/. PilotManager 1.108 is known to be
       compatible with pilot-link 0.11.8 and 0.12.0-pre5.

       pilot-link's default configuration does not include the perl module.
       Due to a bug in the configure script, it is best to avoid using the
       --with-perl configuration option. Rather, compile and install
       pilot-link as usual without the perl bindings; then in the
       bindings/Perl directory, do "perl Makefile.PL" (you can specify
       various options here, e.g. "perl Makefile.PL PREFIX=/usr/local"), then
       "make" and "make install".

       Many linux distributions include the pilot-link libraries, but some do
       not include the PDA::Pilot perl module. Therefore, may find you need
       to download and install pilot-link even if a pilot-link RPM is already
       installed. (It might be best to uninstall the RPM to avoid confusion
       between different versions.)

INSTALLATION

   In the simplest case, unpack the tarball and do

     perl Setup.pl

   This creates the executable PilotManager, which you can then run. It can
   be run in place, i.e. there is no "make install" step. If you want to
   install it somewhere other than where you unpacked it, simply copy the
   whole directory.

   That's all, unless you use third-party conduits, i.e. modules like
   SyncBBDB that are distributed separately from PilotManager. In that case,
   you may give Setup.pl a -conduitdir argument that names a directory where
   such conduits are installed. For example,

     perl Setup.pl -conduitdir /usr/local/lib/pilotmgr-conduits

   The installation instructions for some conduits may direct you to install
   them in the pilotmgr-x.xxx directory (the directory that is created when
   you unpack the tarball). As of PilotManager 1.108, you can install them in
   the -conduitdir directory. This is preferable because it will allow you to
   avoid reinstalling the conduits the next time you upgrade PilotManager.

CONFIGURATION

   Run PilotManager and open the Preferences dialog (under the File menu). To
   configure a conduit, put it on the Active Conduits list, select it, and
   click Configure. See [2]http://pilotmanager.sourceforge.net/conduits.html
   for details on the various conduits.

   If you get an error message when trying to move a conduit from the Active
   to the Inactive list, fix the problem and restart PilotManager before
   trying again.

   The "Pilot Port" field:

     * If syncing via a serial port, choose the appropriate device name from
       the pop-up menu, or select "Other" and type in the device name.

     * If syncing via USB on a linux system, there are two possibilities:

          * If your system has the "visor" kernel module installed, you can
            sync via a usbserial device, typically /dev/ttyUSB0 or
            /dev/ttyUSB1. Experiment to find the right one.

          * If you have libusb installed and pilot-link 0.12.0 or later, set
            Pilot Port to "usb:". pilot-link 0.11.8 and earlier do not
            support libusb.

     * If syncing via USB on a Solaris system, libusb is currently the only
       option. See above.

   The "Comm speed" field: some serial ports are unreliable at high speeds,
   so try a lower one if you have problems.. The speed setting has no effect
   for USB.

RUNNING

   After you have read the instructions for all configured conduits and made
   the recommended backups, press the Hotsync button on PilotManager and then
   on your handheld device.

TROUBLESHOOTING

   PilotManager depends on the pilot-link libraries to communicate with the
   handheld, so if pilot-link isn't working then PilotManager won't either.
   Try testing with "pilot-xfer -l", and see [3]http://www.pilot-link.org/ .

   For PilotManager-specific help, see
   [4]http://pilotmanager.sourceforge.net/ .



References

   Visible links
   1. file:///home/kaplan/pilot-manager-devel/web/pilotmanager-web/index.html
   2. http://pilotmanager.sourceforge.net/conduits.html
   3. http://www.pilot-link.org/
   4. http://pilotmanager.sourceforge.net/
   5. http://sourceforge.net/
