Eric Auer wrote:
> To clarify: Wattcp and Watt/32 IS a tcp/ip stack, but you
> do not INSTALL it. Instead, programs contain wattcp as part
> of their binary. All Wattcp does use the same wattcp.cfg
To clarify again: At least older versions around 1991/92 were available
as TSRs too.
Robert Riebis
> of Linux or Windows. This means that for example you have
> to wait until your app gets a new DHCP lease every time
> when you start it, because no central networking driver
> of the operating system would be around to cache that.
IIRC watt-32 (not sure about wattcp) caches this info in file
%T
To clarify: Wattcp and Watt/32 IS a tcp/ip stack, but you
do not INSTALL it. Instead, programs contain wattcp as part
of their binary. All Wattcp does use the same wattcp.cfg
file, though :-). Note that DOS has no tcp/ip stuff in the
operating system that could be compared to the tcp/ip stuff
of L
Wattcp isn't really a stack that one can install, really. Yes it can
use a global configuration setup, but each application must be built
with the wattcp library to be able to utilize this configuration.
Applications built with other networking 'stacks' require different
configuration, obviously :
Guillermo Mart?nez Jim?nez wrote:
>
>Hello Freedosoyds ;-)
>
>I want to connect my FreeDOS to the Internet. Do I need a TCP/IP stack? If so,
>how must I set-up it?
>
>Thanks. (sorry for my bad english).
I don't know if Erick Engelke's WATTCP can be classified as a
TCP/IP stack, but it works.
