Martin Gregorie wrote: > > The problem is more likely to be caused by the access permissions for > the serial port. > > Who owns /dev/ttyS0 and what permissions does it have? IOW, does the > user where you're running the application have read and write access to > the serial port. Please show us what "ls -l /dev/ttyS[0-3]" shows. > I don't think that permission is the cause, see: Code: ls -l crw-rw---- 1 root dialout 4, 64 2011-01-17 12:26 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 2011-01-17 12:26 /dev/ttyS1 crw-rw---- 1 root dialout 4, 66 2011-01-17 11:27 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 2011-01-17 11:27 /dev/ttyS3 (I belong to dialout group) Martin Gregorie wrote: > > What Linux distro are you using? > Ubuntu Hardy with kernel 2.6.24-28-generic I tried also Gentoo with 2.6.34-r1. Martin Gregorie wrote: > > > > Is it possible to tell wine to not change any flags or set them on my own? > > > You can set them with the stty command. > Martin yes, I did. what I actually did is: 1. opened the port with win32 appl. called hwtest 2. restored previous settings (backed up with stty -g -F /dev/ttyS0) 3. placed card, nothing comes from the port. (cat /dev/ttyS0 works) I tried another COM test. It died after choosing the port to test. In windows with the same reader those programs work well. Could someone help me out with this? Do I have to file a bug at bugs.winehq.org?
