I'm using Console2, which is a very versatile Windows command prompt replacement.
When starting colinux as an nt terminal from inside Console2 (colinux-daemon -t nt), this results in a crash. What causes this problem and is there a solution?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, this Console2 is not compatible to standard MS functions for console handling. For example "WriteConsoleOutput" does not view the chars inside the console, or the function SetConsoleActiveScreenBuffer is not supported.
Here have a binary for your test under normal CMD.EXE and under Console2. You will see the different: Console2 does not output anything of the letters "a b c", and sometimes it kills it self.
You should post that as bug in Console2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using Console2, which is a very versatile Windows command prompt replacement.
When starting colinux as an nt terminal from inside Console2 (colinux-daemon -t nt), this results in a crash. What causes this problem and is there a solution?
Sorry, this Console2 is not compatible to standard MS functions for console handling. For example "WriteConsoleOutput" does not view the chars inside the console, or the function SetConsoleActiveScreenBuffer is not supported.
This example from MS kills the console in same way:
Reading and Writing Blocks of Characters and Attributes
Here have a binary for your test under normal CMD.EXE and under Console2. You will see the different: Console2 does not output anything of the letters "a b c", and sometimes it kills it self.
You should post that as bug in Console2.
Solution: Run colinux-daemon.exe with option -d, and run colinux-console-nt.exe outside of Console2 later, for example from Desktop shortcut.
Thanks for the reply. I'll post a bug report for Console2.