FlexLM and "tcp_s is bad"
bon at elektron.ikp.physik.tu-darmstadt.de
Wed Mar 20 03:54:33 CST 2002
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
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.
Any help appreciated.
Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the wine-devel