74 lines
1.6 KiB
HTML
74 lines
1.6 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>screendump(8)</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
<H1>screendump(8)</H1>
|
|
<HR>
|
|
<PRE>
|
|
|
|
</PRE>
|
|
<H2>NAME</H2><PRE>
|
|
screendump - write current console screen to standard output
|
|
|
|
|
|
</PRE>
|
|
<H2>SYNOPSIS</H2><PRE>
|
|
<STRONG>screendump</STRONG>
|
|
|
|
|
|
</PRE>
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
<STRONG>Screendump</STRONG> prints the contents of the console screen to standard output.
|
|
It does this by reading the screen memory, skipping over attribute bytes,
|
|
omitting trailing blanks and inserting a newline character at the end of
|
|
each line.
|
|
|
|
|
|
</PRE>
|
|
<H2>NOTES</H2><PRE>
|
|
The most common use of <STRONG>screendump</STRONG> is with output redirected to a file.
|
|
This allows screen displays (including output of F-keys) to be captured
|
|
for inclusion in other documents.
|
|
|
|
This version is for IBM-PC architecture only.
|
|
|
|
|
|
</PRE>
|
|
<H2>BUGS</H2><PRE>
|
|
A network user captures an image of the main console, not his or her own
|
|
screen. The output will usually not be what you expect if the display is
|
|
in hardware scrolling mode, since in that mode the order of the lines in
|
|
screen memory may not be the same as what appears on the screen. If you
|
|
expect to use <STRONG>screendump</STRONG> to send notes to someone about problems that
|
|
occur while using <STRONG>MINIX</STRONG> you must remember to toggle to software scrolling
|
|
before you make the dump. It will also be necessary to use <STRONG>su</STRONG>, because
|
|
<STRONG>/dev/mem</STRONG> is normally not world readable.
|
|
|
|
|
|
</PRE>
|
|
<H2>AUTHOR</H2><PRE>
|
|
Kees J. Bot (kjb@cs.vu.nl)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
</BODY>
|
|
</HTML>
|