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?

Which operating system are you using?
In Windows XP I have a command prompt configured with.
Options:
    Cursor Size: Small
    Display Options: Window
    Command History
        Buffer Size 999
        Number of Buffers 4

Font:
    Size: 8 x 12

Layout:
    Screen Buffer Size:
        Width: 80
        Height: 1024 (you can scroll SEVERAL pages back with this.
    Window Size:
        Width: 80
        Height: 48

HTH
Jan



Antwan Williams wrote:

> 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?

I have Windows 98.
"Jan Knepper" <jan@smartsoft.us> wrote in message
news:3E39A5F8.7F195530@smartsoft.us...
> Which operating system are you using?
> In Windows XP I have a command prompt configured with.
> Options:
>     Cursor Size: Small
>     Display Options: Window
>     Command History
>         Buffer Size 999
>         Number of Buffers 4
>
> Font:
>     Size: 8 x 12
>
> Layout:
>     Screen Buffer Size:
>         Width: 80
>         Height: 1024 (you can scroll SEVERAL pages back with this.
>     Window Size:
>         Width: 80
>         Height: 48
>
> HTH
> Jan
>
>
>
> Antwan Williams wrote:
>
> > 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?
>

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 the immediate window?
> 
> 

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 command
line, e.g..:
  sc test.cpp > err.log

The same can be done for your own program:
  test.exe > exe.log

Nic Tiger.

"Antwan Williams" <antwan799@attbi.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: 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 the immediate window?
>
>

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 command
> line, e.g..:
>   sc test.cpp > err.log
>
> The same can be done for your own program:
>   test.exe > exe.log
>
> Nic Tiger.
>
> "Antwan Williams" <antwan799@attbi.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: 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 the immediate window?
> >
> >
>
>

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
command
> > line, e.g..:
> >   sc test.cpp > err.log
> >
> > The same can be done for your own program:
> >   test.exe > exe.log
> >
> > Nic Tiger.
> >
> > "Antwan Williams" <antwan799@attbi.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: 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
the
> > > immediate window?
> > >
> > >
> >
> >
>
>

Rajiv Bhagwat wrote:
> 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
> 

AFAIK, it does work with CMD (WinNT/2k/XP) command shell.  If not, one could use an alternative shell, like zsh from UnxUtils (http://unxutils.sourceforge.net).

HTH,
  Laurentiu

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
> command
> > > line, e.g..:
> > >   sc test.cpp > err.log
> > >
> > > The same can be done for your own program:
> > >   test.exe > exe.log
> > >
> > > Nic Tiger.
> > >
> > > "Antwan Williams" <antwan799@attbi.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: 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
> the
> > > > immediate window?
> > > >
> > > >
> > >
> > >
> >
> >
>
>

In article <b1nl8t$sre$1@digitaldaemon.com>, KarL (someone@somewhere.org) says...
> Yes, but not for stderr

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)