L.D wrote:
> Lantcp.cfg is used with Waterloo TCP. But I'm not using that as far
>as I know. In fact, looking at the lantcp.cfg file, if I were calling
>on it, I wouldn't be getting through at all because all values are still
>default ... which means inoperable.
It is included in Arachne. Let me quote.
First from wattcp\src\readme.2nd:
"The bootp code now supports dhcp."
>From changes.txt (1.60b1):
Notes: 1.50 stable release was skipped due to release of new version of
WATTCP library.
Improvements: Arachne 1.60 beta is based on WATTCP release "9911" which
should be faster, more stable, and it which supports DHCP.
Finally from Arachne.Cfg:
;IP_Address BOOTP ... WatTcp attepmts to use BOOTP protocol
Conclusion, you (as are we all) are using WatTCP (which is short for
Waterloo TCP).
Please check what your TCPconfig line says (I'm on PPP here - PPPTCP.CFG is
mine called)
;TCPconfig filename ... name of WatTcp configuration file (often WATTCP.CFG)
RTFM (*.cfg) ;-)
>If I can't sent this or can't download, it may be because I went ahead
>and put mss=4096 in the tcp/ip section of Arachne.cfg
If you want to try something like that set mss=0 in arachne.cfg instead.
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...
