Hey All,
Still working on getting wIntegrate running under Linux. I'm running into problems running the program either in builtin mode or with native dlls. Here are the dlloverrides that I'm trying:
-dll WSOCK32.DLL=native -dll WS2_32.DLL=native -dll NETAPI32.DLL=native -dll ADVAPI32.DLL=native -dll OLEAUT32.DLL=native -dll OLEPRO32.DLL=native -dll OLE32.DLL=native -dll RPCRT4.DLL=native -dll COMCTL32.DLL=native -dll COMDLG32.DLL=native -dll SHLWAPI.DLL=native -dll IMM32.DLL=native -dll IMM32.DLL=native Running with -debugmsg +fixme, I get the following interesting messages:
fixme:file:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:file:DeviceIoControl Unimplemented control 256 for VxD device NWLINK
Once the app starts and I attempt to create a connection, I get this feedback: [Connecting to 127.0.0.1...]
[Windows Sockets error 183]
Am I correct in interpreting this (net helpmsg 183) in that wine is attempting to create a pipe that already exists? If I take the other approach and run wInteg with no dll overrides (builtin mode), i get the following messages fixme:ole:CoRegisterMessageFilter stub fixme:ole:CFProxy_QueryInterface Unhandled interface: {00000126-0000-0000-c000-000000000046}fixme:ole:CFProxy_QueryInterface Unhandled interface: {00020400-0000-0000-c000-000000000046}fixme:ole:PIPE_GetNewPipeBuf Could not open named pipe \.\pipe\WINE_OLE_StubMgr_00000013, le is 2err:ole:StdMarshalImpl_UnmarshalInterface Failed to get an rpc channel buffer for {00000001-0000-0000-c000-000000000046}fixme:ole:CoUnmarshalInterface Failed to Unmarshal the interface, 80004005? fixme:ole:CoCreateInstance no classfactory created for CLSID {4fbf4bd9-a454-11d1-ab39-00a024709830}, hres is 0x80004005
This is what prompted me to try running the app in native mode (since this message goes away if im using native ole dlls.) When running in builtin mode and creating a connection, wInteg sits on the [Connecting to 127.0.0.1] message. But netstat -nap reports: tcp 12 0 127.0.0.1:1220 127.0.0.1:23 ESTABLISHED 8079/wine Of note is that wInteg uses an ActiveX control called wWinSock.ocx. This is in keeping with its modular approach to transports (having plugins for PicLan, Novell etc). Correct me if I'm wrong, but from the error messages concerning OLE, I'm thinking that my problem lies with an incomplete implementation of OLE (or at least ActiveX controls) in Wine. Specifically, I beleive the actual problem is that the wWinSock object is not receiving a signal from Wine that tells it that the connection has been opened. Anybody have any further suggestions/comments?
Thanks Tom