Here's what I noticed while troubleshooting the problem: 1. After syncing with MultiSync and before opening any of the Zaurus applications, I could see that the xml files were being copied over to the Zaurus correctly.
2. After opening a Zaurus application, its xml file would revert to the data it contained before syncing. 3. I tried deleting the xml files from the Zaurus and syncing. When I did this, the xml files copied over by MultiSync were replaced with empty ones. 4. To make sure that it wasn't the format of the xml files causing problems, I entered some data into the Zaurus and copied the resulting xml files to my computer. I then deleted the files from the Zaurus and copied the files on my computer back to the the Zaurus, both manually and with MultiSync. In each case, the Zaurus replaced them with empty files after I opened the applications. 5. Since the file format wasn't to blame and the Qtopia Desktop was able to sync, I used a packet sniffer to see what the Qtopia program was doing and noticed the QCop stuff. 6. I tried manually entering some of the QCop commands while syncing with MultiSync and it worked. In order for a sync to not be rejected, I do the following after a sync but before opening any applications: 1. Telnet to the Zaurus as root on port 4243. The password doesn't seem to matter. 2. Enter one or more of the following commands depending upon what I have just synced: CALL QPE/System categoriesChanged() CALL QPE/Application/addressbook reload() CALL QPE/Application/todolist reload() CALL QPE/Application/datebook reload() The Qtopia Desktop passes much more commands than these, but these solve my problem. If you'd like to know about the other commands, I can send more info. Dave On Thu, 2003-08-14 at 18:50, Eike M. Lang wrote: > Am Don, 2003-08-14 um 22.01 schrieb David Kaylor: > > > Has any work been done with the QCop bridge? I saw a thread about this > > last month. The reason I ask is that it turned out to be the answer to > > a problem I was having. > > Tom and I are working on this. > > > I have a Zaurus 5500 running the 2.38 ROM with Qtopia version 1.5.0. > > When MultiSync 0.80 came out, I downloaded a copy to sync my Zaurus with > > Evolution but ran into a problem. The Zaurus was rejecting the xml > > files. At first I thought it had to do with the format of the file, but > > it turned out to be the QCop bridge. I looked at what the Qtopia > > Desktop client does when it syncs and found that if I enter some of the > > QCop commands manually, the Zaurus accepts the MultiSync files. My C > > programming skills leave a lot to be desired but I am now familiar with > > the QCop commands that the Qtopia Desktop client uses and would be happy > > to help if I can. > > Tom and I both use opie, so any info on what the qtopia version in the > 2.38 ROM does (differently, as opie happily syncs without using qcop) > would be much appreciated. A step by step transcript of what you did to > make it work and as much info as possible about the case when it doesn't > work would be very helpful. > > Regards, > Eike ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
