> palm m505? I tried a pencil eraser...is that the best?
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.
> Also, if I try to sync, the process repeatedly fails at a few
> specific *.prc files.
Which .prc files?
> Should I remove those from the back up folder and try to synce
> again? If the sync process freezes my system, I end up having to run
> ln -s /dev/ttyUSB1 /dev/pilot and then chmod 666 /dev/ttyUSB1, as
> those are lost when I have to reboot...
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.
> synch worked fine a couple weeks ago, using jpilot, but now, even
> pilot-xfer at the prompt won't run right.
Are you running one of the other conflicting daemons? One of
the most common issues I've seen, is when users mistakenly configure
the Palm device using the GNOME menus (System -> Preferences -> Palm
Devices, or something like that). This will auto-launch gpilotd, the
gnome-pilot daemon, and start it listening on the port every time you
log into GNOME. KDE has one as well for KPilot, called kpilotDaemon.
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"
David A. Desrosiers
desrod at gnu-designs.com
http://gnu-designs.com
More information about the jpilot mailing list