delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/01/17/18:22:46

Date: Mon, 17 Jan 94 17:47:24 -0500
From: DJ Delorie <dj AT ctron DOT com>
To: pgf AT cayman DOT com
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: catching ctrl-break vs. ctrl-c

> hi -- last week i asked how to prevent getting the "Ctrl-C Hit!" message
> when my program is running and doesn't have a pending read() on stdin.
> someone sent me info on the go32_want_ctrl_break()/go32_was_ctrl_break_hit()
> calls, and they work just great at preventing me from ever seeing a ctrl-break.
> however, i _still_ get ctrl-c being reported.  i sort of thought these two
> interrupts were supposed to be equivalent?

No.  They are different interrupts.  You can shut off Ctrl-C checking
in protected mode by performing the DOS interrupt that shuts off
CTRL-C checking.  I think setting stdin to raw or binary mode will do
this automatically, but I don't remember off the top of my head.

Note that the default action for both interrupts is similar, hence the
misconception that they are the same interrupt.


- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019