On Sun, 21 Oct 2001, Francois Gouget wrote:
I have been doing some winsock changes recently so I am interesteed in this one. Can you tell me more precisely which version (date) of the winsock works and the one that does not? What happens with the one that does not work? Do you get any error message that would give a hint about what goes wrong?
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.
Maybe a little excerpt from wine-users would do.
Subject: Re: Forte Agent Socket Problems
On Sat, 6 Oct 2001, Jason wrote:
Hi All,
I'm a newbie to WINE, and for my first application I'm trying to set up Forte Agent RedHat Linux (Roswell). I can run it fine (well, there is a constant flow of error messages on my console, but the program window still looks allright). But I can't connect to the internet. This is the message I keep getting:
fixme:winsock:_get_sock_fd handle 164 is not a socket (GLE 6) fixme:winsock:_get_sock_fd handle 164 is not a socket (GLE 6)
I got the latest rpm today, and upgraded the WINE binaries, and the only configuration I did was to make the ~/.wine directory and edit ~/.wine/config file to show my windows configuration, and filesystem mapping.
Anyone have any ideas?
Juno 4 had that problem with Wine-20011004, but if you get this, it is fixed in the current CVS. This is the ID of the patch that fixed it:
ChangeSet ID: 1002311145503006032668054 CVSROOT: /opt/cvs-commit Module name: wine Changes by: julliard@wine2. 01/10/05 15:45:45
Modified files: server : named_pipe.c sock.c
Log message: Added get_file_info support to named pipes and sockets to avoid breaking the get_handle_fd request.
Patch: http://cvs.winehq.com/patch.py?id=1002311145503006032668054
Revision Changes Path 1.5 +20 -1 wine/server/named_pipe.c 1.21 +20 -1 wine/server/sock.c
I think.
Lawson ---oof---
I just applied the first 9 patches in a batch, but that looks like the one that fixed it.