OK I didn't get it. I still don't understand why such a cause would be visible
on a customer PC and not on a similar PC in our office. That doesn't make sense
to me. But I'll gather some information about any such limitation.
Reason for using Windows is that our software (a realtime 3D visualisa
> On Jan 23, 2023, at 7:41 AM, g.jaegy wrote:
>
> OK I keep that hint in mind as well.
>
> So according to the documentation I could gather, increasing that limit on
> Windows seems to consist in defining FD_SETSIZE with a higher value (default
> being 64) before including "Winsock2.h" head
OK I keep that hint in mind as well.
So according to the documentation I could gather, increasing that limit on
Windows seems to consist in defining FD_SETSIZE with a higher value (default
being 64) before including "Winsock2.h" header. I can easily do that in our
code.
I assume I'll however h
