Mail Archives: djgpp/1999/01/21/07:30:53
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>
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.
[*] 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.
--
==============================================================================
Rich Dawe - 4th-year MSci Physicist @ Bristol University, UK
richdawe AT bigfoot DOT com, http://www.bigfoot.com/~richdawe/
==============================================================================
- Raw text -