summaryrefslogtreecommitdiffabout
path: root/bin
authorzautrix <zautrix>2004-10-26 14:00:36 (UTC)
committer zautrix <zautrix>2004-10-26 14:00:36 (UTC)
commitb20ce8d246ff4662bd33dccfc98a75aece6705b1 (patch) (unidiff)
tree3acd33b8208906aa7689db22abb66ec36d72d90c /bin
parent2430740ac3cb72296c3131dd11736408cc7fa4ce (diff)
downloadkdepimpi-b20ce8d246ff4662bd33dccfc98a75aece6705b1.zip
kdepimpi-b20ce8d246ff4662bd33dccfc98a75aece6705b1.tar.gz
kdepimpi-b20ce8d246ff4662bd33dccfc98a75aece6705b1.tar.bz2
added another sync howto
Diffstat (limited to 'bin') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/Zaurus-KDE_syncHowTo.txt251
1 files changed, 251 insertions, 0 deletions
diff --git a/bin/kdepim/Zaurus-KDE_syncHowTo.txt b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
new file mode 100644
index 0000000..90c6237
--- a/dev/null
+++ b/bin/kdepim/Zaurus-KDE_syncHowTo.txt
@@ -0,0 +1,251 @@
1
2Sync HowTo Zaurus <-> KDE
3
4NOTE:
5CURRENTLY ONLY SYNCING OF CALENDAR DATA IS SUPPORTED!
6
7This is a
8Sync HowTo Zaurus <-> K-Desktop Environment(KDE)
9using the KDE-Pim/Pi applications
10KAddressbook/Pi (KA/Pi) and KOrganizer/Pi (KO/Pi)
11on the Zaurus (Z).
12
13You can now easily sync your Z with the
14PIM data of the KDE.
15(addressbook and calendar data).
16You need to install the desktop versions
17of KA/Pi+KO/Pi on the desktop.
18You need KDE version 3.3.0 or higher on your desktop.
19You need KA/Pi+KO/Pi version 1.9.11 or higher on the desktop
20and on the Z.
21
22NOTE: Almost the same procedure will make it possible to
23sync KA/Pi+KO/Pi running on Windows with KDE via network.
24
25The setup+sync procedure is:
26
271) Installing KA/Pi+KO/Pi on the Z
282) Installing desktop version of KA/Pi+KO/Pi on the desktop
293) Connection your Z to the desktop via network
30 (network connection can be set up via USB cable or (W)Lan
314) Configuring KA/Pi+KO/Pi on Z for Sync
325) Enable remote sync in KA/Pi+KO/Pi on the desktop
336) Sync
34
35
36*****************************************************
371) Installing KA/Pi+KO/Pi on the Z
38*****************************************************
39
40Download latest version of KA/Pi+KO/Pi from
41http://sourceforge.net/projects/kdepimpi/
42Project KDE/Pim.
43Direct link is:
44http://sourceforge.net/project/showfiles.php?group_id=104103&package_id=112604
45Click on the version number to read the release notes/change log.
46Choose there the right precompiled package for your Z:
47For Sharp ROM
48-File: kdepim_1.x.xx_for_SharpROM.ipk.zip
49For Open Zaurus ROM:
50-File: kdepim_1.x.xx_for_OZ-gcc3xx.ipk.zip
51If unsure, choose:
52-File: kdepim_1.x.xx_for_SharpROM.ipk.zip
53
54Unzip the file and install the packages as usual on your Z.
55In order to intstall KA/Pi+KO/Pi on your Z,
56you need to install the following files:
57kmicrokdelibs_1.x.xx_arm.ipk
58kaddressbook_1.x.xx_arm.ipk
59korganizer_1.x.xx_arm.ipk
60
61*****************************************************
622) Installing desktop version of KA/Pi+KO/Pi on the desktop
63*****************************************************
64
65Precompiled packages are available for SuSE 9.1.
66Choose on the above download location:
67File: KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm
68Download file and install it on console with
69su
70rpm -ihv KDE-Pim-Pi-1.9.10-SuSE9.1.i586.rpm
71
72NOTE for users of SuSE 9.1:
73You need KDE version 3.3.0 or higher on your desktop.
74Plese make an online update in SuSE (YAST), then update
75your KDE to version 3.3.0 or higher.
76You can find links to updated precompiled versions of KDE
77for SuSE 9.1 on the SusE web site,
78a direct link is for example:
79ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.1
80HOWTO UPDATE KDE:
81Download there the packages in "base".
82And the needed package for your language in "internationalization".
83Put all downloaded files in one "installation" directory.
84Open console and go to the downloaded "installation" directory.
85Do there a
86su
87and then perform a test for the update:
88rpm -Uhv --test *.rpm
89
90If no dependencies are shown, you can do the actual update with
91rpm -Uhv *.rpm
92
93If there are missing dependencies, you can resolve them by
94- download the needed updated KDE package from the
95 "applications" or from the "development" folder on the server.
96- adding a needed rpm package from the SuSE install DVD
97- remove the package that has dependencies from your "installation" directory.
98
99Do the
100rpm -Uhv --test *.rpm
101until you get no dependencies and no errors, then do a
102rpm -Uhv *.rpm
103Run
104SuSEconfig
105after installing with rpm is finished.
106Restart KDE.
107
108*****************************************************
1093) Connection your Z to the desktop via network
110 (network connection can be set up via USB cable or (W)Lan
111*****************************************************
112
113a) Connection via network cable/(W)Lan cards
114 Connect your desktop to the network.
115 Set up networking on the Z.
116 Make sure, you can ping the desktop from Z.
117b) Connection via USB cable:(is working for Z 7x0 and Z5500)
118 (i) Open console on desktop and type
119 su
120 tail -f /var/log/messages
121 (ii) Connect your Z with the USB cable to your desktop
122 You should get as output in the above console
123 something like this:
124 ("BUG" is the name of the desktop computer!)
125 Oct 26 12:49:37 BUG kernel: usb 2-2: new full speed USB device using address 2
126 Oct 26 12:49:37 BUG kernel: usb 2-2: Product: SL-C860
127 Oct 26 12:49:37 BUG kernel: usb 2-2: Manufacturer: Sharp
128 Oct 26 12:49:37 BUG /etc/hotplug/usb.agent[22659]: need a device for this command
129 Oct 26 12:49:43 BUG kernel: usb0: register usbnet at usb-0000:00:1d.0-2, Sharp Zaurus, PXA-2xx based
130 Oct 26 12:49:43 BUG kernel: usbcore: registered new driver usbnet
131 You see in the 5. line ("BUG kernel: usb0: register"), that usb device usb0 is used.
132 (iii) Create a network startup entry in /etc/sysconfig/network
133 Depending of the number X of the used usb device, create a file
134 /etc/sysconfig/network/ifcfg-usbX
135 (in our case /etc/sysconfig/network/ifcfg-usb0 )
136 with the following content:
137 # usbX config for Zaurus
138 IPADDR='192.168.129.200'
139 NETMASK='255.255.255.0'
140 NETWORK='192.168.129.0'
141 BROADCAST='192.168.129.255'
142 STARTMODE='hotplug'
143 (iv) Disconnect the Z and connect the Z again to the desktop.
144 Now you should be able to ping the Z from the desktop, try in console on desktop:
145 ping 192.168.129.201
146 Now you should be able to ping the desktop from the Z, try in console on Z:
147 ping 192.168.129.200
148
149 Now you will get a network connection automatically,
150 if you connect your Z to the desktop via the USB cable.
151
152
153In the following, we assume, that
154the desktop has the IP address: 192.168.129.200
155and that
156the Z has the IP address: 192.168.129.201
157
158*****************************************************
1594) Configuring KA/Pi+KO/Pi on Z for Sync
160*****************************************************
161
162Start KO/Pi on the Z.
163Choose Menu: Synchronize - Configure
164Fill in name for "Local device name:", e.g. "Z760"
165Click on "New profile"
166Set name of "Profile:", e.g. "BUG".
167(that is the above name of the desktop computer)
168Choose "Profile kind": Pi-Sync.
169Set "Password for remote access", e.g. "xyz" for
170Calendar and Addressbook.
171Set Remote IP address to 192.168.129.200 for
172Calendar and Addressbook.
173(Note: That is the IP address of the desktop!).
174The "Remote port number" is 9197/9198 for
175Calendar and Addressbook.
176You do not have to change the
177"Remote port number" or any other settings.
178Click "OK" button to save your settings.
179
180Now you have configured KA/Pi+KO/Pi sync on the Z,
181no need to configure anything in KA/Pi.
182
183
184*****************************************************
1855) Enable remote sync in KA/Pi+KO/Pi on the desktop
186*****************************************************
187
188Start KO/Pi on the desktop.
189Do a "test" sync with KDE, choose menu:
190Synchronize - KDE_Desktop
191After syncing, you should have the same data in KDE
192and in KO/Pi.
193NOTE:
194The KO/Pi version 1.9.10 had the bug, that on the first
195sync with KDE, all data in KDE was deleted.
196DO NOT USE VERSION 1.9.10!
197
198The bevaviour on the first sync is
199(in versions >= 1.9.11)
200that no data is deleted, the data in KO/Pi and in
201KDE is merged into one calendar.
202
203When the first sync was ok, please choose menu:
204Synchronize - Enable Pi-sync
205Fill in the values for port ("9197" in our examle)
206and for the password ( "xyz" in our example)
207that you did configure on the Z for that computer.
208Enable "Automatically start at application start"
209and "Automatically sync with KDE-Desktop when receiving sync request"
210by checking the two boxes.
211Close KO/Pi.
212
213Configure / test KA/Pi on the desktop in the same way.
214Fill in the right value for the port (9198 in our examle)
215in KA/Pi!
216
217*****************************************************
2186) Sync
219*****************************************************
220
221After configuring everything as above, you have to do
222the following, if you want to sync your Zaurus with KDE:
223(It syncs will all resources in KDE, that are not "readonly").
224
225Start KO/Pi on the desktop.
226Connect the Z with the USB cable to your desktop.
227(Or to the local network).
228Choose on the Z the menu:
229Syncronize - <your name for the desktop sync profile>
230( that was "BUG" in our example ).
231That's all.
232
233Do the same with KA/Pi.
234
235NOTE:
236If an appointment/addressee is created on the Z, it is added to the
237standard resource in KDE.
238
239If you have todos with subtodos in your calendar, you will get on
240every sync (after you restartet KOrganizer or Kontact in KDE)
241the message "xx items changed on local", where
242xx is greater or equal to the number of todos.
243That behaviour is caused by a bug in KDE.
244(In KDE, everytime a subtodo is loaded,
245it's "last modified" settings are set to the current time - ouch!)
246I hope that bug will be fixed soon.
247
248
249
250
251