suggest change

In Windows versions based on Windows NT, does nothing; kept for compatibility with MS DOS.


$ break /?
Sets or Clears Extended CTRL+C checking on DOS system

This is present for Compatibility with DOS systems. It has no effect
under Windows.

If Command Extensions are enabled, and running on the Windows
platform, then the BREAK command will enter a hard coded breakpoint
if being debugged by a debugger.

Feedback about page:

Optional: your email if you want me to get back to you:

Table Of Contents