[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev Re: Bad DOS lynx binary (Was: Mmory problems in DOS.)
From: |
Gisle Vanem |
Subject: |
lynx-dev Re: Bad DOS lynx binary (Was: Mmory problems in DOS.) |
Date: |
Thu, 28 Oct 1999 09:39:03 +0200 |
Doug Kaufman <address@hidden> said:
>This didn't fix the problem. I made the above changes to select.c and
>pctcp.c and recompiled WATT-32, then compiled lynx dev.12. The http
>download stops again after about 160K. Portion of the lynx trace file
>follows (made before the above changes):
>Read 163101 of 2158694 bytes of data, 1418 bytes/sec.
>Read 163613 of 2158694 bytes of data, 1418 bytes/sec.
>Read 164125 of 2158694 bytes of data, 1418 bytes/sec.
>Read 164637 of 2158694 bytes of data, 1419 bytes/sec.
>Read 165149 of 2158694 bytes of data, 1419 bytes/sec.
>Read 165661 of 2158694 bytes of data, 1419 bytes/sec.
>Read 166173 of 2158694 bytes of data, 1420 bytes/sec.
>Data transfer complete
>LYCloseTempFP
>...LYCloseTempFP(C:\WINDOWS\TEMP\15450.htm)
>start_curses: done.
I've seen this behaviour some versions ago, but was sure it was fixed.
Is it acting like this on every/most servers? I think you should look
in debug-file (wattcp.dbg) to see whats really going on and who
closes the connection first.
Gisle V
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- lynx-dev Re: Bad DOS lynx binary (Was: Mmory problems in DOS.),
Gisle Vanem <=