JJ,

Have you tried using the Unicode mode of CMD?

No, I haven't. I was not even aware that it's there ...

But, I think I've narrowed down on the cause: By replacing the text sourcing
program with something else the problem disappears. Also, that program is
legacy, traveled with me from my DOS times ... It appears to somehow
either interfere with the screen, or, as VanguardLH suggested, with the
stream outputted by the MORE program (gobbling-up its stdout stream as long
as it runs ?).

In short, its appears not to be either the "more" program nor the display
driver, but just a legacy program being oblivious to the possibility that a
piped-to program can run while it itself is also (still) running (which was
not possible in the era of DOS, nor of the command consoles of earlier
versions of Windows).

So, it looks I have to replace that legacy program.

Regards,
Rudy Wieser


-- Origional message:
JJ schreef in berichtnieuws
...
On Fri, 15 Jan 2016 11:13:00 +0100, R.Wieser wrote:

I could point fingers at the specific program sourcing the piped text,
but
I'm a lot more interrested in knowing what causes MORE's behaviour, and
how
I can fix it (instead of compiling a list of programs I should not use
in
combination with it).

Have you tried using the Unicode mode of CMD?