Brian Craft wrote:
>
> This is following up the problem I reported earlier, where during a scan, at the
> last second xsane-win32 reports an IO error during read & erases the output
> file.
>
> The IO error occurs when reading the next buffer length in
> sane_read() in net.c, i.e. right after "if (s->bytes_remaining == 0)".
> The error occurs on about the 3rd from last buffer that is sent.
>
> Comparing the debug output of xsane-win32 with a trace of the
> TCP data connection, the win95 box is returning the error on read()
> even though the stack has already ACK'd the rest of the stream. I.e.
> they've been received by the stack, but read() fails. WTF?
>
> When the linux box finishes sending the data it sends a FIN, the win95 box
> sends a couple ACK's, and the linux box sends a RST.
>
> Could the RST be causing the socket to be shut down asynchronously? so RST
> arrives, the socket shuts down, read() returns error with data sitting in
> the buffer?
>
> Anyone have any clue what would cause problems like this?
>
>
Hi Brian,
do you use sane-1.0.3 on the server?
Are you able to test xsane-win32 with an other
computer with winNT or win98?
Does anyone else have that problem?
I did several tests with win98SE to a linux box
and with winNT to a SGI and never had that problem.
What happens if you scan large images (600 dpi A4 size)?
bye
Oliver
-- Homepage: http://www.wolfsburg.de/~rauch sane-umax: http://www.wolfsburg.de/~rauch/sane/sane-umax.html xsane: http://www.wolfsburg.de/~rauch/sane/sane-xsane.html E-Mail: mailto:Oliver.Rauch@Wolfsburg.DE-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Wed Oct 18 2000 - 09:18:05 PDT