Closed Noeda closed 10 years ago
I looked at it and found nothing unusual. I don't think there is a bug.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668.aspx says that WSAEACCESS comes up if we have no permission to bind to some port or a privileged application has bound to the port with exclusive access. As far as I know, all default Dfterm3 ports are such that you don't need special privileges to use them.
Lightman from the forums:
" I think there is a bug with the -w options, if you don't use the -p option, as well.
I have to specify all the ports and then it works. Otherwise, I get this error:
bind: failed (Permission denied (WSAEACCESS)) "
I'll check if there's anything going on in the code when I have the chance. I think this may be a case of misunderstanding how the command line options work.