Closed sebpouteau closed 7 years ago
When we created Dashel in the first place, we checked that the chat worked on Windows. Maybe we made a change at some point that broke stdin:
. I do not have Windows right now, but the best to debug would be to run a simple test program in a debugger and see where the error happens.
From your test with chat, it seems that there is a standard input feature, "immediate", that cannot be set. The best would be to ask a win32 export, if none is available, a search on the net would certainly help.
It seems that the error happens in dashel-win32.cpp
line 407. I do not know why on your computer Windows cannot set these console options.
Chat has never worked for me on the Windows instances hosted by the CI platform. I had always assumed that I was using the wrong command-line arguments. Is there an example of proper usage somewhere?
When Dashel was created, in 2007, chat
worked on Windows. Maybe recent Windows version dropped support for some console-related syscalls?
I've added the display of the system error message in Dashel, and it returns error code 6. A search in Google shows this post. I confirm that with using the Windows command line instead of a msys/cygwin terminal it works. I close the issue.
I've added an issue in Dashel to keep track of this limitation.
Yes, from the Command Shell it works on our Windows instances.
hello,
As part of the programming project which consists in distributing the enki display, we use dashel. We encounter a problem with the Windows platform.
It fails during the connect(stdin).
Error:
As the client code is similar to the example "chat.c" contained in dashel, I try to make it run it turns out that it does not either:
I'm open to any idea about how I could fix this.
Thanks.