Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <397222FD.9EAFFD54@phekda.freeserve.co.uk>
Date: Sun, 16 Jul 2000 22:02:53 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Sparrow <the_mr_sparrow AT my-deja DOT com>
CC: DJGPP newsgroup <djgpp AT delorie DOT com>
Subject: Re: Winsock Difficulties
References: <8klgqg$6st$1 AT nnrp1 DOT deja DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

Sparrow wrote:
> After I finally managed to successfully compile the WSock chat demo, I
> run them and get strange errors. For example, when running CHAT1.EXE, I
> get the following error messages:
> 
> Wsock: Function SOCKET(110) returned WSAEAFNOSUPPORT - Address family
> not supported by this protocol(273f)
> Wsock: Function CONNECT(103) returned WSAEINVAL - Invalid argument(2726)
> 
> CHAT2.EXE gives the following error in an endless loop:
> 
> Wsock: Function ACCEPT(100) returned WSAEINVAL - Invalid argument(2726)

From "Wsock chat demo", it sounds like you are using Dan Hedlund's WSOCK
library. From the error messages it looks like your Windows networking is
provided by Winsock 2. Unfortunately, WSOCK only works with Winsock 1.x.
To confirm you have Winsock 2, look in your Windows system directory for a
file call WSOCK2.VXD, e.g.:

dir c:\windows\system\wsock2.vxd

If this file is present, you are probably using Winsock 2. Which version
of Windows '95/'98 are you using?

libsocket works with Winsock 2:

http://libsocket.tsx.org/

There are a few limitations when working with Winsock 2, unfortunately.
See the list of bugs on the above page.

Hope this helps, bye,

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]