Just point me to setup help
seth at cql.com
Mon Oct 28 11:18:22 EST 2002
I reran this procedure, exactly as I described it, without any
prexisting /dev/ttyUSB0 or /dev/ttyUSB1, and they were indeed detected
On Mon, 2002-10-28 at 04:31, David A. Desrosiers wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> > 2. Boot the system with the cradle disconnected. Then, with pilot-link
> > running, connect the cradle to the USB port (with power to the cradle, of
> > course). You should see a message showing you the device names detected.
> This is incorrect. If you launch pilot-link ("with pilot-link
> running" as you state), it will immediately exit, because /dev/ttyUSB1 does
> not exist (/dev/ttyUSB0 for Clie devices, /dev/usb/tts/1 or 0 for devfs).
> Plugging in the cradle, powered or not, does not connect the device to the
> usb subsystem, it's not like a mouse. You must cradle your Palm and hit the
> HotSync button, which makes the electrical connection, and creates the
> device on the usb subsystem.
> > On my system it is /dev/ttyUSB1. Note that you will see two devices
> > detected, in my case /dev/ttyUSB0 and /dev/ttyUSB1. You want to use the
> > second.
> Depending on your Palm model. Some use 0, some use 1.
> > I've been too lazy to figure out what you would have to specify to
> > pilot-link so that jpilot will see the configuration.
> Absolutely nothing, they are completely unrelated. There is no
> "configuration" in pilot-link that J-Pilot can see or read that can tell
> J-Pilot which device type you are using at launch time. I will be adding a
> global and local configuration file soon that will help this, but not yet.
> perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.1.92 (GNU/Linux)
> -----END PGP SIGNATURE-----
> Jpilot mailing list
> Jpilot at moongroup.com
M. I. S. Corp
Pager 888-605-9296, or 6059296 at skytel.com
More information about the Jpilot