home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.msdos.programmer:2225 comp.os.msdos.programmer:8684 comp.lang.pascal:4943
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!wupost!cs.utexas.edu!uwm.edu!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!ralf
- From: ralf+@cs.cmu.edu (Ralf Brown)
- Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer,comp.windows.ms.programmer,comp.lang.pascal
- Subject: Re: Windows and printscreen
- Message-ID: <BtBFLF.4pr.2@cs.cmu.edu>
- Date: 21 Aug 92 04:10:27 GMT
- Article-I.D.: cs.BtBFLF.4pr.2
- References: <17192mINN2ut@matt.ksu.ksu.edu>
- Sender: news@cs.cmu.edu (Usenet News System)
- Organization: School of Computer Science, Carnegie Mellon
- Lines: 15
- Nntp-Posting-Host: b.gp.cs.cmu.edu
-
- 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
-