Skipping lines could be at the head (start of stream), tail
(end of stream), or within the stream.
As far as I can tell they are always skipped from the start of the stream.
Sometimes with no effect on the screen, sometimes I see the screen being
We don't know if you are redirecting or piping a program's
output or using command-line args to more.com to specify
I'm piping the output of another command into it. No arguments.
I don't see how anything video card related would affect
the content of a stdout or stderr stream.
Why would you think it does or should do ? All I see is that output
directed at the screen disappears, sometimes without a trace. Mind you,
when I redirect the output to a file instead of to the screen I see all the
data I expect.
Are you running it in a console (command shell, cmd.exe)
so the console remains after the program ends?
Does "skipping" mean you don't see the lines on the screen or
that they are truncated in the console window?
See above. Sometimes I see nothing, sometimes I just see the screen
scrolling up or the cursor moving down.
And by the way, pressing "=" to show the line number displays, AFAIK, the
correct one, 24.
Does the console's window have scrolling enabled?
No. I've used MODE CON to set an old-school 80x25 screen.
Have you tried "more.com file otherfile
No, but I just have (good catch btw). A filecompare with an earlier
outputted file (no MORE, directly to file) shows no differences.
Hmmm... odd ....
I saw you asking about what commandline I ran, and skipped answering it
because the piping should isolate the two programs from each other (using an
Nevertheless, I seldom let such questions go without trying to make sure I'm
right. So, I also ran the command "... bla & more bla". That worked
every time I tried it. Which, I might say, is quite unexpected. What is
going on here ?
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).
-- Origional message:
VanguardLH schreef in berichtnieuws
R.Wieser wrote on 2016/01/14:
I threw together a small program emulating a basic MORE program, and
it failed pretty-much the same way.
Either my OS has got problems or, more likely, there something wrong
video card and/or driver ... I've already tried to disable hardware
accelleration, but that did not seem to help.
Alas, we still don't know what you are doing. Skipping lines could be
at the head (start of stream), tail (end of stream), or within the
stream. We don't know if you are redirecting or piping a program's
output or using command-line args to more.com to specify a file.
I don't see how anything video card related would affect the content of
a stdout or stderr stream. Those don't even require video. Those are
data streams, not video streams. I don't even need a video card
connected to a monitor for more, type, Notepad, or any other program to
work correctly. Me not seeing it does not equate to the program not
producing expected results.
What are you running? What is the command? Are you running it in a
console (command shell, cmd.exe) so the console remains after the
program ends? Does "skipping" mean you don't see the lines on the
screen or that they are truncated in the console window? Does the
console's window have scrolling enabled? If so, does scrolling still
have the missing lines? is the console's window partially offscreen?
Have you yet tried booting into Windows' safe mode to make sure
something you load on startup and login are not affecting however you
are trying to view output from more.com?
Have you tried "more.com file otherfile & notepad otherfile" to see if
all the lines are there when viewing the stdout stream in Notepad
(instead of on the screen within the console window)?