Several comments about the above: %_WinCols yields no number for me, ever, less than 80 (somewhat ironically given what Vince says vs. what Rex "suggests" in the above), and, not only that, "Echo %_WinCols" yields a "null" string (i.e., "Echo is OFF") in a stand-alone TCC session, which is certainly not any better if not actually worse. (And Rex, I want to do this because I, like Vince if nobody else so far in this thread, often have very long running batch files (as in many hours) that I run in stand-alone TCC and/or Take Command windows that I keep in the "corner" of screen to kind of "monitor" in the background and that sometimes produce error (or "warning") messages that I want to know the full "details" about just by glancing at the window in the corner of the screen. Put simply, I am quite disappointed if that is not possible because that is, exactly, what I really want to do. (I've been considering putting a "message box" up when that happens, but I haven't yet decided whether to do that because I like the way things are (should be) now: When the batch file has a "problem" it displays the message and then "pauses" until I hit a key of some kind - particularly the "[Esc]" key meaning I want to abort the whole thing, and I'd really rather not have that message box "interrupt" what I am doing at any present moment - I get distracted and lose track of what I am doing very easily.)
So, the only question remaining here is "why doesn't 4Console do what Vince thinks is should do?"