Hello,
Me again.
Here is a patch that makes it work. I'm probably doing something
terrible here, but it solves the problem for now. I'm piggy-backing on
the code for handling FD_TYPE_SOCKET, because I noticed that if I treat
a serial port with:
ReadIntervalTimeout=MAXDWORD
ReadTotalTimeoutM
Nope, now the app just dies with very little trace as to why. Not to
worry, I just need to go eat some lunch or something and get my head
clear. This conversation has given me a much clearer understanding of
what goes on.
Mike McCormack wrote:
Izak Burger wrote:
Ok. I had to set +comm to ge
Izak Burger wrote:
Ok. I had to set +comm to get that info, and modified the code to dump
the contents of the COMMTIMEOUTS structure:
trace:comm:SetCommTimeouts ReadIntervalTimeout=4294967295
trace:comm:SetCommTimeouts ReadTotalTimeoutMultiplier=0
trace:comm:SetCommTimeouts ReadTotalTimeoutCons
Thanks for the speedy reply.
Mike McCormack wrote:
The wineserver may also change the status of the request to
STATUS_SUCCESS after a certain timeout is reached. The problem is most
likely that the timeout is not being calculated properly.
>
> The code to do that is in server/async.c and server
Hi Izak,
The wineserver may also change the status of the request to
STATUS_SUCCESS after a certain timeout is reached. The problem is most
likely that the timeout is not being calculated properly.
The code to do that is in server/async.c and server/serial.c.
The timeouts are set by the SetCo
I end up showing my ignorance :-)
Ok, I see how it is supposed to work, so I changed it back to
FD_TYPE_DEFAULT. It looks like my real troubles is caused by the
snippet of code that decides when the read is successful:
if (io_status->Information >= fileio->count
|| fileio->fd_type == FD_TY
Izak Burger <[EMAIL PROTECTED]> writes:
> I'm currently debugging a problem with serial comms over wine, and I
> see that when a serial device is opened (in server/serial.c) the
> serial_get_info function returns a type of FD_TYPE_DEFAULT, which in
> turn causes the serial device to be read from a
Hello,
I'm currently debugging a problem with serial comms over wine, and I see
that when a serial device is opened (in server/serial.c) the
serial_get_info function returns a type of FD_TYPE_DEFAULT, which in
turn causes the serial device to be read from and written to with pread
and pwrite i
