I have tested with a winsock client I wrote and mingw32 and it works fine, however you are not possibly using low portnumbers ?


if lower than 1024 ( or 2048 ) wine will not access them from user space, so something like 10000 would be nice for testing.

I don't know if this is the problem, just a guess ...

/ Lars Segerlund.

Mike Hearn wrote:
Seems that for whatever reason Wines winsock simply isn't being loaded.

I'd double check that it's not using a builtin version, and try with a
+loaddll trace to ensure that winsock builtin is actually being used
(otherwise i'd expect to see some winsock trace output).

thanks -mike

On Wed, 2003-07-02 at 17:42, Ferenc Wagner wrote:

Hi,

I decided to forward this from the user newsgroup (having
read the latest WWN :))
                                          Feri.

From: [EMAIL PROTECTED] (Steve)
Newsgroups: comp.emulators.ms-windows.wine
Subject: Simple TCP client (winsock) does nothing
Date: 30 Jun 2003 13:59:17 -0700
Message-ID: <[EMAIL PROTECTED]>

I am testing the winsock.dll in RH9 with a Visual Basic program
running under WINE.  This is the most simple winsock client I could
write... in fact, its copied directly out of the "Using Winsock
Control" in MS sample docs.  One button to connect to a server and
another to send data to the server.  Works fine on a Windows box, but
fails under WINE.

I say "fails" but it doesn't do anything.  My server (on the LAN)
doesn't recieve a connect request when you click the connect button on
the client... it doesn't see anything from the client.  I can click
the connect and nothing happens, click send and nothing happens.  No
errors, but no data transfer either.  No firewall is configured.  I
did copy a mswinsck.ocx to the windows/system directory but its using
WINE's winsock.dll.

I have installed and run VNC bidirectionally between the same two
boxes (Linux and Windows) so I know there is a good IP connection. Any direction is greatly appreciated by one whose struggling to learn
Linux and WINE at the same time. Below is a copy of --debugmsg
+winsock for what its worth.


Thanks,

Steve Ricketts

[EMAIL PROTECTED] Exe]$ wine --debugmsg +winsock TCPClient
Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
Could not stat /cdrom (No such file or directory), ignoring drive D:
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:OLEPictureImpl_Construct Unsupported type 3
fixme:win32:PE_CreateModule Security directory ignored
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:MSFT_DoTypeInfo Assign constructor/destructor memid
fixme:ole:ITypeInfo_fnInvoke set 0 to pointer for get (type is 12)
fixme:ole:ITypeInfo_fnInvoke set 1 to pointer for get (type is 12)
fixme:ole:ITypeInfo_fnInvoke Does not support optional parameters (2)
fixme:ole:CoRegisterMessageFilter stub
[EMAIL PROTECTED] Exe]$




Reply via email to