🚀 go-pugleaf

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.

Here's what I thought I'd do (in TP5.5):

  .  Copy the Int 05h vector (should point to window's routine)
  .  Put ROM vector back in table (F000h:FF54h)
  .  Exec() the "comm" program (or any program, really)
  .  Restore the Int 05h vector for windows and exit

This should have the effect of sending the screen contents to the 
printer rather than to window's clipboard.  Additionally, I could
have it take a '-c' switch (for 'c'lipboard) to also call the
old windows interrupt and send it to the clipboard after it prints
it....

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!

How the heck's it doing that?  Am I going about this all wrong?
Any suggestions/ideas?  I s'pose I could use "Snipper" from PC-Mag,
but that's just one more hassle, i think...

 -- Rich

-- 
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!!"