summaryrefslogtreecommitdiffabout
path: root/bin/kdepim/korganizer/howtoSYNC.txt
authorzautrix <zautrix>2004-10-06 11:28:57 (UTC)
committer zautrix <zautrix>2004-10-06 11:28:57 (UTC)
commitcbee622faf1a76e4d8f7bb88d87efb49ef3bb631 (patch) (side-by-side diff)
tree007231e4800c7b4197c51f27459615d3867d7372 /bin/kdepim/korganizer/howtoSYNC.txt
parentd0cf120f92aaf6820457f4e13cfcd26005cfa0bc (diff)
downloadkdepimpi-cbee622faf1a76e4d8f7bb88d87efb49ef3bb631.zip
kdepimpi-cbee622faf1a76e4d8f7bb88d87efb49ef3bb631.tar.gz
kdepimpi-cbee622faf1a76e4d8f7bb88d87efb49ef3bb631.tar.bz2
updated sync howto
Diffstat (limited to 'bin/kdepim/korganizer/howtoSYNC.txt') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/korganizer/howtoSYNC.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt
index ad765d3..d3046de 100644
--- a/bin/kdepim/korganizer/howtoSYNC.txt
+++ b/bin/kdepim/korganizer/howtoSYNC.txt
@@ -272,48 +272,50 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
Fill in the needed values:
- Password for remote access:
The password you specified on the remote device.
- Remote IP address:
The IP address of the remote device.
- Remote port number:
The port number you specified on the remote device.
Now you can syncronize your local device easily with your
remote device. This works well for all platforms KO/Pi is
running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
is now very easy.
c) Remote file
Syncing with the profile kind "Remote file" is performed in three steps:
i) download the remote file to your local machine to a temp file
ii) sync with this temp file
iii) upload the synced file to the remote device
The down-/uploading if i) and iii) is done via a command line command.
Please specify the download/upload command ( like scp, ftp, ...) and the
file name of the temp file in the corresponding fields.
d) Mobile device (cell phone)
+ Note: On the Zaurus you have to install the kammu_xxx_arm.ipk package
+ to be able to access mobile phones.
We mention here only KO/Pi, but the same is valid for KA/Pi.
Note:
It is only possible to sync a mobile phone with one particular device
running KO/Pi. If you want to be able to write data of more than one device
to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
do not sync with the mobile phone at all, but use the
"Export to phone" functionality from the different devices.
Using "Export to phone" makes it not possible to get back data from the
phone, if it was changed there, of course.
If you sync with the phone, do not use "Export to phone" from any device.
(And do not sync, as mentioned above, from any other device with that phone).
It would delete the needed information for syncing with that phone!
We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
for accessing the phones.
Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because
we have modified the original version to make it useable for syncing!
Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...).
The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared).
Bluetooth access is disabled on the Zaurus, but may work on Windows.
Please look at the Gammu homepage and documentation about more details
configuring Gammu how to access your phone.
If you have problems accessing your phone, start KO/Pi from the konsole
and you will get a more detailed output what went wrong.