*shrug*, sometimes console2 crashes for me, and that sometimes takes out all the running console apps as well.
Well, yeah, they would be considered child processes of Console, and when the parent croaks, so do the kids.
And by "fullscreen" I didn't mean alt+enter fullscreen, but "GUI console apps" - at least a few of them work very poorly with console2.
Oh, OK. The main one I tried that had heartburn was SETEDIT. The DOS version insisted
on running full screen, and could not be resized into a window. If you installed the DOS version, then copied over the EXE for the Win32 console build, it would resize, but Console didn't like it at all. That author had no idea what was going on. He wrote it using a Borland toolkit, and something in the Borland library code did things that mightily confused Console.
If those problems were fixed, it would be a really great app, having tabs certainly beat several open cmd.exe windows
It works well enough here for me to use it regularly.