On Tue, 2005-11-08 at 07:33 -0700, Craig White wrote:
> On Tue, 2005-11-08 at 09:18 -0500, lance raymond wrote:
> > On Tue, 2005-11-08 at 06:53 -0700, Craig White wrote:
> > > On Mon, 2005-11-07 at 22:45 -0500, lance raymond wrote:
> > >
> > > > ok, switched to plain text, and on the bottom :)
> > > ----
> > > thanks - nice - makes it easy to reply inline and in context
> > > ----
> > > >
> > > > Did what you requested, 1st got a popup error
> > > > "The Application "gpilotd" has quit unexpectedly."
> > > ----
> > > that's ok - gpilot and pilot-xfer are two different things
> > > ----
> > > >
> > > > It did continue in the terminal though, starting with;
> > > >
> > > > Listening for incoming connection on /tmp/pilot... connected!
> > > >
> > > > Reading list of databases in RAM and ROM...
> > > >
> > > > then a HUGE list of what looks like everytihng on the treo and them
> > > > some, ending with;
> > > >
> > > > List complete. 485 files found.
> > > >
> > > >
> > > > Thank you for using pilot-link.
> > > ----
> > > right on - it workee
> > > ----
> > > >
> > > > So at least it was able to read from the device, just not sure how to
> > > > tell the OS that the device is on /device/something, and / or is there
> > > > more to it. I see evo uses /dev/pilot which I can simply sym link to.
> > > ----
> > > yes, you can either symlink...
> > >
> > > ln -s /tmp/pilot /dev/pilot # which seems tacky to me but should
> > > # work without issue
> > > or
> > >
> > > simply change the setup of gpilotd
> > > (Tools -> Pilot Settings -> Devices -> Port)
> > >
> > > to use /tmp/pilot instead of /dev/pilot
> >
> > -- left it as is (as you said no reason to), still not syncing. I use
> > the /tmp/pilot port, tested on evo with nothing at all. Tried to jump
> > to jpilot (as they have the sync icon / debug window). Pressing the syc
> > button you get the "PRESS HOTSYNC NOW", after pressing, you get nothing
> > in jpilot, but in the messages file you get:
> >
> > Nov 8 09:15:35 vader kernel: usb 2-1: Handspring Visor / Palm OS
> > converter now attached to ttyUSB2
> > Nov 8 09:15:35 vader kernel: usb 2-1: Handspring Visor / Palm OS
> > converter now attached to ttyUSB3
> > Nov 8 09:15:36 vader kernel: visor ttyUSB1: visor_write -
> > usb_submit_urb(write bulk) failed with status = -19
> ----
> That's a bit vague...
>
> 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!
>
> Craig
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
--
.~.
/V\
// \\
/( )\
^`~'^
