I am trying to get a proprietary app's windows service running in Wine. When I try to start the service, I get this: err:eventlog:ReportEventW L"System error 10044: Socket type not supported." I have copied all dependant DLLs from a Windows installation, but still the same error. I know that this service is trying to set up a socket to listen on, but I'm not sure of the specifics, especially the type. Anyone have any ideas? Getting this to work here would be great, since I won't need to set up a separate Windows box just for this service. TIA ken
kbbass wrote:> I am trying to get a proprietary app's windows service running in Wine. When I try to start the service, I get this: > > err:eventlog:ReportEventW L"System error 10044: Socket type not supported." > > I have copied all dependant DLLs from a Windows installation, but still the same error. > > I know that this service is trying to set up a socket to listen on, but I'm not sure of the specifics, especially the type. > > Anyone have any ideas? Getting this to work here would be great, since I won't need to set up a separate Windows box just for this service. > >Do you know what protocol and port this product listens on? That would give us a start. It is possible that Linux does not know which port to use. James McKenzie
kbbass wrote:> > Anyone have any ideas?it's easier if you tell us the name of the program and if there is somewhere to get a demo/trial copy
austin987 wrote:> > So perhaps we need to propagate that key to support that app. What was > in that key? > > > -- > -AustinI can send you the exported key file if needed, but it might be easier to just go to any windows installation and look for yourself. It seems to be just an enumerated listing of supported protocols with descriptions. ken
austin987 wrote:> > I didn't have a windows box handy at the time. How much of that key > needs to be present? Does it just need the Winsock2 key? The version > key? > > What app is this? > > -- > -AustinThe contents of the key seem to be a list of supported network types. Looking at the debug output, the app enumerates the entries in both branches (under the Parameters key). So the only entries you would need would be for whatever network types are available on the linux system. Also, I believe (not 100%) that it is not my app that looks at this key, but maybe the WSock2 DLL itself, when it gets loaded. My app simply listens for incoming tcp connections on one port. Nothing too exotic. BTW: this is a server that is a backend to a proprietary (ie, not available publicly) graphics application suite . The network part is simply the doorway for processing requests. ken