On Tue, 24 Jun 2003 12:41:43 -0400 Mike Green wrote:

Is USB is supported by jpilot?

Yes, because it uses pilot-link just like kpilot/jpilot.

If so, is there some trick I am missing to get it to use USB? Or??

Press the hotsync button first on the cradle before pressing the sync button in jpilot. Also, check your settings in the preferences. If it still can't connect please post another message with the log. Charles -- A Linux machine! because a 486 is a terrible thing to waste! (By jjs@wintermute.ucr.edu, Joe Sloan)

On Tue, 24 Jun 2003 13:20:43 -0400 Jerry Feldman wrote:

Some versions of the newer Palm require pilot-link 0.11.x

I know that, but since he can sync with kpilot I assume that the pilot-link on his system is sufficient for his model. Charles -- "The world is beating a path to our door" -- Bruce Perens, (Open Sources, 1999 O'Reilly and Associates)

Thanks for all of the recommendations. So far I am not out of the woods. A. In my case I am syncing a Handspring Visor. So I think maybe the link to /dev/ttyUSB1 may be appropriate. (I have a generic question with respect to this which I will put at the end of this email.) B. What I now find is that if I re-boot both the Handspring *and* my computer (SuSE 8.2), I can sync just fine with jpilot the first time. Thereafter, whenever I try to sync, the Handspring reports that it cannot connect with the computer and I get the following message from jpilot: pi_accept Invalid argument Exiting with status SYNC_ERROR_PI_ACCEPT Note: I am not certain that the reboot of the Handspring is necessary. I have not tried to reboot only the computer. But I am sure that the reboot of the computer is necessary. I have tried rebooting -- i.e. re-setting -- only the Handspring. I looked for a process to kill instead of having to reboot the computer, but could not figure out which one it could be. Any ideas?? My more generic question: How does one figure out what device should be the symlink target? E.g., I had an idea that I should try /dev/ttyUSB1 for /dev/pilot, since I had been told by someone that that is what I should use for the Handspring Visor. But I am also trying to get my modem to work and have had troubles with a USB printer. In both of these cases my problems are likely not with what device they are symlinked to. But it would be good to be sure that they are symlinked to the correct devices to eliminate that as a potential source of the problems. TIA! Mike Green On Tuesday 24 June 2003 12:41 pm, Mike Green wrote:

Hi!

I have been following this thread and decided to try jpilot. But I can't get it to connect. (I can get kpilot to connect, albeit erractically.)

I supect the problem is due to the fact that my connection is through a cradle which uses USB. I have symlinked (ln -s /dev/ttyUSB1 /dev/pilot). But the settings menu in jpilot don't explicitly mention USB.

Is USB is supported by jpilot? If so, is there some trick I am missing to get it to use USB? Or??

TIA!

Mike Green

On Tuesday 24 June 2003 11:41 am, Sharpe, Richard wrote:

...

Charles

Thanks for the help !

Rich

-----Original Message----- From: Charles Philip Chan [mailto:cpchan@sympatico.ca] Sent: Tuesday, June 24, 2003 11:09 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Re: Syncing Palm's with SuSE KDE or GNOME ?

On Tue, 24 Jun 2003 10:54:04 -0400

"Sharpe, Richard" wrote:

...

I will try jpilot on KDE and if that does not work out I will attempt GNOME.

It will work under KDE. If you are going to compile it yourself I suggest you go for the CVS version since it is much better than 0.9.5. By default jpilot utilizes gtk 1.x, if you want a gtk2 version pass the flag --enable-gtk2 when doing ./autogen.sh. You can make it look some what the same as your other KDE app if you use Keramik as your KDE theme and Geramik for gtk.

Charles

-- "Besides, I think [Slackware] sounds better than 'Microsoft,' don't you?" (By Patrick Volkerding)

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!

I've just been trying to confirm that. I thought I would try your earlier suggestion to downgrade to 0.9.5. So I Googled for it and came up with pilot-link-0.9.5-ximian.2.i386.rpm, as being appropriate for SuSE. So I downloaded it and did (as root) rpm -ivh --replacefiles pilot-link-0.9.5-ximian.2.i386.rpm Then I again tried to hotsync and got exactly the same results as before... ;-( So I've been trying to find a way to confirm that it is actually using 0.9.5, so far without success. On Tuesday 24 June 2003 09:40 pm, Charles Philip Chan wrote:

On Tue, 24 Jun 2003 21:35:43 -0400

Mike Green wrote:

...

Thanks for the pointers. I am, however, still stuck at essentially the same point.

What is your version of pilot-link?

Charles

(1) pilot-xfer -v yields (aside from copyright and license statements): This is pilot-xfer, from pilot-link version 0.11.7 Build target..: i686-suse-linux Build date....: Mar 14 2003 00:17:05 (2) ldd /usr/bin/jpilot yields: libpisock.so.8 => /usr/lib/libpisock.so.8 (0x40027000) libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x4004b000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x4018d000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x401c6000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x401c9000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x401ee000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x401f6000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40205000) libm.so.6 => /lib/libm.so.6 (0x402d4000) libdl.so.2 => /lib/libdl.so.2 (0x402f6000) libc.so.6 => /lib/libc.so.6 (0x402f9000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) It is clear from (1) that I was not successful in my attempt to downgrade to 0.9.5. What (2) means is not clear to me. I'll have to dig more into how to downgrade. Any suggestions are appreciated... Thanks for your continued help! On Tuesday 24 June 2003 10:10 pm, Charles Philip Chan wrote:

