Microsoft KB Archive/137379

{|
 * width="100%"|

BUG: Windows 95 Access Violation Error After Disabling CTRL+C

 * }

Q137379

-

The information in this article applies to:


 * Microsoft Win32 Application Programming Interface (API), included with:
 * Microsoft Windows 95

-

SYMPTOMS
In a Win32 environment, a console application can be terminated by pressing CTRL+C. To disable CTRL+C input, a console application can call the SetConsoleCtrlHandler(NULL, TRUE) API function.

When this API function is called in Windows NT, CTRL+C is ignored if pressed. However, when it is called in Windows 95, pressing CTRL+C generates an Access Violation error. Similarly, when this API is called in Windows 95, pressing CTRL+BREAK generates an Access Violation error.

RESOLUTION
There are two alternatives when you want to disable CTRL+C and avoid generating an Access Violation error:


 * 1) Install a console control handler to capture and ignore the CTRL+C keypress:
 * 2) Disable CTRL+C by disabling the ENABLE_PROCESSED_INPUT console mode. Disabling the ENABLE_PROCESSED_INPUT console mode then reports CTRL+C to the input buffer, not the system:

STATUS
Microsoft has confirmed this to be a bug in the products listed at the beginning of this article.

Additional query words:

Keywords : kbprogramming kbConsole kbKernBase kbGrpDSKernBase

Issue type : kbbug

Technology : kbAudDeveloper kbWin32sSearch kbWin32API