On Thu, Dec 11, 2008 at 8:40 AM, kbbass <wineforum-user@xxxxxxxxxx> wrote: > > 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? >> >> -- >> -Austin > > > The 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 > > > > > > A) Can you test and see how much of the key is needed? I.e., try deleting a bit at a time to see when it stops working? B) Is there some reason you can't name the application? -- -Austin
