On Tue, 2005-11-08 at 09:55 -0500, lance raymond wrote: > > > > Is Tools -> Pilot Settings -> Devices -> Port now set to /tmp/pilot ? > > -- yes, set to /tmp/pilot > > > > If that doesn't work, it would seem that whatever is > > in /usr/share/gnome-pilot/devices.xml doesn't match your device since > > gpilotd will monitor /tmp/pilot and try to identify that against what is > > in /usr/share/gnome-pilot/devices.xml > > > > If you need to check the device, try pressing the hotsync button on the > > cradle and then in command line try... > > /sbin/lsusb > > > > and see if the info matches an entry in > > /usr/share/gnome-pilot/devices.xml > > -- devices.xml shows: > <!-- Handspring Treo 600 --> > <device vendor_id="082d" product_id="0300" /> > > -- lsusb shows: > Bus 002 Device 009: ID 082d:0300 Handspring Treo 600 > > I am lost! ---- given that pilox-xfer -L -p /tmp/pilot works and the device matches up as you have verified and that gpilotd is set to /tmp/pilot then it should work. Let's leave the setup alone for a second and either reboot or log off and kill your gnome session completely and log back on and try again by opening evolution. If you have never sync'd before, you might try Tools -> Pilot Settings -> Select your pilot -> Edit and then clicking the button 'Get from Pilot' as that is sort of a first sync function and then pressing the 'hotsync' button on the cradle. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
