🚀 go-pugleaf

In article <1992Sep12.221805.18053@news.clarkson.edu>, AAron@sun.soe.clarkson.edu (AAron nAAs) writes:
|> 
|> From article <BuG1F8.G6o@mentor.cc.purdue.edu>, by piskacrj@mentor.cc.purdue.edu (Bob Piskac):
|> > How do you trap a Control Break or Control C in MS C V7.0.  I can
|> > stop it from interupting the program, but I get a ^C on the screen.
|> > 
|> > Thanks,
|> > 
|> > piskacrj@mentor.cc.purdue.edu
|> We wrote a program with a TUI, and had a Ctrl-C handler that did nothing.
|> We encountered your problem of the ^C on the screen, and our quick and
|> dirty solution was to redirect stdout in initialization.  Since we did
|> special screen writes it wasn't a problem.
|> 
|> AAron nAAs
|> Eclat Technologies, Inc.
|> 

Hi.  You might want to try using console I/O rather than stdio I/O, because the
console routines get characters from the ROM-BIOS rather than from DOS, and the
BIOS doesn't write ^C's to the screen like DOS does.  However, you still might
want to trap INT 1Bh (the BIOS Ctrl-Break trap) so DOS won't see it when you
try to write a file or something.

Tschuess,
David Paschal