Hello. I have tried wine with several open-source systems (Knoppix, PC-BSD, Ubuntu, Fedora), running a windows program that uses serial at 4800 baud to communicate with a measuring device. I notice that wine behaves a little differently with each operating system I run it on, using the exact same hardware (just a different hard drive each time). I also tried wine with 4 different computers, with the various operating systems. What I see is generally poor or no operation of the serial COM port. With PC-BSD and Fedora I get no serial operation. With Knoppix I see a slow operation on "fast" computers while older slower computers hang-up on the first attempts to communicate. Wine on Ubuntu runs the best, almost as good as the program runs on Windows. But that happened when I installed wine using sudo (which I later learned is not recommended) AND copying the program's files directly into a sub-folder off the .wine folder. When I installed wine in Ubuntu (a new installation of Ubuntu) not using sudo, and installed the program "normally" from the CD, that same program would not communicate at all. There may be a lot of variables going on here, but I wonder if anyone has any thoughts about any of this. Is there anything I could do in the wine configuration (or anywhere) to improve serial operation? Thank you.
On Fri, 2012-03-30 at 14:10 -0500, ron r wrote:> Hello. I have tried wine with several open-source systems (Knoppix, > PC-BSD, Ubuntu, Fedora), running a windows program that uses serial at > 4800 baud to communicate with a measuring device. I notice that wine > behaves a little differently with each operating system I run it on, > using the exact same hardware (just a different hard drive each time). > I also tried wine with 4 different computers, with the various > operating systems. >What serial port hardware are you using? IME this matters a lot. I use the Fedora distro. Many releases and 6 years ago, when I started to run Windows apps that use a serial port to talk to external devices I had no joy at all with attempts to use USB<->Serial adaptor and installed a multiport serial board with real 16650 UARTS on it. This 'just worked' and I've had no problems with using it for the same app over many Fedora and Wine upgrades. I've never needed to reinstall the app: the automatic Wine prefix upgrades have also 'just worked'. Recently I replaced the PC, transferring the multiport card into the new box and upgrading from F13 to F16 at the same time. This app worked first time when tried after the upgrade. Martin
In most cases the user doesn't have permision to access serial ports, so you'd first need to add the user to group dialout or take similar action depending on the underlying system. Then you'd add symbolic links like "ln -s /dev/ttyS0 com1", if not already present. With this solution you usually won't need to run as root. For the remaining issues you should file bugs.
Hey! I also have tried with Knoppix to activate some programs I need..but usually I had a mistake. Reading the forum i hope will solve my problem but at the moment I've idea what is going on. __________ mp4 to avi http://freemp4toaviconverter.com/
Thanks for the replies. The serial hardware is what is on the motherboard(s) - I don't know any more detail. I tried "ln -s /dev/ttyS0 com1" and there was no error message, but there was no difference either. I was going to try entering "chmod 777 ." in the /etc/rc.d/rc.local folder, but I did not find that folder while carefully using the file manager. And I tried this with Ubuntu, Fedora and PC-BSD, each one did not have that exact folder. I still wonder why one disk installation of ubuntu and wine runs the serial program well, while another disk installation of ubuntu and wine will not see the serial port. Thank you for any continued suggestions.
I am using Fedora 16. Using "ls -l /dev/ttyS*" shows 4 "devices" with "crw-rw----" for each one. So then I looked on google for setting serial permissions, and entered "chmod a+rw /dev/ttyS0" as root and the serial port now works! That was a nice victory, but the line must be entered at each boot. (Is there a solution to that?) Thank you, Martin, for the suggestions. I would never have known how to begin to fix the problem.
ron r wrote:> I am using Fedora 16. Using "ls -l /dev/ttyS*" shows 4 "devices" with "crw-rw----" for each one. So then I looked on google for setting serial permissions, and entered "chmod a+rw /dev/ttyS0" as root and the serial port now works! > That was a nice victory, but the line must be entered at each boot. (Is there a solution to that?) > > Thank you, Martin, for the suggestions. I would never have known how to begin to fix the problem.As lahmbi5678 pointed out, access to the serial port only requires your user to be member of the "dialout" group, which has read & write access to the ports. Close your session after adding your user to the group, you should be fine. Usurp