Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!turnkey!ladcgw.ladc.bull.com!melb.bull.oz.au!lro From: lro@melb.bull.oz.au (Liam Routt) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: Control-C blocker needed Message-ID: Date: 17 Jun 91 06:42:30 GMT References: ,<1991Jun11.151950.2097@gupta.portal.com> <0094A28F.A230B060@EA.USL.EDU> Sender: news@melb.bull.oz.au (USENET News Account) Organization: Bull HN Information Systems Australia. Lines: 30 Nntp-Posting-Host: sirius callawaycj@EA.USL.EDU (C.JamesCallaway) writes: >In article <1991Jun11.151950.2097@gupta.portal.com>, max@gupta.portal.com (Max Rochlin) writes: >>In article morgan@chaos.cs.brandeis.edu (Dylan Kaufman) writes: >>>let >>>me completely block out Ctrl-C and Ctrl-Break during execution of the >>>AUTOEXEC.BAT > >An ISR Device Driver That Intercepts INT09h(BIOS Keyboard Handler) Or >INT1Bh(BIOS CtrlBRK) Or INT23h(BIOS CtrlC Handler), Might Do The Trick. > >Let Me Know If You Find Something. Maybe I Could Use It, Too. ># C.JamesCallaway! # CALLAWAYCJ@EA.USL.EDU | FUTURE iMAGE SoftWorks! # MS-DOS 5.0 allows you to define your own Control-C handler. It will be used to handle all Control-Cs detected (while other methods in earlier versions might not have worked 100% of the time). The interrupt it 23h. The vector is now saved in the PSP of a program, so the vector table entry can be changed, but the parent program will have its handler restored on exit. Incidently the same is true for the Critical Error Handler (int 24h) under MS-DOS 5.0. (the CEH is the one that gives the Abort Retry Fail messages all the time!). This is all only true under MS-DOS 5.0, though, so it will not work with the 3.3 versions I think the original poster was concerned about supporting (unless they upgrade :-) ). Liam Routt "Murder by Pirates is Good!" Senior Software Engineer - The Princess Bride Bull Information Systems Melbourne Australia