On Tue, 24 Jun 2003 22:00:18 -0400

Mike Green wrote:

...

So I've been trying to find a way to confirm that it is actually using 0.9.5, so far without success.

What is the output of:

(1) pilot-xfer -v

(2) ldd /usr/bin/jpilot

Charles

Thanks! When you say "Recompile Jpilot to use version 0.9.5" I take it to mean that I cannot use an rpm. Is that true? On Wednesday 25 June 2003 08:00 am, Charles Philip Chan wrote:

On Wed, 25 Jun 2003 07:51:05 -0400

Mike Green wrote:

...

This is pilot-xfer, from pilot-link version 0.11.7

Build target..: i686-suse-linux Build date....: Mar 14 2003 00:17:05

(2) ldd /usr/bin/jpilot yields:

libpisock.so.8 => /usr/lib/libpisock.so.8 (0x40027000)

libpisock is from version 0.11.7. Now that things are a bit messes up you should:(1) Uninstall all pilot-link packages via YaST. (2) Install pilot-link 0.9.5 and (3) Recompile Jpilot to use version 0.9.5. Once you have done that, doing a ldd on jpilot will yield: libpisock.so.4.

Charles

On Wed, 25 Jun 2003 09:07:11 -0400 Charles Philip Chan wrote:

Not unless you can find a jpilot that is linked against 0.9.5 that works on your system. You can try the one from SuSE Linux 8.1 which is linked against 0.9.5 and see if it works (you can try using the pilot-link 0.9.5 from 8.1 too). Failing that, compiling it is very easy- I can guide you through that. If I recall, Jpilot 0.99.5 requires pilot-link 0.11.3+ IMHO, you are probably better of compiling from sources. If you have the development packages installed, then building is very simple.

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

On Wed, 25 Jun 2003 11:40:02 -0400 Charles Philip Chan wrote:

On Wed, 25 Jun 2003 11:20:56 -0400 Jerry Feldman wrote:

...

If I recall, Jpilot 0.99.5 requires pilot-link 0.11.3+

No it doesn't, it all depends on which library you link it to. I am using Jpilot CVS linked against 0.9.5. Anyway, I already send him links to the Jpilot and pilot-link 0.9.5 from 8.1. I hope it will work on his system- no harm trying. That is true. You need pilot-link 0.11.3 or greater if you want to sync some of the newer Palm s using USB. The older versions of Pilot-link will be fine for serial syncing.

-- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

