cvs.gedasymbols.org/archives/browse.cgi | search |
Date: | Mon, 22 Sep 1997 09:27:32 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
To: | Laszlo Vecsey <master AT internexus DOT net> |
cc: | dwi AT netc DOT com, djgpp AT delorie DOT com |
Subject: | Re: Win98 wsock.vxd (libsocket, WSock) |
In-Reply-To: | <Pine.LNX.3.96.970921182637.21689A-100000@micro.internexus.net> |
Message-ID: | <Pine.SUN.3.91.970922092712.11436F-100000@is> |
MIME-Version: | 1.0 |
On Sun, 21 Sep 1997, Laszlo Vecsey wrote: > So in other words, the way in which a VxD is called is still done the same > way (I pasted a code snipet below, from WSock) its just that the > CallVxD(offsets) have changed? That's one possibility. Another possibility is that Winsock 2.0 in Windows 98 is an entirely different VxD, with a different device ID. So programs that call the Windows 95 VxD are trying to use a driver that's not there.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |