I have several software packages for Windoz that provide for a phone/fax answering machine. In the newer wine, I can install, but cannot get access to the Com port. I have created the ln -s in dosdevices, and even did a chmod 777 on dev/ttyS0. The user is a member of groups associated w/ modems, dialout, etc. I always get "the port is being accessed by another program". I am stuck on two very different machines. Both run Open SuSe 11.0 Anyone solved this? Thanks, FX
On Thu, 2009-09-17 at 12:43 -0500, driveoldford wrote:> I have several software packages for Windoz that provide for a > phone/fax answering machine. In the newer wine, I can install, but > cannot get access to the Com port. I have created the ln -s in > dosdevices, and even did a chmod 777 on dev/ttyS0. The user is a > member of groups associated w/ modems, dialout, etc. > > I always get "the port is being accessed by another program". I am > stuck on two very different machines. Both run Open SuSe 11.0 Anyone > solved this? >I had a similar problem with a WINE app that downloads files from a logger. BTW, it applies to all programs, e.g. Kermit and minicom, as well as WINE apps that are run by normal users. With current, udev-based, kernels its necessary to reset the permissions of /dev/ttyS[0-9] after every boot. I added a local rule file to /etc/udev/rules.d: $ cat 51-local.rules # # Locally defined rules. # # # Give world read/write access to ttyS* and ttyUSB* serial devices # KERNEL=="tty[A-Z]*", GROUP="uucp", MODE="0666" $ This works under Fedora 6 through Fedora 10. Under earlier releases it was sufficient to add a line containing: chmod uga+rw /dev/ttyS* to /etc/rc.d/rc.local so it got run at boot time, but IIRC this doesn't work with UDEV since all the /dev/ttyS* devices are no longer created ar boot time. On Fedora 10 and WINE 1.1.23 this works with all real serial ports (I have two on the mobo and another 4 on an IPC card) without needing to add COMn: symlinks to the dosdevices directory. I have never been able to access USB serial adapters from WINE, probably because they need special Windows drivers. Martin
Thanks for the reply. Unfortunately, it does not seem to be permissions problems. I tried exactly what you had suggested - no go. I have tried three different software packages - all w/ the same result - cannot access the com port. Anybody else having problems w/ serial ports in Wine? Thanks, FXS
driveoldford wrote:> I have several software packages for Windoz that provide for a phone/fax answering machine.Just pick a native Linus program instead. You moved to Linux why? So you can run some crappy windows software?
Here goes: linux-w5px:/proc # chmod 777 /dev/ttyS* linux-w5px:/proc # ls -l /dev/ttyS* crwxrwxrwx 1 root uucp 4, 64 2009-04-14 06:32 /dev/ttyS0 crwxrwxrwx 1 root uucp 4, 65 2009-04-14 06:32 /dev/ttyS1 crwxrwxrwx 1 root uucp 4, 66 2009-04-14 06:32 /dev/ttyS2 crwxrwxrwx 1 root uucp 4, 67 2009-04-14 06:32 /dev/ttyS3 crwxrwxrwx 1 root uucp 4, 68 2009-04-14 06:32 /dev/ttyS4 crwxrwxrwx 1 root uucp 4, 69 2009-04-14 06:32 /dev/ttyS5 crwxrwxrwx 1 root uucp 4, 70 2009-04-14 06:32 /dev/ttyS6 crwxrwxrwx 1 root uucp 4, 71 2009-04-14 06:32 /dev/ttyS7 I should point out that I'm trying two different computers: an old IBM laptop 600X, and, a really old Toshiba desktop. Both! have exactly the same ls listing! Software is Chyenne Bitware Voice Mail System (works real well). When I try to "setup" the modem - the message is: "... com port currently used by another application ...". But it's not, that I am aware of. Dmesg on the old Toshiba referenced ttyS1, so, I have links in dosdevices to both com1 and com2. As you can see, I don't think this is a permissions issue. Interestingly, I have some really old DOS "Testcoms" software. Both report no com port (in xdosemu)! Is this an old Bios issue?
Martin: Thanks for your continued interest and input. Most of my effort is on the old Toshiba. This is a multi-boot machine w/ Win 2000,Open SuSe 11.0 and Knoppix, which is a debian distro. This machine has one physical serial port. In Knoppix, the ls command shows 4 serial ports. Wine, in Knoppix, is showing the same non-functioning with the software as was the case w/ SuSe 11.0 Just to be sure, I attempted to install all 3 commercial packages that I have. Same result. The software does not seem to properly capture the serial port. W/ communicate Pro (not a very good package) the software claimed that it did, in fact, connect w/ the proper serial port ( a success message) - but - nothing really worked at all and I had to terminate w/ a kill command. I can tell you that this is an embarrassment for me since one of our business lines is to convert people to linux! But the "answering/fax machine" is running on Windoz! Regards, FXS