Okay, using the pilot-link and jpilot links for 8.1 do the trick! The only significant wrinkle was that there was a dependency issue with perl-PDA-Pilot. [Well, it was the only wrinkle after I had jumped through several hoops upsidedown and backwards to undo the damage I had done in my attempts to do this using packages I had found on my own before you sent these links. ;-) ] I couldn't find a perl-PDA-Pilot package other than the one which came with my SuSE. So I used it. Also, YaST is now complaining about package inconsistencies with the pilot stuff. I don't know if this will give me grief in the automatic updates or not. I guess my cron job tonight will let me know if it does ;-) ? ;-( Thank you -- and everyone who has contributed to this thread -- very, very much!!! Cheers! Mike Green On Wednesday 25 June 2003 11:40 am, Charles Philip Chan wrote:

On Wed, 25 Jun 2003 11:20:56 -0400

Jerry Feldman wrote:

...

If I recall, Jpilot 0.99.5 requires pilot-link 0.11.3+

No it doesn't, it all depends on which library you link it to. I am using Jpilot CVS linked against 0.9.5. Anyway, I already send him links to the Jpilot and pilot-link 0.9.5 from 8.1. I hope it will work on his system- no harm trying.

Charles On Wednesday 25 June 2003 09:29 am, Charles Philip Chan wrote: OK, here are some quick links:

ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/pilot-link-0.9.5-47.i586.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/pilot-link-devel-0.9.5-47.i5 86.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-0.99-413.i586.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-devel-0.99-413.i586.r pm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-Backup-0.41-193.i586. rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-Mail-0.0.6-329.i586.r pm

I hope these will work with 8.2. There is no harm trying.

Charles

Well, from my experience, mostly what I can say is "try" -- and when you get stuck ask for help from the folk on this list ;-) I am now searching for a way to link the jpilot address book to something (e.g., OpenOffice) which I can use to print envelopes using the addresses in jpilot. But that should become another thread. On Wednesday 25 June 2003 05:30 pm, W.D. McKinney wrote:

Good to hear. I just inherited a iPAQ 3600 and wonder if there is any hope of syncing it in a similiar manner ?

Dee

On Wed, 2003-06-25 at 13:08, Mike Green wrote:

...

Okay, using the pilot-link and jpilot links for 8.1 do the trick!

The only significant wrinkle was that there was a dependency issue with perl-PDA-Pilot. [Well, it was the only wrinkle after I had jumped through several hoops upsidedown and backwards to undo the damage I had done in my attempts to do this using packages I had found on my own before you sent these links. ;-) ] I couldn't find a perl-PDA-Pilot package other than the one which came with my SuSE. So I used it.

Also, YaST is now complaining about package inconsistencies with the pilot stuff. I don't know if this will give me grief in the automatic updates or not. I guess my cron job tonight will let me know if it does ;-) ? ;-(

Thank you -- and everyone who has contributed to this thread -- very, very much!!!

Cheers!

Mike Green

On Wednesday 25 June 2003 11:40 am, Charles Philip Chan wrote:

...

On Wed, 25 Jun 2003 11:20:56 -0400

Jerry Feldman wrote:

...

If I recall, Jpilot 0.99.5 requires pilot-link 0.11.3+

No it doesn't, it all depends on which library you link it to. I am using Jpilot CVS linked against 0.9.5. Anyway, I already send him links to the Jpilot and pilot-link 0.9.5 from 8.1. I hope it will work on his system- no harm trying.

Charles

On Wednesday 25 June 2003 09:29 am, Charles Philip Chan wrote:

...

OK, here are some quick links:

ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/pilot-link-0.9.5-47.i586 .rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/pilot-link-devel-0.9.5-4 7.i5 86.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-0.99-413.i586.rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-devel-0.99-413.i5 86.r pm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-Backup-0.41-193.i 586. rpm ftp://ftp.suse.com/pub/suse/i386/8.1/suse/i586/jpilot-Mail-0.0.6-329.i5 86.r pm

I hope these will work with 8.2. There is no harm trying.

Charles

