http://bugs.winehq.org/show_bug.cgi?id=15987
Summary: ActiveSync 4.5 don't synchronize devices (comm:get_baud_rate) Product: Wine Version: 1.1.8 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: shakaran@gmail.com
Created an attachment (id=17174) --> (http://bugs.winehq.org/attachment.cgi?id=17174) ActiveSync 4.5 log
When you execute ActiveSync 4.5 and plug a device, the program not recognize the port USB and the device is waiting.
Also the list of device has a overflow and the letters "Hide details/Show details" (in the spanish image "Ocultar detalles/Mostrar Detalles" is overlapped
But if you press again "Hide details" then the box has the normal aspect.
The complete log and images is attached.
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #1 from shakaran shakaran@gmail.com 2008-11-09 12:23:13 --- Created an attachment (id=17175) --> (http://bugs.winehq.org/attachment.cgi?id=17175) ActiveSync 4.5 at start
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #2 from shakaran shakaran@gmail.com 2008-11-09 12:25:00 --- Created an attachment (id=17176) --> (http://bugs.winehq.org/attachment.cgi?id=17176) ActiveSync normal
When you press "Hide details", the normal size (without overflow)
http://bugs.winehq.org/show_bug.cgi?id=15987
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|ActiveSync 4.5 don't |ActiveSync 4.5 don't |synchronize devices |synchronize devices |(comm:get_baud_rate) |
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2008-11-09 13:13:25 --- Wine does not presently support USB devices. What OS? What hardware?
http://bugs.winehq.org/show_bug.cgi?id=15987
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #4 from Anastasius Focht focht@gmx.net 2008-11-09 14:26:42 --- Hello,
yes target hardware information would be useful. How is your Windows CE/Windows Mobile device recognized in Linux? Such USB devices are usually talked using virtual serial interface (which is what Windows does with wineceusb driver)
If it's recognized in Linux using USB serial module (dmesg | grep usbserial) you might want to map it to COMx and use serial connection option of ActiveSync. E.g.
$ ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1
Make sure you have appropriate user rights for /dev/ttyUSB0 (sudo chmod a+rw /dev/ttyUSB0)
There is also a native Linux toolsuite, called "synce" (http://www.synce.org/) which aims to be feature compatible.
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #5 from shakaran shakaran@gmail.com 2008-11-09 18:40:56 --- Yes, I use synce and working perfectly, but wine with Activesync not working.
Some information of device (PDA)
The PDA is a HERM200 (PocketPC) commercialized by HTC as HTC TyTN II with Windows Mobile 6
$ synce-pstatus Version ======= Version: 5.1.465 (Unknown) Platform: 3 (Windows CE) Details: ""
System ====== Processor architecture: 5 (ARM) Processor type: 2577 (StrongARM) Page size: 0x10000
... more data insignificant (as battery status)
My laptop has Ubuntu 8.10 with kernel 2.6.27-7-generic, I connect the PDA for USB method.
The command $ ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1 doesn't help.
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #6 from shakaran shakaran@gmail.com 2008-11-09 18:46:59 --- Ah, forget it!. At the risk of mistaken, I believe that this bug might be related to the bug 15986 since in the installation of ActiveSync some fixme as stub as well not updated drivers, in special newdev:UpdateDriverForPlugAndPlayDevicesA
(Sorry fixme are not bugs, but can be related for synchonize devices)
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #7 from Anastasius Focht focht@gmx.net 2008-11-11 08:20:10 --- Hello,
--- snip --- Yes, I use synce and working perfectly, but wine with Activesync not working. --- snip ---
Does a serial device get created? /dev/ttyUSB0? Attach the relevant snippets of 'dmesg' which contains the usb driver/device information for that HERM200 device after you plugged it in.
--- snip -- The command $ ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1 doesn't help. --- snip --
How did you verify? Use that wcescomm.exe tool to check for connectivity. Make sure it also scans all serial COMx devices.
In your wine windows temp directory ($WINEPREFIX/drive_c/windows/temp/) there should be some logfiles, called wces*.log You might want to attach these logs.
--- snip --- I believe that this bug might be related to the bug 15986 since in the installation of ActiveSync some fixme as stub as well not updated drivers, in special newdev:UpdateDriverForPlugAndPlayDevicesA --- snip ---
Again: serial-over-USB host kernel driver for Windows CE/Mobile devices won't work. You need native Linux host driver support which creates the virtual serial port for you.
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #8 from shakaran shakaran@gmail.com 2008-11-11 16:34:12 --- Created an attachment (id=17224) --> (http://bugs.winehq.org/attachment.cgi?id=17224) Dmesg output for HERM200
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #9 from shakaran shakaran@gmail.com 2008-11-11 16:34:46 --- Created an attachment (id=17225) --> (http://bugs.winehq.org/attachment.cgi?id=17225) wces's logs
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #10 from shakaran shakaran@gmail.com 2008-11-11 16:35:34 --- --- snip --- Does a serial device get created? /dev/ttyUSB0? --- snip --- No, there is no file. I have to create it myself or should be created? If so I need some special command as mknod or similar?
--- snip --- Attach the relevant snippets of 'dmesg' which contains the usb driver/device information for that HERM200 device after you plugged it in. --- snip --- See file attached.
--- snip --- How did you verify? Use that wcescomm.exe tool to check for connectivity. Make sure it also scans all serial COMx devices. --- snip --- Yes, I executed these process and it launch ActiveSync, then I go to File>Conexion Settings and press the button "Connect", then a assistant appear and I press Next and I choose COM1 and the program return again over and over.
--- snip --- In your wine windows temp directory ($WINEPREFIX/drive_c/windows/temp/) there should be some logfiles, called wces*.log You might want to attach these logs. --- snip --- See file attached.
--- snip --- Again: serial-over-USB host kernel driver for Windows CE/Mobile devices won't work. --- snip --- Ok thanks. Does the implementation serial-over-USB might be considered for wine 1.2? or it requires much time and effort to prepare it? (I assume it must be quite laborious).
Cheers.
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #11 from Anastasius Focht focht@gmx.net 2008-11-11 18:12:23 --- Hello,
--- quote --- No, there is no file. I have to create it myself or should be created? If so I need some special command as mknod or similar? --- snip ---
If /dev/ttyUSBx doesn't get created this basically means the device isn't advertising itself as generic modem or serial port. In that case you could try to pass the vendor and product id to the Linux USB serial driver so it will recognize it.
Please run '/sbin/lsusb' command which shows vendor and product ids for the USB devices and post the output.
If one row contains the HERM200 device name (or something similar), use the vendor and product id and pass it to usb serial driver. E.g. look for Bus xxx Device yyy: ID <vendorid>:<productid> before the device name.
You then might want to load the usb serial driver:
--- snip --- $ sudo modprobe usbserial vendor=0x<vendorid> product=0x<productid>
$ dmesg --- snip ---
and post 'dmesg' output again.
--- quote --- Does the implementation serial-over-USB might be considered for wine 1.2? or it requires much time and effort to prepare it? (I assume it must be quite laborious). --- quote ---
Very unlikely in near future.
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #12 from shakaran shakaran@gmail.com 2008-11-13 09:10:20 --- Hi,
--- snip --- Please run '/sbin/lsusb' command which shows vendor and product ids for the USB devices and post the output. --- snip ---
$ lsusb Bus 003 Device 009: ID 0bb4:0b04 High Tech Computer Corp. Hermes / TyTN / T-Mobile MDA Vario II / O2 Xda Trion
--- snip --- You then might want to load the usb serial driver: --- snip --- $ sudo modprobe usbserial vendor=0x<vendorid> product=0x<productid>
$ dmesg --- snip ---
and post 'dmesg' output again. --- snip ---
dmesg output related: [147717.836563] usbcore: registered new interface driver usbserial [147717.838312] usbserial: USB Serial support registered for generic [147717.839989] usbcore: registered new interface driver usbserial_generic [147717.840027] usbserial: USB Serial Driver core
Regards.
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #13 from Anastasius Focht focht@gmx.net 2008-11-13 09:33:30 --- Hello,
--- quote --- $ lsusb Bus 003 Device 009: ID 0bb4:0b04 High Tech Computer Corp. Hermes / TyTN / T-Mobile MDA Vario II / O2 Xda Trion --- quote ---
--- quote --- dmesg output related: [147717.836563] usbcore: registered new interface driver usbserial [147717.838312] usbserial: USB Serial support registered for generic [147717.839989] usbcore: registered new interface driver usbserial_generic [147717.840027] usbserial: USB Serial Driver core --- quote ---
No other usbserial line following, stating 'xxx attached to ttyUSBx'? You could try the generic ipaq module ...
--- snip --- $ sudo modprobe ipaq vendor=0xbb4 product=0xb04 --- snip ---
and post dmesg output.
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #14 from shakaran shakaran@gmail.com 2008-11-13 10:02:21 --- Hi,
--- quote --- No other usbserial line following, stating 'xxx attached to ttyUSBx'? --- quote --- No and the command $ dmesg | grep attached, return nothing
--- quote --- $ sudo modprobe ipaq vendor=0xbb4 product=0xb04 --- quote ---
New dmesg output: [150795.104096] usbserial: USB Serial support registered for PocketPC PDA [150795.104106] ipaq: USB PocketPC PDA driver v0.5 [150795.105067] usbcore: registered new interface driver ipaq
Regards.
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #15 from Austin English austinenglish@gmail.com 2009-05-18 10:51:05 --- Is this still an issue in current (1.1.21 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=15987
stewartmike@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #16 from stewartmike@yahoo.com 2009-06-06 07:21:03 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #17 from Austin English austinenglish@gmail.com 2010-03-11 17:21:03 --- This is your friendly reminder that there has been no bug activity for 8 months. Is this still an issue in current (1.1.40 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #18 from Gerold Jens Wucherpfennig gjwucherpfennig@gmx.net 2011-01-10 19:01:51 CST --- Created an attachment (id=32807) --> (http://bugs.winehq.org/attachment.cgi?id=32807) The Installation Log of ActiveSync 4.5 on Wine 1.3.11
Please pay attention to the last line of the ActiveSync 4.5 Installation.
err:msi:copy_package_to_temp can't find L"C:\Program Files\Microsoft ActiveSync\SyncWatchdog.msi"
The Installation has gives to error return value, but SyncWatchdog.msi cannot be found.
I have no clue on how to fix this... can anybody help? I'm using wine git post 1.3.11 and Ubuntu 10.10.
http://bugs.winehq.org/show_bug.cgi?id=15987
Gerold Jens Wucherpfennig gjwucherpfennig@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gjwucherpfennig@gmx.net
--- Comment #19 from Gerold Jens Wucherpfennig gjwucherpfennig@gmx.net 2011-01-10 19:06:49 CST --- Sorry, for the typo...
I do not mean: "The Installation has gives to error return value, but SyncWatchdog.msi cannot be found."
but: "The Installation gives no error return value, but SyncWatchdog.msi cannot be found."
http://bugs.winehq.org/show_bug.cgi?id=15987
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kelvin_benson2002@yahoo.com
--- Comment #20 from Anastasius Focht focht@gmx.net 2011-06-19 03:57:47 CDT --- *** Bug 22061 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=15987
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://download.cnet.com/Mi | |crosoft-ActiveSync/3000-209 | |4_4-10031823.html Summary|ActiveSync 4.5 don't |Microsoft ActiveSync 4.5 |synchronize devices |don't synchronize devices OS/Version|other |Linux
--- Comment #21 from Anastasius Focht focht@gmx.net 2011-06-19 04:15:59 CDT --- Hello,
--- quote --- Please pay attention to the last line of the ActiveSync 4.5 Installation.
err:msi:copy_package_to_temp can't find L"C:\Program Files\Microsoft ActiveSync\SyncWatchdog.msi"
The Installation has gives to error return value, but SyncWatchdog.msi cannot be found. --- quote ---
That message seems harmless. The installer runs a custom action:
"msiexec.exe /I "[INSTALLDIR]SyncWatchdog.msi" /q
but this msi package is nowhere found in the installer, I inspected all binaries. Probably installed by another program (outlook?).
---
Anyway, there is still no one here with a proper phone setup!
The phone must be recognized in Linux first (USB Serial Driver -> /dev/ttyUSBx)!
As long as Wine doesn't see the device through serial device symlink there is nothing we can do!
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
--- Comment #22 from butraxz@gmail.com 2013-12-07 02:49:00 CST --- This ticket has not been updated for over 900 days. Development recommends to check the status on your bug every release or two and let to be known if the bug is still present. If not, mark it fixed. If you are no longer able to put effort to this ticket, you can abandon it.
Is this still an issue with 1.7.8 or higher ?
http://bugs.winehq.org/show_bug.cgi?id=15987
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |ABANDONED
--- Comment #23 from Anastasius Focht focht@gmx.net 2013-12-07 08:51:54 CST --- Hello folks,
since no one really bothered to properly set up their device in Linux first -> marking this bug 'abandoned'.
Please check the native Linux support for Windows Mobile devices here:
https://help.ubuntu.com/community/PortableDevices/WindowsMobile
This is also a required prerequisite for Wine.
Regards
http://bugs.winehq.org/show_bug.cgi?id=15987
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #24 from Austin English austinenglish@gmail.com 2013-12-09 21:19:56 CST --- Closing.