CrossOver Support - Community Forums

I have a couple of Windows programs which use serial ports, which are Aten or FTDI usb-serial adapters. These worked OK until upgrading to CrossOver 17.
It appears that the upgrade overwrites the symbolic links which I had manually installed in accordance with the instructions here:
https://www.codeweavers.com/support/wiki/mac/faq/usbtoserial
The solution was to delete the .cxoffice/[bottlename]/dosdevices/com1 symbolic link.
I could then re-establish the correct link to /dev/ttyUSB0.
The com1 serial port then worked as it should.
Hope that this helps somebody.

This is a change in behavior from CrossOver 16 to CrossOver 17. I'm sorry - this is a change which we should have handled in a more automated way.

Wine now scans for usb ports automatically, and has changed so that creating symlinks by hand is no longer supported behavior. For CrossOver users, this means two things. First, you should no longer create such symlinks because they will be overwritten as you describe. Second, you should instead edit the registry of the bottle you want.

For now, a guide from Wine's wiki is here and should get you going:

https://wiki.winehq.org/Wine_User%27s_Guide#Serial_and_Parallel_Ports

We also need to update our own documentation at the link you referenced above, which we will do also.

Again, I apologize. This is something we should have both made more automated and also documented earlier. The above should get you up and running.

Thank you Josh for responding so quickly.
This definitely needs documenting.
Can I help with this?

We've filed a bug internally to get the doc updated - I'm hopeful we'll have that done shortly.

Thanks for the post - it's good to hear where we need updated docs!

Here is how to locate the COM number for a USB serial adapter:

1. Open a terminal;
2. Navigate to the dosdevices folder in the bottle you are intending to use;
3. Generate a long format listing with 'ls -l'
4. The COM port alias for 'ttyUSB0' will appear among all of the other port aliases.
   Here is my listing for my LabVIEW bottle called b00_LV:
   [code]ray@ray-All-Series ~ $ cd .cxoffice/b00_LV/dosdevices
   ray@ray-All-Series ~/.cxoffice/b00_LV/dosdevices $ ls -l
   total 0
   lrwxrwxrwx 1 ray ray 10 Mar 17 2016 c: -> ../drive_c
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com1 -> /dev/ttyS0
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com10 -> /dev/ttyS9
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com11 -> /dev/ttyS10
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com12 -> /dev/ttyS11
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com13 -> /dev/ttyS12
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com14 -> /dev/ttyS13
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com15 -> /dev/ttyS14
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com16 -> /dev/ttyS15
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com17 -> /dev/ttyS16
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com18 -> /dev/ttyS17
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com19 -> /dev/ttyS18
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com2 -> /dev/ttyS1
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com20 -> /dev/ttyS19
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com21 -> /dev/ttyS20
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com22 -> /dev/ttyS21
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com23 -> /dev/ttyS22
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com24 -> /dev/ttyS23
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com25 -> /dev/ttyS24
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com26 -> /dev/ttyS25
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com27 -> /dev/ttyS26
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com28 -> /dev/ttyS27
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com29 -> /dev/ttyS28
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com3 -> /dev/ttyS2
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com30 -> /dev/ttyS29
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com31 -> /dev/ttyS30
   lrwxrwxrwx 1 ray ray 11 Jan 1 13:11 com32 -> /dev/ttyS31
   lrwxrwxrwx 1 ray ray 12 Jan 1 13:11 com33 -> /dev/ttyUSB0
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com4 -> /dev/ttyS3
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com5 -> /dev/ttyS4
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com6 -> /dev/ttyS5
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com7 -> /dev/ttyS6
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com8 -> /dev/ttyS7
   lrwxrwxrwx 1 ray ray 10 Jan 1 13:11 com9 -> /dev/ttyS8
   lrwxrwxrwx 1 ray ray 8 Apr 8 2016 d:: -> /dev/sr0
   lrwxrwxrwx 1 ray ray 8 Nov 14 2016 e:: -> /dev/sdc
   lrwxrwxrwx 1 ray ray 22 May 23 2017 f: -> /media/ray/RST LV PUMP
   lrwxrwxrwx 1 ray ray 9 Nov 14 2016 f:: -> /dev/sdc1
   lrwxrwxrwx 1 ray ray 9 Mar 17 2016 y: -> /home/ray
   lrwxrwxrwx 1 ray ray 1 Mar 17 2016 z: -> /
   ray@ray-All-Series ~/.cxoffice/b00_LV/dosdevices $

As you can see, the USB adapter comes up as COM33.
This works perfectly with my Windows programs.

Hi...i am a new user here. As per my knowledge recompiling the kernel should work. But if exagear has managed to do this without modifying the kernel, i would like to see if I can get something similar working and Wine is still compiling in my Docker container.

Is there documentation on this yet??? Otherwise I see no reason to ever upgrade if it will break my USB-Serial devices!

The automatic COM Port numbering system seems to work under Crossover Linux but NOT for Mac. Perhaps this is because the Mac gives non-standard names to devices? Anyway, I'm rolling back to an earlier version of Crossover because the latest one breaks all my COM ports!

There was a change in the way that COM ports work between CrossOver 16 and 17 that would have broken your existing port setup during the upgrade. The instructions for setting up COM ports in CrossOver 17 are here. If your devices are still not working, feel free to contact our support team using the "Contact Us" link at the top of this page.

Thanks,
Anna