Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!watdcsu!broehl
From: broehl@watdcsu.UUCP
Newsgroups: comp.sys.ibm.pc,comp.graphics,comp.sources.wanted
Subject: Re: Hercules and EGA graphics screen dumping.
Message-ID: <3623@watdcsu.UUCP>
Date: Mon, 13-Jul-87 17:09:09 EDT
Article-I.D.: watdcsu.3623
Posted: Mon Jul 13 17:09:09 1987
Date-Received: Tue, 14-Jul-87 04:56:58 EDT
References: <384@mdbs.UUCP>
Reply-To: broehl@watdcsu.waterloo.edu (Bernie Roehl)
Organization: U. of Waterloo, Ontario
Lines: 12
Xref: utgpu comp.sys.ibm.pc:4929 comp.graphics:866 comp.sources.wanted:1388

In article <384@mdbs.UUCP> jmg@mdbs.UUCP (John Murray Gamble) writes:
>This doesn't quite solve my problem: i wanted my *program* to
>screen dump, not to invoke someone else's program.

Most screen dump programs that I know of stay resident and trap int 5's,
which get issued by the keyboard handler when shift-prtsc is pressed.
Therefore to invoke the screen-dump function from your code, you simply
do an int 5 (this should be feasible in any reasonable high-level language,
as well as assembler).

Of course, some printscreen programs will then interactively prompt you
for information, which may not be what you want them to do.