summaryrefslogtreecommitdiffabout
path: root/bin
authorulf69 <ulf69>2004-10-22 22:32:54 (UTC)
committer ulf69 <ulf69>2004-10-22 22:32:54 (UTC)
commitbcad4a526b3bc04a4889e6bbbe9b73731a5aacf5 (patch) (side-by-side diff)
tree6cc7ceb9829e6e2412fd1320b9292ec443a8d21b /bin
parent6b99c0feac04963f814a32586268ecac966f3d51 (diff)
downloadkdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.zip
kdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.tar.gz
kdepimpi-bcad4a526b3bc04a4889e6bbbe9b73731a5aacf5.tar.bz2
added references to PWM/Pi
Diffstat (limited to 'bin') (more/less context) (show whitespace changes)
-rw-r--r--bin/kdepim/SyncHowto.txt25
1 files changed, 13 insertions, 12 deletions
diff --git a/bin/kdepim/SyncHowto.txt b/bin/kdepim/SyncHowto.txt
index ec5513a..5874fc3 100644
--- a/bin/kdepim/SyncHowto.txt
+++ b/bin/kdepim/SyncHowto.txt
@@ -4,7 +4,7 @@ IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM
THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES
HAVE TOO MUCH DIFFERENCE.
-In other words: Please make shure, that the clocks of the devices
+In other words: Please make sure, that the clocks of the devices
you want to sync have only a difference of some seconds!
@@ -23,28 +23,29 @@ CONTENT:
Note:
The recommended and easiest way to syncronize two devices where
-KO/Pi or KA/Pi is installed, is the profile kind "Pi-Sync".
+KO/Pi, KA/Pi or PWM/Pi is installed, is the profile kind "Pi-Sync".
Details about that in 5) b).
-In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook
-with another calendar/addressbook , by syncing your
-(local) calendar/addressbook with a (remote) file.
+In KDE-Pim/Pi you can synchronize ( sync ) your calendar/addressbook/
+passwordfile with another calendar/addressbook/passwordfile,
+by syncing your (local) calendar/addressbook/passwordfile
+with a (remote) file.
This remote file may on your local filesystem
or on another (remote) device.
-If you want to sync with another remote device,
-you have two create a sync profile.
+If you want to sync with another remote device, you have to create
+a sync profile.
You have two choices for choosing the profil kind:
-I) You have to choose profile kind "Remote file" and to specify a
+I) You can choose profile kind "Remote file" and specify a
command line download/upload command ( like scp, ftp, ...) to
a) download the remote file to your local machine to a temp file
b) sync with this temp file
c) upload the synced file to the remote device
-II) If you want to sync with a device, where KO/Pi( or KA/Pi ) is
+II) If you want to sync with a device, where KO/Pi( or KA/Pi, PWM/Pi) is
installed, you can easily get the remote file via network
with the build in file transfer feature:
Choose profile kind "Pi-Sync" and
- a) Start KO/Pi or KA/Pi on remote device and
+ a) Start KO/Pi,KA/Pi or PWM/Pi on remote device and
enable "Pi-Sync" on remote device with password and port.
b) Specify password, port and IP address in your profile.
@@ -55,8 +56,8 @@ Everything is explained in more details below.
NOTE:
If you do not use profile kind "Pi-Sync",
it is recommended to close
-a running KO/Pi ( or KA/Pi) on the remote device.
-(Note: KO/Pi( or KA/Pi) running on Zaurus with
+a running KO/Pi (KA/Pi, PWM/Pi) on the remote device.
+(Note: KO/Pi(KA/Pi, PWM/Pi) running on Zaurus with
FastLoad enabled will never be closed!)
After syncing with a running KO/Pi on the remote device,
a "save" on the remote device will tell you that it needs to merge (sync).