Wine and the serial port
Antonio Augusto Todo Bom Neto
antonio at xultz.wox.org
Mon Nov 5 07:43:42 CST 2001
On Sun, 04 Nov 2001 21:03:22 +0100
Gerson Kurz <gerson.kurz at t-online.de> wrote:
> I have an application that talks to hardware via the serial port.
> (Actually, it talks to a lot of hardware, banking peripherals). The app
> runs on both Win32 and OS/2.
> Of course, the main theme is porting the thing natively to linux (and I'm
> working on that). But just for fun I tried to get it to work with WINE, and
> while the "device emulation" works perfectly (much to my surprise, really
> good work guys!) the serial communication doesn't go far. The hardware
> receives the data, but the signals (RTS/CTS etc.) are NOT correctly handled
> by WINE.
I have an application that uses serial comm. with a litle Microchip PIC programmer. And I have the same problem.
In the moment, the solution was instalation of Codeweavers Wine from wine.codeweavers.com, but I'm studing why the Wine from winehq.com has this problem.
This event ocours because the codeweavers is an older version of wine,but is very stable.
Other older version, from winehq, runs ok.
Lowson wrote me an e-mail with a method to call wine and debug the serial access:
It that doesn't help, maybe
wine --debugmsg +comm,+file blah.exe 2>&1|tee logfile
will at least give you different error messages, which might tell me
what is wrong.
Or you could just give up and boot with the boot parameter
"devfs=nomount". I _think_ that will disable devfs and give you back
your old /dev/ttyS* devices. Maybe.
Please, mail me if you know what is happen.
More information about the wine-users