thr3ads.net - wine users - serial port communication

If this information is useful, please help other people find it:
Share via:

Matthias Schweinoch

2004-Jan-29 06:32 UTC

serial port communication - again

hello,

i am using wine 20040121, and the windows application i am trying to run
need to communicate through the serial ports with an attached device.
the problem is this: whenever i try to communicate with the serial
device, i get the following error message:

--- ouput starts ---
 
trace:comm:EscapeCommFunction handle 0x164, function=3
trace:comm:EscapeCommFunction SETRTS
fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub
trace:comm:SetCommTimeouts (0x164,0x424f0a50)
trace:comm:PurgeComm handle 0x164, flags f
trace:comm:BuildCommDCBAndTimeoutsA (COM1:9600,e,8,1,0x424f0a64,(nil))
trace:comm:BuildCommDCBAndTimeoutsW
(L"COM1:9600,e,8,1",0x424f0a64,(nil))
trace:comm:SetCommState handle 0x164, ptr 0x424f0a64
trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 1 Parity 2
stopbits 1
trace:comm:SetCommState ~IXON ~IXOFF
trace:comm:EscapeCommFunction handle 0x164, function=3
trace:comm:EscapeCommFunction SETRTS
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:PurgeComm handle 0x164, flags 4
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 1 cbOutQue = 0
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:ClearCommError handle 0x164 cbInQue = 8 cbOutQue = 0
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:PurgeComm handle 0x164, flags 4
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x164 cbInQue = 3 cbOutQue = 0
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:PurgeComm handle 0x164, flags 8
trace:comm:PurgeComm handle 0x164, flags 4
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS
trace:comm:EscapeCommFunction handle 0x164, function=4
trace:comm:EscapeCommFunction CLRRTS


--- output ends ---

R/W perms are okay, as far as i can tell (user running wine has R/W
perms to access serial devices). 

thanks for your help in advance.

matthias

any suggestions are very welcome:-)

Raul Dias

2004-Jan-29 07:23 UTC

head link

serial port communication - again

On Thu, 2004-01-29 at 10:32, Matthias Schweinoch wrote:> hello,
> 
> i am using wine 20040121, and the windows application i am trying to run
> need to communicate through the serial ports with an attached device.
> the problem is this: whenever i try to communicate with the serial
> device, i get the following error message:
Hi,

I have a fiscal serial printer from Itautec that only works with 
wine <= 20001024 .

Other serial fiscal printers works with newer wines.

Somewhere after that wine, there was a major rewrite in the serial comm
parts (AFAIK).
This probably has to do on how the printer driver acccess the ports.

I suggest you try to see if wine-20001024 is capable of running your
application.
Another problem about this wine is that I couldn't compile it against
newer glibcs and gccs, so you will have to stick with older distros.

[]'s
Raul Dias

Rein Klazes

2004-Jan-29 08:05 UTC

head link

serial port communication - again

On Thu, 29 Jan 2004 13:32:23 +0100, you wrote:
> hello,
> 
> i am using wine 20040121, and the windows application i am trying to run
> need to communicate through the serial ports with an attached device.
> the problem is this: whenever i try to communicate with the serial
> device, i get the following error message:

Matthias,

There is not a single error in the debug trace that you posted. The one
fixme is almost certainly harmless.

I presume it does not work: how do you notice? Does the program report
anything?

> trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
> trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 11
These ClearCommError's are normally used by program's to check for bytes
in the in- and output buffers. Here you see that the program has written
11 bytes.

> trace:comm:ClearCommError handle 0x164 cbInQue = 0 cbOutQue = 0
Lots of those: the program waits for a response.
> trace:comm:ClearCommError handle 0x164 cbInQue = 1 cbOutQue = 0
Here is an incoming byte.

So the program appears to be communicating, hence my question what goes
actually wrong?

Adding the debug option  "--debugmsg +file,+comm" might give more
insight in the communication problem. The resulting output may be much
bigger though, you will need to search the actual ReadFile and WriteFile
calls that the program does to exchange data.

Rein.
-- 
Rein Klazes
rklazes@xs4all.nl

Ivan Leo Murray-Smith

2004-Jan-30 12:42 UTC

head link

serial port communication - again

> Another problem about this wine is that I couldn't compile it against
> newer glibcs and gccs, so you will have to stick with older distros.It would be a good idea to find out what's wrong with the new comm
implementation, or at least opening a bug report, then a developer will look
into it.

Ivan.

wine users - Jan 2004 - serial port communication - again

serial port communication - again

serial port communication - again

serial port communication - again

serial port communication - again