NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/alt/msdos/programm/2258

Internet Message Format | 1992-08-27 | 3.4 KB

Xref: sparky alt.msdos.programmer:2258 comp.os.msdos.programmer:8802 comp.lang.pascal:5057
Path: sparky!uunet!bonnie.concordia.ca!hobbit.ireq.hydro.qc.ca!beaurega
From: [e-mail] (Denis Beauregard)
Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer,comp.windows.ms.programmer,comp.lang.pascal
Subject: Re: Windows and printscreen
Message-ID: <[e-mail]>
Date: 26 Aug 92 03:25:05 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Sender: [e-mail] (Netnews Admin)
Organization: Institut de recherche d'Hydro-Quebec, Varennes, Canada
Lines: 52

In article <[e-mail]> [e-mail] (Rich Holland) writes:
>
>Okay, I understand that I can't run a TSR that redirects Int 09h, then run
>Windows, and when I "shell" to DOS from windows, expect my TSR to still
>be active.  That's *NOT* what I was attempting to do.  Instead of running

But, you should!  If you consider DOS (i.e. prompt available) and Windows
(i.e. MS Windows controlling mouse, keyboard and screen) as 2 modes,
whenever you are in DOS mode (from prompt after booting or from a
DOS shell like command.com running inside a Windows window or in
full screen mode), the TSR is available and you could hang up int 09.

>something like this: 'tn3270 matt' from within windows, I'd change the
>PIFF file to read: 'prthru tn3270 matt' -- my prthru program would Exec()
>whatever command I pass it, after re-directing the Interrupt so I can
>catch the prtscr (i had originally thought I needed to grab 05h, but I
>found out later I need the keyboard, 09h).  When the telnet session ends
>(in this case), control returns to my prthru program, which restores the
>vectors and exits to windows -- as far as Windows knows, there hasn't been
>any re-direction...
>
>Now, someone tell me why THIS won't work?
>
In your example, prthru is a Windows program calling tn3270, a Windows
program too, so int 05 and 09 are catched.  If, however, prthru and
tn3270 are both DOS programs (i.e. Windows will install DOS prompt before
running prthru), then you should be able to intercept printscreen, but only
if the DOS window is active.  It is like a program writting directly to
the screen (like a text editor I wrote years ago).  In the DOS window,
the editor writes to the video memory directly so that in DOS full
screen, the video memory is not intercepted.  However, in DOS window
with Windows active, when the editor writes to the screen, Windows intercept
the character, and re-write it on the copy of memory video in the DOS window.

In other words, Windows catch many interrupts (if not all) and when
WIndows has the control, you can't do anything.  Maybe you could do something
if you intercept WIndows commands, but this is not using the interrupts
and should be discussed in the ms-windows newsgroups anyway.

>
>--
>Rich Holland              | INTERNET: [e-mail]
>100 Jardine Terr, Apt A7  | BITNET  : holland@ksuvm
>Manhattan, KS  66502-3357 | UUCP    : ...!rutgers!matt.ksu.ksu.edu!holland
>"Jesus saves...but Gretzky gets the rebound!  He shoots!  He scores!!"


--
  \_\    Denis Beauregard  *  internet:[e-mail]
 /   \   Genealogiste officiel : Beauregard/Jarret/Jarest/Vincent
J   __>  Vient de paraitre : Andre Jarret et ses Ancetres
\_.-===  En vente par l'auteur                      Opinions ? Et pis non !