Thanks for the pointers. I am, however, still stuck at essentially the same point. Whether the link is to /dev/usb/ttyUSB1 or /dev/ttyUSB1 (both exist and one is not a symlink to the other) my Handspring still reports that it can't connect and jpilot says pi_accept Invalid argument Exiting with status SYNC_ERROR_PI_ACCEPT tail (Thanks for the tip on this!) says: Jun 24 21:19:16 Lewis kernel: hub.c: new USB device 00:01.2-2, assigned address 8 Jun 24 21:19:16 Lewis kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected Jun 24 21:19:16 Lewis kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 2 Jun 24 21:19:16 Lewis kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0 Jun 24 21:19:16 Lewis kernel: visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1 Jun 24 21:19:16 Lewis kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Jun 24 21:19:16 Lewis kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs) Jun 24 21:20:08 Lewis kernel: usb.c: USB disconnect on device 00:01.2-2 address 8 Jun 24 21:20:08 Lewis kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB0 Jun 24 21:20:08 Lewis kernel: usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter now disconnected from ttyUSB1 So it appears that the Handspring is detected and assigned, as you indicated, to ttyUSB1 for the hotsyncing (although it does not say whether this is to /dev/usb/ttyUSB1 or /dev/ttyUSB1). And it seems odd that it all worked just fine the first time I tried it and then again after I rebooted the computer. It is as if something is getting set and not unset, or started and not stopped, during the hotsyncing. Thanks again for your help! Mike Green On Tuesday 24 June 2003 06:08 pm, John Pettigrew wrote:
In a previous message, Mike Green wrote:
A. In my case I am syncing a Handspring Visor. So I think maybe the link to /dev/ttyUSB1 may be appropriate.
Sorry - didn't realise you weren't the original poster. Must read attributions more closely :-)
In any case, that link should still be /dev/usb/ttyUSB1 (notice the extra directory in the middle). Always check that targets exist when creating links!
My more generic question: How does one figure out what device should be the symlink target?
tail -f /var/log/messages (as root)
This will show you the messages as the device is connected to the computer. And in there somewhere will be the ports that the Visor is claiming.
John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!