From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	WSOCK2.VXD [Was: Re: Async COM managing]
Date:	Sat, 06 Jan 2001 15:58:45 +0000
Organization:	Customer of Energis Squared
Message-ID:	<3A5740B5.A08DE7E1@phekda.freeserve.co.uk>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1001224081539 DOT 7747E-100000 AT is> <9250eb$a84$00$1 AT news DOT t-online DOT com> <h2ob5t4eb075dfi877bu18r88kug5qq66i AT 4ax DOT com> <557-Fri05Jan2001203419+0200-eliz AT is DOT elta DOT co DOT il> <936lkf$7mj$01$1 AT news DOT t-online DOT com> <6137-Sat06Jan2001145950+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host:	modem-63.carbon.dialup.pol.co.uk
Mime-Version:	1.0
X-Trace:	newsg4.svr.pol.co.uk 978797723 31262 62.136.5.63 (6 Jan 2001 16:15:23 GMT)
NNTP-Posting-Date:	6 Jan 2001 16:15:23 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586)
X-Accept-Language:	de,fr
Lines:	36
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> The problem with this interface is not how to access it---this is
> documented in RBIL---but what data structures to use, how to lay them
> out, and what values to use for some of the flags.  If that is
> documented by Microsoft, then the problem is solved (but then I wonder
> how come it took such a long time for Rich Dawe and friends to find
> the way to make the Wsock2 interface work).

Unfortunately the WSOCK2.VXD interface is completely undocumented. In
fact, the WSOCK.VXD interface is only "documented" by a header file. It's
a big jump from a header file to a known interface. The DDK documentation
is constantly criticised for not having enough detail, not documenting
vital interfaces, assumptions, etc.

The only thing I discovered about the WSOCK2.VXD interface was that it was
different than the WSOCK.VXD interface. ;) All the credit for the
discovery goes to other people. See:

    http://www.phekda.freeserve.co.uk/richdawe/dossock/

for more details.

I've coded up an interface to WSOCK2.VXD for libsocket, but there are a
couple of snags. The first one is that you need to apply a patch to bugfix
WSOCK2.VXD. The second is that I haven't had enough time to do fix the
first snag. It's looking hopeful - you can create a socket, connect and
close the socket. Sending and receiving data does not work (snag #1). As
ever, it's just a question of time.

Bye, Rich =]

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]

- Raw text -