Quote:
1) Make sure that gpilotd is not running while trying to sync using JPilot. It can cause the syncronization to fail (or simply hang there). I made this mistake when I first trying to get this to work.
|
I'm Ok on this one ...
Quote:
2) Check the permissions on /dev/ttyS0. If you are getting a "permission denied" error, it might mean that the user you are logged in as doesn't have read/write permission to the port.
|
But not on this one - my permissions were 660 - I changed them to 666 - (I was sure I'd done that, but I was wrong) and it's now acting -
Now - both KPilot and jpilot (separate tests) are timing out
from Kpilot
Version: KPilot 4.3.10 (BRANCH)
Version: pilot-link 0.11.8
Version: KDE 3.1.4
Version: Qt 3.2.1
HotSync Log
19:25:29 Trying to open device...
19:25:29 Device link ready.
19:26:16 Can't accept Pilot (Connection timed out)
from jpilot
(magic):/home/magic-> jpilot
Couldn't find empty DB file.
jpilot may not be installed.
pi_accept: Connection timed out
pi_accept Illegal seek
Exiting with status SYNC_ERROR_PI_ACCEPT
Finished
Quote:
Also, just so I am clear, when you started jpilot (e.g., (magic):/home/magic-> jpilot), it gave you the error message about the empty DB file but the GUI still appeared?
|
Yes - I wondered about that -- How was I supposed to prepare an empty DB file for it ?
But this is progress - thx for your help so far -- I'm thinking the timing out may be a port rate issue