Newsgroups:	comp.os.msdos.djgpp
From:	rd5718 AT irix DOT bris DOT ac DOT uk (Rich Dawe)
Subject:	Re: Lib Socket for WinSock2?
X-Nntp-Posting-Host:	irix.bris.ac.uk
Message-ID:	<F5yEK9.H53@fsa.bris.ac.uk>
Lines:	49
Sender:	usenet AT fsa DOT bris DOT ac DOT uk (Usenet)
Organization:	University of Bristol, England
X-Newsreader:	TIN [UNIX 1.3 950824BETA PL0]
References:	<780v40$rb2$1 AT holly DOT prod DOT itd DOT earthlink DOT net> <Pine DOT SOL DOT 3 DOT 91 DOT 990119145652 DOT 15034A-100000 AT fan1 DOT fan DOT nb DOT ca> <F5wqBA DOT I0M AT fsa DOT bris DOT ac DOT uk> <Pine DOT SOL DOT 3 DOT 91 DOT 990121105124 DOT 25146B-100000 AT fan1 DOT fan DOT nb DOT ca>
Date:	Fri, 22 Jan 1999 09:04:57 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Jeff Patterson (aa093 AT fan DOT nb DOT ca) wrote:
: > 	With regard to 1): Specs. Ahahaha. I doubt Microsoft will ever
: > produce specs for the WSOCK2.VXD device driver. If only they would release
: > the source code for it <sigh>
: 
: Has anyone asked directly for any API specs?  I recall seeing MSTCP.VXD 
: api specs somewheres but don't know where at the moment.

	No, I didn't think that would ellicit any response.

	I would like a copy of your specs for MSTCP.VXD if you manage to
find them.

: > 	I think Winsock 2 can be accessed from a DOS box.
:
: Hmm, sounds interesting.  I wonder how much could actually have changed 
: (other than being a 16-bit Prot-Mode interface to a 32-bit Prot-Mode 
: interface (*if* that difference even exists)).

	The 32-bit interface and the 16-bit interface are the same, as one
can find out by dumping the VXD's entry table - the PM and V86 entry
points are the same. I think this is the same for WSOCK2.VXD.

	I think libsocket actually calls the VXD from protected mode - no
16-bit thunks or anything. I think the reason this works is that the VXD
*knows* it's being called from protected mode.

: > 	Perhaps the most irritating aspect of this is that WSOCK.VXD from
: > Winsock 2 is the same (binary compare) as the WSOCK.VXD from Winsock 1.1.
: 
: Current version of WSOCK2.VXD for Win95 does not:
: WSOCK2   VXD        23,203  03-20-98  6:00p WSOCK2.VXD
: WSOCK    VXD        15,547  03-20-98  6:00p WSOCK.VXD

	You misunderstand me WSOCK.VXD from Winsock 1.1 and WSOCK.VXD from
Winsock 2 are the same. It could be that it's not overwritten - doh.

: BTW, is there a new mailing-list for it?  I used to be subscribed to 
: "dossock" but it disappeared.

	Me too. Apparently the list admin's computer crashed and the admin
had no back of the subscriber list. Maybe we should set up another one on
onelist or a similar service?

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

- Raw text -