From: Jeff Patterson <aa093 AT fan DOT nb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Lib Socket for WinSock2?
Date: Thu, 21 Jan 1999 10:57:27 -0400
Organization: Fredericton Area Network
Lines: 48
Message-ID: <Pine.SOL.3.91.990121105124.25146B-100000@fan1.fan.nb.ca>
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>
NNTP-Posting-Host: 24.231.28.194
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <F5wqBA.I0M@fsa.bris.ac.uk> 
X-No-Archive: Yes
Cache-Post-Path: fan1.fan.nb.ca!aa093 AT localhost
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Thu, 21 Jan 1999, Rich Dawe wrote:

> Jeff Patterson (aa093 AT fan DOT nb DOT ca) wrote:
> : Unfortunately it simply ain't the same thing.  It is unlikely there will 
> : ever be a libsocket for WinSock2 as:  1) no one can get a hold of the specs 
> : for it.   2) I have heard rumors that WinSock2 cannot be accessed through 
> : a DOS session (neither DPMI nor Real-Mode).  As to whether the second is 
> : true or not, I haven't found anyone that knows.
> 
> 	I wish I could add Winsock 2 support to libsocket. It's at the top
> of my to-do list for libsocket.
> 
> 	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.
 
> 	I think Winsock 2 can be accessed from a DOS box. I haven't 
> checked it myself, but here is some justification. Dan Hedlund, the author
> of the WSOCK C++ library, originally found out how to use WSOCK.VXD
> device driver from a DOS box [*]. He is investigating how to use
> WSOCK2.VXD. He told me that he has got creation and destruction of sockets
> working, but not sending/receiving. So, hopefully he'll work out the
> remainder soon, and Winsock 2 support can be added.

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)).
 
> [*] libsocket is based on Dan Hedlund's code from his WSOCK library.
> 
> 	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.
> I have no idea why it does not work.

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

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

-- 
 Jeff Patterson                       Internet: aa093 AT fan DOT nb DOT ca
| PGP Info: 2048/A8A1DCD5 : E0 9E 9B EF C8 E4 68 3D  B5 9C 72 4C EC 61 DD 7A |