David:
> Generally, yes. Or you could use denatured alcohol and a swab.
> Just make sure they're clean and dry before you cradle it. You don't
> want to short those pins there.
The contacts cleaned well with the eraser.
> > Also, if I try to sync, the process repeatedly fails at a few
> > specific *.prc files.
>
> Which .prc files?
Now I can't find the files in question. I'll watch for them at the next
attempted sync.
> Setting the proper udev rule will fix this. You don't want the
> device to remain around anyway, since you can't communicate across it
> when its not in use.
> Are you running one of the other conflicting daemons?
I have checked with ps ax | grep gpilotd / kpilotd, and find none of those
are running.
> If either of these are running, it may cause problems. They
> are both unrelated to J-Pilot. Perhaps J-Pilot should check for these
> two daemons running in memory when it launches, and warn the user to
> kill them off if they wish to sync with J-Pilot.
> The udev rule you want should look like the following, all on
> one line in /etc/udev/rules.d/10-Palm.rules (you will have to create
> this file manually):
>
> BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB*",
> NAME=="ttyUSB%n", SYMLINK=="pilot", GROUP=="tty", MODE=="0666"
>
I have created 10-Palm.rules as directed. Should I attempt another sync with
pilot-xfer? I'll give it a go and see what happens.
Scott
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.jpilot.org/pipermail/jpilot/attachments/20060612/c92cab7b/attachment.pgp
More information about the jpilot mailing list