On Wed, Mar 20, 2002 at 10:54:33AM +0100, Uwe Bonnes wrote:
Hallo,
I have a demo of a commercial Linux application, which comes with FlexLM protection but doesn't have a Linux vendor daemon. Running windows flexlm with the windows vendor daemon and --winver win95 --dll netapi32=b works fine and will save me having to run a NT Box with VMWare in the background. Good!
Running Linux flexlm calling the windows vendor daemon via wine however doesn't work. Flexlm aborts with a message "tcp_s is bad!!!". Could this tcp_s be some sequence number that our present winsock implementation does wrong somehow? I can give more evidence on reqeust.
Searching on Google seems to show that tcp_s is generally used to refer to a TCP socket. (so it's probably not a sequence number)