On Saturday 03 February 2007 21:17, Dirk Eddelbuettel wrote:
> 1) Prepare the statement to be executed, in my case
> pilot-xter -p /dev/ttyUSB1 -l
> but do not yet press Enter
>
> 2) On the Palm Treo 700p, launch the HotSync and press the hotsync icon.
> Wait until the 'Connecting with the desktop using Cradle/Cable' appears
>
> 3) Maybe a half-second or second after the text appears, hit Enter in the
> shell prepared in 1). You will greeted with 'Connected' from pilot-xfer.
Newer palm devices have exactly this behavior. They also appear to the system
even if there is no hotsync active. Older models only appeared while pressing
the button on the cradle. Newer devices exactly disappear and appear again
with different endpoints which are used for syncing. I am not this familiar
with the usb subsystem, but i guess if a process like pilot-xfer claim
the /dev/ttyUSB1 device node, it is not going to disappear and the new
endpoints will appear then as /dev/ttyUSB{2,3}.
Which version of pilot-link do you have? The pilot-link version 0.12.x
supports syncing via libusb which should fixed this ("LiveDrive") issue.
For the socket address just use "usb:" instead of the serial USB device node:
pilot-xfer -p usb: -l
If this doesn't help, you should report this issue to the pilot-link-general
mailing list.
best regards,
Daniel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
