On Mon, 2005-09-05 at 20:54 +0900, Dave Gutteridge wrote:
ls -l /dev/pilot /dev/ttyUSB* should come up empty...please confirm
Confirmed: [dave@localhost ~]$ ls -l /dev/pilot /dev/ttyUSB* ls: /dev/pilot: No such file or directory ls: /dev/ttyUSB*: No such file or directory
then again... ls -l /dev/pilot /dev/ttyUSB* you should see 3 things happening...
And I do: [dave@localhost ~]$ ls -l /dev/pilot /dev/ttyUSB* lrwxrwxrwx 1 root root 7 Sep 5 20:38 /dev/pilot -> ttyUSB1 crw-rw---- 1 dave uucp 188, 0 Sep 5 20:38 /dev/ttyUSB0 crw-rw---- 1 dave uucp 188, 1 Sep 5 20:38 /dev/ttyUSB1
---- so far pretty good - though /dev/ttyUSB0 is owned by dave which means that you succeeded in mucking the permissions which obviously wasn't the problem as that should have been owned by root. ----
so I would say that if you don't have those devices when you aren't syncing and you do have those devices when you push the sync button on the cradle or on the palm - if jpilot is set to use /dev/pilot then the only issue I can see is the settings... 57600 & auto flow control works for me.
I don't see a setting for "auto flow control" in Jpilot. But I do have it set to 57600.
---- I meant the palm pilot - making sure it is set to 57600 and auto-flow ----
Perhaps you should make sure that you don't have some old processes hanging and reboot first.
Sorry, I'm not sure what you mean by this. Processes related to the palm pilot?
---- yes - and the usb drivers - try the windows fix - reboot the system.
Craig