Message-Id:	<199709211256.IAA27205@delorie.com>
Comments:	Authenticated sender is <dwi AT netc DOT com>
From:	"Chad Catlett" <dwi AT hsnp DOT com>
Organization:	Don't Need An Organization! :)
To:	djgpp AT delorie DOT com
Date:	Sun, 21 Sep 1997 07:54:30 +0000
MIME-Version:	1.0
Subject:	Re: Win98 wsock.vxd (libsocket, WSock)
Reply-to:	dwi AT netc DOT com
CC:	master AT internexus DOT net

From: Laszlo Vecsey <master AT internexus DOT net>

>Has anyone gotten the WSock classes or libsocket-0.4 to work with
>Win98? I've had a fair amount of success with stock Win95, but Win98
>just chokes on the executables. - lv

 i have never used libsock-0.4. but wsock i have. the reason that 
wsock will not work is that it goes thru the winsock vxd file instead 
of thru the dll, this meaning that the offsets for functions could 
change with a new version. if i remember correctly win98 uses winsock 
2.0 instead of 1.x. this would mean it has more stuff and the vxd 
would must certianly change. the only way i know that this problem 
could be solved is to make a program similar to mpath(quake for dos 
uses this) and release it as freeware or something. mpath sets up a 
software interrupt and you can communicate to winsock thru it 
somehow, i dont know enough  about this so i'll not make a fool outta 
my self and explain it totally wrong, anyone an mpath expert here?



==============
 Chad Catlett
 dwi AT netc DOT com
==============

- Raw text -