I'm afraid this program is not yet ready for real use - even ignoring that some of the sync features are not yet available.
Hi,
sorry that you have these problems with ZMacSync. We will try to solve them if they can be repeated. Other users have reported that it now works for them without issues.
ZMacSync hung while syncing my address book of about 700 entries (or maybe it just was taking a very long time - but there's no progress bar or other report so you can tell the difference).
There are reports from the author of AJZaurusUSB that the USB hardware of the SL5500 devices is not stable and might stop communication. So ZMacSync will sit there and wait. To test, you could try to start a parallel ssh session to the Zaurus to find out if IP over USB is hanging.
On first sync, *identical* entries on the Zaurus and the Mac were copied across to the Mac (they were put on the Zaurus from the Mac in the first place using ZMacSync 1.0a3), resulting in hundreds of duplicate entries in my Mac's address book.
This is a result of the way syncing works. ZMacSync has no idea / makes no assumptions about the content of the records. So, entries are identified by an "unique-ID" tag. If there are initially entries on both machines which look the same, they are still processed as two different entries having different "unique-ID". So, records apparently identical are therefore copied to the peer. In normal operation, this allows to reliably detect deletions, additions and modifications and allows to sync only what really has been changed. And to limit the data loss by conversion from one machine to the other. It is basically the same mechanism as Apple uses for iSync.
The solution for your problem is to start with a fresh and empty Zaurus address book (the 1.0a3 release did not yet have the unique-ID mechanism!). Sync will then copy all entries from the Mac to the Zaurus.
Could not connect to a Zaurus which has a passcode set (which is necessary if your Zaurus has a static IP address!)
[The documentation does say this might not work, I admit. However, I have no trouble using Fugu (sftp) to connect to the Zaurus with a passcode set.]
Yes, ssh and sftp can handle passcodes/passwords properly, but we have not yet found a mechanism to make a wrapper around the ssh command that can pass in the passcode. If you or somebody else knows of a solution we will be happy to integrate this feature.
On another point, the installation document assumes the user is using a USB cable for syncing, rather than WiFi, and it could say what is necessary in the latter case.
Nothing special or different. Just set the IP address of the Zaurus in the "i" popup. But nevertheless a good point for adding to the upcoming "Manual".
So, while the program holds promise, and I wish the author well in getting it all going, it seems a little premature to be expecting us to pay for it given that it is both incomplete and buggy.
Well, this is a matter of personal valuation - I think ZMacSync can already save a lot of time worth 10$. But in the shareware model that we have choosen, you are invited to download, evaluate and pay only if you are personally happy with it.
So, thank you very much for the hints for further improvement.
-- hns