Date: Mon, 25 Jan 1999 15:08:26 +0000 (GMT)
From: "Rich N.S. Dawe" <rd5718 AT bristol DOT ac DOT uk>
To: Michael Callahan <mjc AT rodagroup DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Coda has TCP/IP and annonymous mmap for DJGPP on W95
In-Reply-To: <Pine.SGI.3.94.990122190001.1797A-100000@evelyn.smith.edu>
Message-ID: <Pine.SGI.3.95q.990125144758.642A-100000@irix.bris.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com

Hello.

>   - access to Windows 95's built-in TCP/IP networking
> 
> The TCP/IP support allows a DJGPP program to access the Windows 95 kernel
> networking stack using a Berkeley sockets API.  The bulk of the code is
> a VxD that implements the Berkeley sockets API using the semi-documented
> in-kernel TDI API to the W95 networking stack.

	I maintain a library for DJGPP, libsocket
(see http://libsocket.ml.org/), that provides a BSD socket interface,
but takes a different route. It communicates with the Winsock VxD
WSOCK.VXD directly. Unfortunately it only works with Winsock 1.x and
not Winsock 2.0. Does your VxD allow DOS programs to use Winsock 2?

	Also, does it allow protocols other than TCP and UDP to be used,
e.g. ICMP, that are supported by Winsock 2? Is the BSD interface support
complete?

	I would be extremely happy if I could put Winsock 2 support into
libsocket. It's been bugging me for ages.

> I should note, by the way, that there are still some very obvious holes in
> these extensions.  For example, there's no resolver library for TCP/IP,
> and there are doubtless some bugs.

	libsocket uses the Linux resolving code, and this works fine. It
is fairly tricky to configure, however.

==============================================================================
         Rich Dawe - 4th-year MSci Physicist @ Bristol University, UK
           richdawe AT bigfoot DOT com, http://www.bigfoot.com/~richdawe/
==============================================================================