Path: utzoo!attcan!uunet!aplcen!samsung!emory!stiatl!huang
From: huang@stiatl.UUCP (Jim Huang)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Avoiding ^C
Message-ID: <10294@stiatl.UUCP>
Date: 9 Jul 90 14:59:04 GMT
References: <10688@spool.cs.wisc.edu> <577@dg.dg.com> <1990Jun30.203726.7480@sjsumcs.sjsu.edu> <1990Jul5.171205.2036@tc.fluke.COM> <1990Jul6.220720.15747@Octopus.COM>
Organization: Sales Technologies Inc.  Atlanta, Ga.
Lines: 29

In article <1990Jul6.220720.15747@Octopus.COM> stever@octopus.UUCP (Steve Resnick ) writes:
>
>If you HAVE to use stdio, there might be some diddling of the I/O streams

>to set "raw" mode. I have never tried this so I cannot recomend this.
>
>

  I have try this in my program. It work fine, but you had to remember to
  reset it to "cooked" mode before your program terminated.

  Following are from "Advanced MS-DOS" by Ray Duncan, Micrsoft Press

  To avoid losing control upon entry of a Ctrl-C.

  1, Performing all keyboard input and status check throug function 06h
     and 07h, and turning on the raw mode for the console driver.

  2, Performing all display output through MS-DOS function 06h or by
     direct write to the ROM BIOS or to the video controller's refresh 
     buffer.

  3, Setting the other character devices(AUX, PRN) into raw mode.

  4, Disabling Ctrl-C checking with function 33h, for MS-DOS operations
     other than character I/O.

   
						   Jim Huang