What does not
What was not tested
Anything beyond device syncing.
It should be noted that setting a Windows Mobile 2005 device into PocketPC connection mode will at least allow the device to be detected. (I.e Device says Connecting to Host.) ActiveSync regconises that the COM port is avaiable, (and even the USB port) but fails to connect to the device. (I.e ActiveSync says the device was not "detected".) It should also be noted that attempting to have ActiveSync connect manually via the conection settings window causes the device to make noise with each click on the connect button. So it's obviously doing something.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Arch Linux x86_64||Mar 08 2016||1.9.5||Yes||Yes||Platinum||michael|
|Current||Mageia 3||May 24 2013||1.5.30||Yes||Yes||Garbage||Patrick|
|Show||Ubuntu 9.04 "Jaunty" i386 (+ variants like Kubuntu)||Jun 06 2009||1.1.23||Yes||No||Garbage||Mikw|
|Show||Ubuntu 8.10 "Intrepid" i386 (+ variants like Kubuntu)||Apr 01 2009||1.1.18||N/A||No||Garbage||Martin Maucher|
|Show||Ubuntu 8.10 "Intrepid" i386 (+ variants like Kubuntu)||Jan 16 2009||1.1.12||Yes||Yes||Bronze||Patrick Kann|
by Dan (July 28th 2008)
If you're like me, and the only reason you wanted ActiveSync was to get
the .CAB file for a Windows Mobile program packaged as an installer
which is complaining you don't have ActiveSync installed, you might be
able to work around the requirement by adding a "PocketPC" folder to
your C:\, then applying this key with Wine regedit:
ActiveSync still won't install, but some installers that require it will put their CAB files in your virtual C:\PocketPC, then silently fail.