http://bugs.winehq.org/show_bug.cgi?id=9526
Summary: Asyncpro and Linux Product: Wine Version: 0.9.44. Platform: All OS/Version: other Status: UNCONFIRMED Severity: critical Priority: P5 Component: test AssignedTo: wine-bugs@winehq.org ReportedBy: software@rel-tek.com
Hi,
I am trying to convert my program to run on Linux under wine. I have been very successful so far but one thing that is stopping me from going any further. That is Asyncpro. My program uses Asyncpro to get access to comports and to send and receive data. Apparently, wine HQ is having trouble dealing with Comports using Asyncpro.
Initially, I started running my window program on Linux (PCLinuxOS) under crossover. It failed miserably. My program connected and was communicating through comport but within running for a minute or so, a lots of error message boxes pop up non-stop with message, "too many open files." I couldn't figure what it was. So, after playing around with that far awhile, I changed to another Linux OS. This time instead of using CrossOver I decide to use Wine HQ.
Great, I thought when everything was going great with Wine HQ on SimplyMephis. My program started with no problem and even connected to serial port. From there I was able to communicate non-stop with no error boxes of any kind until I tried to shut my program down. My program completely froze to a point I had to go into window manager to kill wine-server or It will not shutdown. I still think there something not quiet right about Asyncpro on Wine.
When I ran debug on Wine, I got messages like
fixme:win:LockWindowUpdate(0x10020) partial stub! ...
Is anyone having a similar problem or is there a known bug with Wine and Asyncpro?
I will probably have to write my own comport control tool to better manage serial communication.
Please, Help.