BREAK

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

Links:

break at Microsoft

$ 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.

Found a mistake? Have a question or improvement idea? Let me know.

Table Of Contents