Evolution & Palm
 

I'm probably missing something insanely obvious here, but anyway...

I'm trying to get Evolution to sync with my Tungsten T (m550), via USB.

I made /etc/udev/rules.d/10-visor.rules with the content as instructed by http://www.clasohm.com/blog/one-entry?entry_id=12096.
Then I ran the Pilot Settings wizard, and it found my palm at /dev/pilot and got the username etc from it. I changed the conduits settings to do everything on the list (backup, ecalendar, etodo, eaddress, file).

All the walkthroughs I've found get me to this point. Then they say 'press the hotsynch button', but I just get a timeout on the palm. I read somewhere that having a password can cause conflicts, so I removed it, but still no go. I feel like I'm living on borrowed time because I can't backup my palm... help me please!

I'm not sure about Evolution, but under JPilot I have to press the sync button on my Palm _before_ pushing the sync button in the app. If I don't the connection times out.

Yes, but I can't find the sync button on my computer. Evolution doesn't seem to have a nice 'sync with palm' button... Or... wait, should I try stopping the daemon and then pressing the hotsync button, then starting it? Hmm... I'll try that.

I'll actually have to try Evolution out one of these days. I hope that trick works for you.

Uh-oh. I restarted, and now I've lost it, ttyUSB* is gone, ditto anything with 'usb' in it in /dev.

What happened to my USB device? Or, more importantly, how do I get it back?

Okay, this seems to be what's happening. Once I restart, I lose all my ttyUSB's, until I press the hotsync button. Then I get them back, and the udev rule can grab them. Apart from that being rather an anoying way of having to get it connected... I still can't actually back anything up.

How am I actually supposed to use gpilot anyway? I'm lost...

I've given up on Evolution, and I'm just trying to get pilot-xfer to work, with this damn usb cradle. This is what I've done so far...
I've made the udev rules 10-local.rules and 10-visor.rules with the content:

BUS="usb", SYSFS{product}="Palm Handheld ", NAME="palm%n", KERNEL="ttyUSB*"

This creates the devices palm0 and palm1 after I press the HotSync button. I have a symlink /dev/pilot pointing to /dev/palm1 (which is the equivilent of ttyUSB1 should I not have the udev rules) .

I also have a script with the content:
#!/bin/sh

until [ -e /dev/pilot ]; do sleep 1; done
exec /usr/bin/pilot-xfer "-b /home/catherine/MyPilot"

What I do is this: I press the hotsync button, wait between 5 to 15 seconds, and then type in the command as root "pilot-xfer -b /home/catherine/MyPilot". It sees the device, and then asks me to press the hotsync button.
I can also run pilot-xfer before pressing the hotsync button. Then pilot-xfer waits as it sees that /dev/pilot isn't pointing to anything. Once I've pressed the hotsync button, it asks me to press the hotsync button. -.-
For both of the above, if I wait for the palm to timeout, or if I disconnect it, I get the error "Error read system info on /dev/pilot" and thats it.
If I run the script... it waits (I get nothing) and then I press the hotsync button and its the same as if I'd pressed the hotsync button before running pilot-xfer.

I'm at my whit's end. My pilot hasn't been backed up since March (when by some random stroke of luck I logedin as root to gnome and the transfer worked with gnome-pilot). I'm going to have to back it up on my mum's XP box soon.