Difference between revisions of "Serial Port Access in Wine Troubleshooting"

From Free Knowledge Base- The DUCK Project: information for everyone
Jump to: navigation, search
m
m (references)
Line 20: Line 20:
 
* https://usercomp.com/news/1036506/application-under-wine-cannot-access-any-serial-ports
 
* https://usercomp.com/news/1036506/application-under-wine-cannot-access-any-serial-ports
 
* https://www.onetransistor.eu/2015/12/wine-serial-port-linux.html
 
* https://www.onetransistor.eu/2015/12/wine-serial-port-linux.html
 +
* https://forums.linuxmint.com/viewtopic.php?t=412636

Revision as of 17:46, 16 February 2024

Identify the serial port for the device. in /dev you should see the following: /dev/ttyUSB0 then identify and inspect the port with the device connected and on.

tty -F /dev/ttyUSB0 -a

Once you know it exists and you can communicate with the device through Linux (the host operating system) you can continue.

Make sure your user (you) are a member of the dialout group

sudo adduser nicolep dialout

Wine (current versions >3) detects ports when it is run. You should look in ~/.wine/dosdevices folder for links to tty ports.

According to this source, Why can't applications under Wine access serial ports? By default, Wine does not provide direct access to serial ports on the host system. This is because accessing hardware devices directly can be a security risk and may interfere with the stability of the system. Therefore, Wine restricts access to certain resources, including serial ports.

Following their instructions

sudo vi ~/.wine/system.reg 

Look for "Serialcomm" and E486: Pattern not found rendering usercomp.com advice absolutely useless.

references