Distance Debugging Logo

As those of you who read my earlier posts about Linux and T-Mobile Dash may remember, I had a couple of lingering issues (you can read part I and part II). Well, with a little help from the internet community, my two biggest issues are now solved, and I believe that there is little or nothing that can be done on Windows that can't be done on the Linux platform.

  1. PIM Synchronization - After correctly patching my synce installation, I was able to sync contacts, calendar, tasks, and they've just added file sync support so that you can synchronize your smartphone file system with a directory on disk.  PIM stuff is under heavy development with new features and bug fixes all the time.  If you are interested in testing the bleeding-edge code, subscribe to the SynCE Windows Mobile 2005 mailing list for more info.
  2. After a kind WINE developer read my earlier post about problems installing ActiveSync, he took it upon himself to fix the issues and now ActiveSync installs correctly (see his posts on my earlier T-Mobile dash posts for more info).  I then was able to use WINE to run one of the standalone program installers (gnuboy, an opensource game boy emulator), which was "fooled" into thinking that ActiveSync would install it on the next sync.  Instead, I grabbed the .cab file that it unpacked into the ActiveSync directory, and was able to install that directly, so now there shouldn't be any problem installing applications either.

    After discussing this with the Windows Mobile 2005 SynCE list, there is some talk of other ways to accomplish this, such as determining how an application tries to check for ActiveSync, and tricking it so that you don't have to install ActiveSync in the first place, or writing/improving a tool to scan through these special installers looking for the .cab header, so this won't be last word on this issue for sure.

Hope this helps those of you concerned about Dash support on Linux.  After another month or so of use, I am extremely pleased with the whole setup.