SV: [Evolution] syncing iPAQ with Evolution
Anders.Naslund@connecta.se
Anders.Naslund@connecta.se
Tue, 8 Feb 2005 11:31:59 +0100
This is a multi-part message in MIME format.
------_=_NextPart_001_01C50DC9.AAA6CFF4
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Have You got the Multisync Evo2 plugin compiled as well?
It's only available from CVS as far as I know...
If You use Multisync you need to setup a sync pair in Multisync to get =
it to work, Evo does not understand Multisync plugins :-)
=20
/A
________________________________
Fr=E5n: evolution-admin@lists.ximian.com genom Joel Louis Blom
Skickat: ti 2005-02-08 11:09
Till: evolution@lists.ximian.com
=C4mne: [Evolution] syncing iPAQ with Evolution
Hi,
I had some answer to my question with respect to the connection of
Evolution to my iPAQ but I still haven't succeeded. Using synce I can
connect to the iPAQ (HP 1940). pstatus, plist, etc all work like a
charm. Evolution, however is completely blind. When I try to connect,
using the pilot-settings procedure, the syncing does not occur, although
I'm using ttyUSB0 which is the connecting device. Most other thing s
work. I can even ping it (although it only works with a fixed IP and not
with DHCP).
I have installed all the synce packets (synce-0.9.0-1.i386.rpm and
synce-multisync_plugin-0.9.0-1.i386.rpm) but Evolution cannot be
reached. What am I missing here?
Joep
_______________________________________________
evolution maillist - evolution@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/evolution
------_=_NextPart_001_01C50DC9.AAA6CFF4
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7226.0">=0A=
<TITLE>[Evolution] syncing iPAQ with Evolution</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText67180 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Have You got =
the Multisync =0A=
Evo2 plugin compiled as well?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>It's only available from CVS =
as far as I =0A=
know...</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>If You use Multisync you need =
to setup a =0A=
sync pair in Multisync to get it to work, Evo does not understand =
Multisync =0A=
plugins :-)</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>/A</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>Fr=E5n:</B> =
evolution-admin@lists.ximian.com genom =0A=
Joel Louis Blom<BR><B>Skickat:</B> ti 2005-02-08 11:09<BR><B>Till:</B> =0A=
evolution@lists.ximian.com<BR><B>=C4mne:</B> [Evolution] syncing iPAQ =
with =0A=
Evolution<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi,<BR>I had some answer to my question with respect =
to the =0A=
connection of<BR>Evolution to my iPAQ but I still haven't succeeded. =
Using synce =0A=
I can<BR>connect to the iPAQ (HP 1940). pstatus, plist, etc all work =
like =0A=
a<BR>charm. Evolution, however is completely blind. When I try to =0A=
connect,<BR>using the pilot-settings procedure, the syncing does not =
occur, =0A=
although<BR>I'm using ttyUSB0 which is the connecting device. Most other =
thing =0A=
s<BR>work. I can even ping it (although it only works with a fixed IP =
and =0A=
not<BR>with DHCP).<BR>I have installed all the synce packets =0A=
(synce-0.9.0-1.i386.rpm and<BR>synce-multisync_plugin-0.9.0-1.i386.rpm) =
but =0A=
Evolution cannot be<BR>reached. What am I missing =0A=
here?<BR>Joep<BR>_______________________________________________<BR>evolu=
tion =0A=
maillist - evolution@lists.ximian.com<BR><A =0A=
href=3D"http://lists.ximian.com/mailman/listinfo/evolution">http://lists.=
ximian.com/mailman/listinfo/evolution</A><BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C50DC9.AAA6CFF4--