Does anyone know how to scroll up and down in a MSDOS command prompt window?
If I print a list or my program has a lot of bugs in it and runs through the
whole screen, what can I do to see the all the errors that are not in the
immediate window?

Does anyone know how to scroll up and down in a MSDOS command prompt window?
If I print a list or my program has a lot of bugs in it and runs through the
whole screen, what can I do to see the all the errors that are not in the
immediate window?

charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
If you are using MS-DOS (and Windows Console and Unix),
the easiest way of redirecting your all printf and fprintf is to
add this in the beginning of your program:
freopen("wherestdoutgoes.txt", stdout);freopen("wherestderrgoes.txt", =
stderr);
This way, you can keep a record of all the text generated by your =
program
using printf(...) and fprintf(stderr, ...) including system errors.
You may chose to only redirect stderr only since stdout is for
normal screen output.
"Antwan Williams" <antwan799 attbi.com> wrote in message =
news:b1c24i$19g1$1 digitaldaemon.com...

Does anyone know how to scroll up and down in a MSDOS command prompt =

window?

If I print a list or my program has a lot of bugs in it and runs =

through the

whole screen, what can I do to see the all the errors that are not in =

Under Linux, you can do:
make 2> err.log
for redirecting stderr to a file. ('1' for stdout). Too bad this does not
work in dos.
- Rajiv Bhagwat
"KarL" <someone somewhere.org> wrote in message
news:b1nl8t$sre$1 digitaldaemon.com...

Yes, but not for stderr
"Nic Tiger" <nictiger progtech.ru> wrote in message
news:b1cung$2jlu$1 digitaldaemon.com...

I can simply redirect output to file and then view this file wherever

you

want: Far, Notepad, etc.
To redirect file add "> filename" (without quotes) at the end of

Sigh..... The title says MS-DOS, please.... I know you are trying to be
helpful.
"Rajiv Bhagwat" <dataflow vsnl.com> wrote in message
news:b1nr7c$vub$1 digitaldaemon.com...

Under Linux, you can do:
make 2> err.log
for redirecting stderr to a file. ('1' for stdout). Too bad this does not
work in dos.
- Rajiv Bhagwat
"KarL" <someone somewhere.org> wrote in message
news:b1nl8t$sre$1 digitaldaemon.com...

Yes, but not for stderr
"Nic Tiger" <nictiger progtech.ru> wrote in message
news:b1cung$2jlu$1 digitaldaemon.com...

I can simply redirect output to file and then view this file wherever

you

want: Far, Notepad, etc.
To redirect file add "> filename" (without quotes) at the end of

The cmd.exe shell redirects stderr when fed
tokens as shown in the following session:
C:\Work>dir NotAFilename 2>yap
Volume in drive C has no label.
Volume Serial Number is 5C76-EEA2
Directory of C:\Work
C:\Work>type yap
File Not Found
C:\Work>dir NotAFilename >yap 2>&1
C:\Work>type yap
Volume in drive C has no label.
Volume Serial Number is 5C76-EEA2
Directory of C:\Work
File Not Found
C:\Work>
If you are using command.com, then there is
no hope of doing anything sensible with it.
--
-Larry Brasfield
(address munged, s/sn/h/ to reply)

If you are using command.com, then there is
no hope of doing anything sensible with it.

Doesn't all DOS power-users use 4DOS? Is so it's easy:
"command >&> file".

I almost put in a plug for JP Software's CLI
shells, but decided to stick to the subject.
I find it easier on my brain to stick with
the redirection syntax used by cmd.exe, (also
accepted by 4NT), since from time to time I
have to use some crippled system that lacks
a decent shell.
--
-Larry Brasfield
(address munged, s/sn/h/ to reply)