Date: Sun, 6 Jul 1997 15:57:19 -0400 (EDT)
From: Laszlo Vecsey <master AT internexus DOT net>
To: Stewart <slstewart AT infocom DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: wsock library -- compliant with memphis tcp/ip stack?
In-Reply-To: <33BFF2EC.3563@infocom.net>
Message-ID: <Pine.LNX.3.96.970706155333.32350A-100000@micro.internexus.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Sun, 6 Jul 1997, Stewart wrote:

> Laszlo Vecsey wrote:
> > 
> > Has anyone gotten around to modifying the wsock library so that its
> > compliant with the new memphis tcp/ip stack?
> > 
> > Specifically, I'm referring to just getting the existing library to run
> > properlly.. which it apparently doesn't (the sample binaries, resolve.exe
> > for example, dont run) Or if progress on a winsock2 implementation is
> > being made, please point me to it!
> 
> I'm hacking on the library a little...  to my knowledge, resolve never
> worked (i'm working on a real resolver).  Also this library accesses the
> VxD, not the .DLL so I don't know that winsock2 means anything at this
> le vel.  
> 
> What are the differences between Memphis winsock and normal winsock?

What i've noticed (with resolve, pre-compiled and compiled myself) is that
resolve fails on Memphis.. reporting some vxd error. It works fine with
stock Win95, even with all the ie4.0 service pack upgrades etc.

It seems to me Memphis is now using the winsock2 standard, which is
backwards compatible with regular winsock, but that as you say in the
djgpp wsock library it was probably not implemented correctly/completely
in the first place.. 

I'm glad there is someone else out there looking into this, I will now be
upgrading my main system to memphis... this was the primary reason holding
me back ;)

- lv