On Mon, Jan 05, 2004 at 09:08:17AM -0500, Tom Foottit wrote:
> First, thanks for the patch!
>
> The problem with this is that if you make a change in Opie and sync back
> to Evolution, everything will be back in the single address field in
> Evo.
Yup, but without this patch the data in Opie in
At Mon, 05 Jan 2004 09:29:47 -0500,
Tom Foottit <[EMAIL PROTECTED]> wrote:
>
> The 3.X ROM isn't supported for two reasons:
> 1) Last I looked, the english documentation for the new PIM data formats
> was not very good. That was some time ago, mind you.
> 2) I don't have a device capable of runnin
At Sat, 03 Jan 2004 20:24:46 -0800, Dan wrote:
> Ron,
>
> Spend some time reading the Openzaurus and the zaurususersgroup sites.
> It she purchased it retail it must be the Sharp ROM.
>
> After several attemps I have Open Zaurus 3.3.6 pre1 running on my 5500
> and syncing. The latest Multisync
We have an RPM with libwbxml2 on the download page -
http://sourceforge.net/project/showfiles.php?group_id=64305&package_id=61421&release_id=201383
Tom
On Sun, 2004-01-04 at 09:00, Pascal Hurni wrote:
> Hi all!
>
> I can install all rpm's with no problems on my rh9. but if i try to
> install th
When I have upgraded/re-flashed in the past I have deleted my sync pair
in Multisync, touched the .xml files in Opie, then created a new sync
pair.
If you keep the existing sync pair then everything should work as long
as the same data is present on your Opie device before you try the first
sync.
Yes, I think this could definitely be part of your problem. You should
be doing everything as one user - preferably not root.
Tom
On Tue, 2003-12-30 at 17:57, Kelly wrote:
> Hi,
>
> I'm still not able to get my sync to work ... everything is talking
> and ssh works.
>
> I just started fiddlin
The 3.X ROM isn't supported for two reasons:
1) Last I looked, the english documentation for the new PIM data formats
was not very good. That was some time ago, mind you.
2) I don't have a device capable of running a Sharp ROM (I run Opie on
my iPaq).
I don't mind hacking a bit to get around lack
Bart,
Sorry I did not get back to you on this a long time ago. When I was
trying to fix some opie_sync bugs before releasing 0.81 I had a look at
your calendar file you sent me. The problem was that somehow
(conversion/upgrades from old sharp PIM/???) it is garbled and not valid
XML. The XML parsi
First, thanks for the patch!
The problem with this is that if you make a change in Opie and sync back
to Evolution, everything will be back in the single address field in
Evo.
I have resisted doing things like this in the past, but I guess if
people think this is a good idea then I'll consider i