summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (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
@@ -248,96 +248,98 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
248 with the build in file transfer feature "Pi-Sync": 248 with the build in file transfer feature "Pi-Sync":
249 You have first to enable file transfer on the remote device: 249 You have first to enable file transfer on the remote device:
250 - Start KO/Pi on the remote device. 250 - Start KO/Pi on the remote device.
251 - Choose Menu Synchronize-Enable Pi-Sync. 251 - Choose Menu Synchronize-Enable Pi-Sync.
252 - Choose a port number, where KO/Pi should listen for 252 - Choose a port number, where KO/Pi should listen for
253 file sending requests. Valid port numbers are numbers 253 file sending requests. Valid port numbers are numbers
254 between 1 and 65565. Do not specify port numbers, that are 254 between 1 and 65565. Do not specify port numbers, that are
255 used by other applications. A port number between 9000 and 9999 255 used by other applications. A port number between 9000 and 9999
256 is most likely not used by another application. 256 is most likely not used by another application.
257 The default port number is 9197 for KO/Pi. 257 The default port number is 9197 for KO/Pi.
258 If you specify a port number, which is already in use, 258 If you specify a port number, which is already in use,
259 you will get an error message when closing this dialog. 259 you will get an error message when closing this dialog.
260 - Choose a password. 260 - Choose a password.
261 - Click OK. 261 - Click OK.
262 Now KO/Pi will send the calendar data via the network, 262 Now KO/Pi will send the calendar data via the network,
263 if some other device is sending a "please send calendar" 263 if some other device is sending a "please send calendar"
264 request on the given port using the given password. 264 request on the given port using the given password.
265 If you want to be sure, nobody can access your calendar 265 If you want to be sure, nobody can access your calendar
266 data, simply disable the file transfer feature on the 266 data, simply disable the file transfer feature on the
267 remote device after the syncing is done by choosing: 267 remote device after the syncing is done by choosing:
268 Menu Synchronize-Disable Pi-Sync. 268 Menu Synchronize-Disable Pi-Sync.
269 269
270 On your local device, create a new profile and choose 270 On your local device, create a new profile and choose
271 profile kind "Pi-Sync". 271 profile kind "Pi-Sync".
272 Fill in the needed values: 272 Fill in the needed values:
273 - Password for remote access: 273 - Password for remote access:
274 The password you specified on the remote device. 274 The password you specified on the remote device.
275 - Remote IP address: 275 - Remote IP address:
276 The IP address of the remote device. 276 The IP address of the remote device.
277 - Remote port number: 277 - Remote port number:
278 The port number you specified on the remote device. 278 The port number you specified on the remote device.
279 279
280 Now you can syncronize your local device easily with your 280 Now you can syncronize your local device easily with your
281 remote device. This works well for all platforms KO/Pi is 281 remote device. This works well for all platforms KO/Pi is
282 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows 282 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
283 is now very easy. 283 is now very easy.
284 284
285c) Remote file 285c) Remote file
286 Syncing with the profile kind "Remote file" is performed in three steps: 286 Syncing with the profile kind "Remote file" is performed in three steps:
287 i) download the remote file to your local machine to a temp file 287 i) download the remote file to your local machine to a temp file
288 ii) sync with this temp file 288 ii) sync with this temp file
289 iii) upload the synced file to the remote device 289 iii) upload the synced file to the remote device
290 290
291 The down-/uploading if i) and iii) is done via a command line command. 291 The down-/uploading if i) and iii) is done via a command line command.
292 Please specify the download/upload command ( like scp, ftp, ...) and the 292 Please specify the download/upload command ( like scp, ftp, ...) and the
293 file name of the temp file in the corresponding fields. 293 file name of the temp file in the corresponding fields.
294 294
295d) Mobile device (cell phone) 295d) Mobile device (cell phone)
296 Note: On the Zaurus you have to install the kammu_xxx_arm.ipk package
297 to be able to access mobile phones.
296 We mention here only KO/Pi, but the same is valid for KA/Pi. 298 We mention here only KO/Pi, but the same is valid for KA/Pi.
297 Note: 299 Note:
298 It is only possible to sync a mobile phone with one particular device 300 It is only possible to sync a mobile phone with one particular device
299 running KO/Pi. If you want to be able to write data of more than one device 301 running KO/Pi. If you want to be able to write data of more than one device
300 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) 302 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
301 do not sync with the mobile phone at all, but use the 303 do not sync with the mobile phone at all, but use the
302 "Export to phone" functionality from the different devices. 304 "Export to phone" functionality from the different devices.
303 Using "Export to phone" makes it not possible to get back data from the 305 Using "Export to phone" makes it not possible to get back data from the
304 phone, if it was changed there, of course. 306 phone, if it was changed there, of course.
305 If you sync with the phone, do not use "Export to phone" from any device. 307 If you sync with the phone, do not use "Export to phone" from any device.
306 (And do not sync, as mentioned above, from any other device with that phone). 308 (And do not sync, as mentioned above, from any other device with that phone).
307 It would delete the needed information for syncing with that phone! 309 It would delete the needed information for syncing with that phone!
308 310
309 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ ) 311 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
310 for accessing the phones. 312 for accessing the phones.
311 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because 313 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because
312 we have modified the original version to make it useable for syncing! 314 we have modified the original version to make it useable for syncing!
313 Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...). 315 Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...).
314 The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared). 316 The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared).
315 Bluetooth access is disabled on the Zaurus, but may work on Windows. 317 Bluetooth access is disabled on the Zaurus, but may work on Windows.
316 Please look at the Gammu homepage and documentation about more details 318 Please look at the Gammu homepage and documentation about more details
317 configuring Gammu how to access your phone. 319 configuring Gammu how to access your phone.
318 If you have problems accessing your phone, start KO/Pi from the konsole 320 If you have problems accessing your phone, start KO/Pi from the konsole
319 and you will get a more detailed output what went wrong. 321 and you will get a more detailed output what went wrong.
320 About Gammu from the Gammu homepage: 322 About Gammu from the Gammu homepage:
321 Gammu (formerly known as MyGnokii2) is a cellular 323 Gammu (formerly known as MyGnokii2) is a cellular
322 manager for various mobile phones/modems. 324 manager for various mobile phones/modems.
323 It supports the Nokia 2100, 3100, 32xx, 33xx, 325 It supports the Nokia 2100, 3100, 32xx, 33xx,
324 3410, 35xx, 51xx, 5210, 5510, 61xx, 62xx, 326 3410, 35xx, 51xx, 5210, 5510, 61xx, 62xx,
325 63xx, 6510, 6610, 6800, 71xx, 7210, 7250, 327 63xx, 6510, 6610, 6800, 71xx, 7210, 7250,
326 7250i, 82xx, 83xx, 8910, 9110, 9210 328 7250i, 82xx, 83xx, 8910, 9110, 9210
327 and compatible and AT devices (Siemens, Alcatel, 329 and compatible and AT devices (Siemens, Alcatel,
328 Falcom, WaveCom, IPAQ, Samsung, SE, and others) 330 Falcom, WaveCom, IPAQ, Samsung, SE, and others)
329 over cables/infrared/BlueTooth. 331 over cables/infrared/BlueTooth.
330 332
331 Here is an example what to specify to access a Nokia 6310i via infrared: 333 Here is an example what to specify to access a Nokia 6310i via infrared:
332 On Linux (Zaurus): 334 On Linux (Zaurus):
333 I/O device: /dev/ircomm 335 I/O device: /dev/ircomm
334 Connection: irda 336 Connection: irda
335 Model: <leave empty> 337 Model: <leave empty>
336 338
337 On Windows: 339 On Windows:
338 I/O device: <ignored - i.e. leave empty> 340 I/O device: <ignored - i.e. leave empty>
339 Connection: irda 341 Connection: irda
340 Model: <leave empty> 342 Model: <leave empty>
341 343
342 Here is the overview from the Gammu documentation, 344 Here is the overview from the Gammu documentation,
343 how to specify the connection settings for 345 how to specify the connection settings for