From:	mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: wsock library -- compliant with memphis tcp/ip stack?
Date:	6 Jul 1997 22:16:21 GMT
Organization:	Oxford University, England
Lines:	23
Message-ID:	<5pp5fl$j9e@news.ox.ac.uk>
References:	<Pine DOT LNX DOT 3 DOT 96 DOT 970705223226 DOT 8077A-100000 AT micro DOT internexus DOT net>
NNTP-Posting-Host:	sable.ox.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Laszlo Vecsey (master AT internexus DOT net) wrote:
: Has anyone gotten around to modifying the wsock library so that its
: compliant with the new memphis tcp/ip stack? 

: Specifically, I'm referring to just getting the existing library to run
: properlly.. which it apparently doesn't (the sample binaries, resolve.exe
: for example, dont run) Or if progress on a winsock2 implementation is
: being made, please point me to it!

Hmm, the sample applications work for me; note however that resolve.exe
(IIRC) requires bootp, to get your nameserver. If you take the time to
read up on how to use the Winsock in general, the library is fairly
self-explanatory - it isn't complete, though, and it is built around
classes. Consequently, you don't pass a socket reference to the calls.
Some other paarameters change slightly too; I think Socket::Send and
Socket::Recv are actually the Winsock's SendTo and RecvFrom, not Send and
Recv. Anyway, the library does work; you might need to tweak it a bit. If
you don't have bootp you need to tell it your nameserver manually before
the resolve function will work.

-- 
George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Merton College, Oxford

- Raw text -