Apparently Version 0.9.5 does not provide for exporting data. At least it is not in any of the menus. And the Help menu and man page give little information. Perhaps I need to explore pilot-link itself more to see what would be needed to make it provide a conduit to a database accessible from OO... On Wednesday 25 June 2003 08:13 pm, Charles Philip Chan wrote:

On Wed, 25 Jun 2003 17:43:25 -0400

Mike Green wrote:

...

I am now searching for a way to link the jpilot address book to something (e.g., OpenOffice) which I can use to print envelopes using the addresses in jpilot. But that should become another thread.

Unfortunately, you can't do it directly. However, you can export the Jpilot address book to csv and import it into OO or another program.

If you want to use your Jpilot address book for email, you might want to check out Sylpheed ( http://sylpheed.good-day.net/) or Sylpheed-claws (http://sylpheed-claws.sourceforge.net/) which support it directly. Alternatively you can use Mutt in conjunction with lbdb (http://www.spinnaker.de/lbdb/).

Charles

There is no export option and ctrl-A does nothing. And I agree with you that the RPM I installed was Jpilot 0.99-413. So I don't know what happened... If and when you have an RPM that will provide more features while still working with the Handspring Visor, I will much appreciate having it. Thanks again! On Wednesday 25 June 2003 09:37 pm, Charles Philip Chan wrote:

On Wed, 25 Jun 2003 21:16:56 -0400

Mike Green wrote:

...

Apparently Version 0.9.5 does not provide for exporting data. At least it is not in any of the menus. And the Help menu and man page give little information.

You are using Jpilot 0.99-413, 0.9.5 is the pilot-link version. Are you sure there is no export option? It should be in the File menu, the shortcut is ctrl-A. If you want, next time when I upgrade, I can send you an RPM.

Charles

In a previous message, Mike Green wrote:

I've just been trying to confirm that. I thought I would try your earlier suggestion to downgrade to 0.9.5.

All this talk of downgrading pilot-link seems odd to me. My wife can sync her Visor on my SuSE 8.2 system via USB, which is running pilot-link 0.11.5 from the SuSE DVD.

From what I recall of the logfile you posted here, it showed that the Visor disconnected after connecting - was this because you had cancelled the hotsync or was it spontaneous? If the latter, check your cabling and plugs in case there's a loose connection somewhere that's causing comms problems.

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 Fields of Valour: 2 Norse clans battle on one of 3 different boards

In a previous message, Charles Philip Chan wrote:

On Wed, 25 Jun 2003 16:29:42 +0100 John Pettigrew wrote:

...

All this talk of downgrading pilot-link seems odd to me. My wife can sync her Visor on my SuSE 8.2 system via USB, which is running pilot-link 0.11.5 from the SuSE DVD.

Good for her, but myself and a lot of people have problems with pilot-link > 0.9.5 and Visors (I am using a Visor Deluxe). It is even stated on the Jpilot website:

2002-07-29 Do NOT use jpilot with pilot-link 0.11.0, 0.11.1, or 0.11.2! You have been warned. You can use 0.11.3 if you need usb, or a pilot-link older than 0.11 for serial, or usb visors.

I know "it works for me" isn't necessarily helpful. But this warning isn't about visors - it's about specific versions of pilot-link. For USB, you need a 0.11.x version, unless it's a visor for which 0.9.x versions are OK, and certain 0.11.x versions are known to cause problems with jpilot. If your visor/PC combination doesn't get on with specific versions of pilot-link then, by all means, try older versions. But I actually found that I needed 0.11.x to get my old visor to work on this PC. It seems to be a rather odd area that often requires fiddling. 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 Knossos: escape the ever-changing labyrinth before the Minotaur catches you!

On Tue, 24 Jun 2003 15:22:22 -0400 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. (I have a generic question with respect to this which I will put at the end of this email.)

I see, you might have to downgrade, Handspring Visor's works best with pilot-link 0.9.5. The device to use is /dev/usb/ttyUSB1. Charles -- ..you could spend *all day* customizing the title bar. Believe me. I speak from experience." (By Matt Welsh)