Newsgroups: comp.os.msdos.djgpp
From: rd5718 AT irix DOT bris DOT ac DOT uk (Rich Dawe)
Subject: Re: req: tcp lib that will work with the microsoft tcp/ip stack....
Message-ID: <EM98E8.9JC@fsa.bris.ac.uk>
Sender: usenet AT fsa DOT bris DOT ac DOT uk (Usenet)
Organization: University of Bristol, England
References: <34AA1D0C DOT 3621 AT wxs DOT nl> <EM4FD8 DOT JBy AT fsa DOT bris DOT ac DOT uk> <01bd174e$f4439680$e4fdcccf AT damien>
Date: Sun, 4 Jan 1998 10:13:20 GMT
Lines: 24
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Damien (damien@%poe.org) wrote:
: Rich Dawe <rd5718 AT irix DOT bris DOT ac DOT uk> wrote in article
: > libsocket may not work with Winsock 2 however.
: 
: It probably doesn't.  I use WSOCK, & all my WSOCK programs would crash as
: soon as they hit the SocketInit() function after I installed Winsock 2 (so
: I uninstalled it, of course).  I think I remember hearing libsocket was
: based on WSOCK.

	libsocket is based on WSOCK. The behaviour with Winsock 2 is
strange. Things like getprotobyname and getservbyname work fine, but
creating sockets doesn't. libsocket uses a DOS function call to use
WSOCK.VXD's functionalit. I guess M$ changed how this VxD works between
Winsock 1 and 2, breaking libsocket and other libraries in the process :(
Does anybody have any information about Winsock 2?

	Cheers, Rich Dawe.

-- 
==============================================================================
              Rich Dawe - 3rd year Physicist @ Bristol Uni, UK
E-mail: rd5718 AT bristol DOT ac DOT uk        Web pages: http://irix.bris.ac.uk/~rd5718/
==============================================================================