Date:	Tue, 26 Jan 1999 00:22:46 -0500 (EST)
From:	Michael Callahan <mjc AT rodagroup DOT com>
X-Sender:	mjc AT evelyn DOT smith DOT edu
To:	Rich Dawe <richdawe AT bigfoot 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.95q.990125144758.642A-100000@irix.bris.ac.uk>
Message-ID:	<Pine.SGI.3.94.990126001810.15582A-100000@evelyn.smith.edu>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

On Mon, 25 Jan 1999, Rich N.S. Dawe wrote:

> >   - 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?

Since my VxD is independent of WSOCK and the WinSock DLL, it shouldn't
matter whether you have Winsock 1.x or 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?

No, just TCP and UDP at this time.  I'm trying to remember if the BSD
interface is complete.  I'm not sure--I think e.g. that it may be that not
everything that you should be able to make nonblocking, is able to be made
nonblocking.  Peter, do you know about this?

Michael

- Raw text -