🚀 go-pugleaf

In article <17192mINN2ut@matt.ksu.ksu.edu> holland@matt.ksu.ksu.edu (Rich Holland) writes:
}Easy, right?  WRONG.  I went into windows and did FILE-RUN and         
}specified COMMAND.COM -- got a shell to DOS from within Win30.
}I dumped the vector table via debug (debug, d0:0, q) and found
}that the Int 05h vector was *STILL* pointing to F000h:FF54h!
}And Win30 was *still* capturing the screen dumps!

Windows takes over the INT 09h keyboard interrupt, so it is presumably
checking for PrtSc itself and calling its own routines instead of INT 05h
as the ROM BIOS does.
-- 
Internet: RALF+@CS.CMU.EDU   |The University would disclaim this if it knew...
FIDO: Ralf Brown 1:129/26.1  |
BIT: RALF%CS.CMU.EDU@CARNEGIE|"Success has a simple formula: do your best,
AT&Tnet: (412)268-3053 school| and people may like it."   -- Sam Ewing

ralf+@cs.cmu.edu (Ralf Brown) writes:

>Windows takes over the INT 09h keyboard interrupt, so it is presumably
>checking for PrtSc itself and calling its own routines instead of INT 05h
>as the ROM BIOS does.

Yeah, I thought of that about 10 minutes after I posted.  :-)

Guess I'll re-direct Int 09h instead of Int 05h, huh?  

-- 
Rich Holland              | INTERNET: holland@matt.ksu.ksu.edu
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!!"

In article <17387rINNnm9@matt.ksu.ksu.edu>, holland@matt.ksu.ksu.edu (Rich Holland) writes:
|> ralf+@cs.cmu.edu (Ralf Brown) writes:
|> 
|> >Windows takes over the INT 09h keyboard interrupt, so it is presumably
|> >checking for PrtSc itself and calling its own routines instead of INT 05h
|> >as the ROM BIOS does.
|> 
|> Yeah, I thought of that about 10 minutes after I posted.  :-)
|> 
|> Guess I'll re-direct Int 09h instead of Int 05h, huh?  
|> 

Does Windows write its OWN int 9 or does it call the DOS one because if I have a TSR in dos that hooks int 9, I can't seem to get it to work in windows.


|> -- 
|> Rich Holland              | INTERNET: holland@matt.ksu.ksu.edu
|> 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!!"

-- 
Greg Humphreys    |  "Playing not to win is like sleeping with your 
gregh@alw.nih.gov |  sister - sure, she's a great piece of tail, 
                  |  and she's got a bag full of goodies, but it's 
(301) 402-1817    |  just plain illegal."  -Charlie Sheen, "Hotshots"

In article <17387rINNnm9@matt.ksu.ksu.edu> holland@matt.ksu.ksu.edu (Rich Holland) writes:
>ralf+@cs.cmu.edu (Ralf Brown) writes:
>
>>Windows takes over the INT 09h keyboard interrupt, so it is presumably
>>checking for PrtSc itself and calling its own routines instead of INT 05h
>>as the ROM BIOS does.
>
>Yeah, I thought of that about 10 minutes after I posted.  :-)
>
>Guess I'll re-direct Int 09h instead of Int 05h, huh?  
>
>-- 
>Rich Holland              | INTERNET: holland@matt.ksu.ksu.edu
>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!!"

But, you can't redirect int 09h !  It is something every user working in
almost any other language than English learn very soon : keyboard interface
that change the keyboard to support French or other "foreign" characters
just won't work with Windows :-( and you have to use the foreign language
drivers included with Windows.  I don't know what actually Windows does,
but it is like it was detecting original BIOS entry points and removing them
while in Windows, but it gives them back while in a DOS windows (i.e.
inside WIndows, WIndows keyboard driver is active; outside Windows and inside
DOS window, DOS keyboard driver is active).

-- 
  \_\    Denis Beauregard  *  internet:beaurega@ireq.hydro.qc.ca
 /   \   Genealogiste officiel : Beauregard/Jarret/Jarest/Vincent
J   __>  Vient de paraitre : Andre Jarret et ses Ancetres
\_.-===  En vente par l'auteur                      Opinions ? Et pis non !

holland@matt.ksu.ksu.edu (Rich Holland) writes:

> When I started out, my task seemed simple enough!  i've got a 286 with 
> MS-Win 3.0 installed and I've got to dial up a mainframe and ocasionally
> get a printout of something.  It's such a hassle to hit PRTSCR, swap
> back to windows, go into notepad, hit EDIT-PASTE-FILE-PRINT, and then
> swap back to my program.  I figured it'd be pretty easy to intercept the
> PRTSCR keypress by writing a "shell" around my comm program.

Hi there!

What I'm saying is what I have at work, I run with Win 3.1 but if memory
serves me correctly, this is still applicable in 3.0 too

Create a PIF file for your program and enable in the RESERVE KEYS
section all those related to PRINT SCREEN (even those for shift, alt,
and ctrl). It works for me, I too have to use the mainframe of the
company and print out a few stuff...

See You around the 'Net!!

 ----------------------------------------------------------------------
 |                      rider@geloser.CAM.ORG                         |
 |          Matrix Rider                     Serge Ayotte             |
 |      Gentleman Loser System (private), Montreal/Quebec/Canada      |
 ----------------------------------------------------------------------