MS-DOS 6.22 BREAK Command Function and Usage

This article explains the purpose, operation, and configuration of the BREAK command in MS-DOS 6.22. It covers how this command controls extended interruption monitoring, how to configure it within the system startup files or command prompt, and the operational trade-offs between responsiveness and system performance.

Purpose of the BREAK Command

In MS-DOS 6.22, the BREAK command controls how frequently the operating system checks for the Ctrl+C or Ctrl+Break key combination to halt running programs or processes.

By default, MS-DOS checks for Ctrl+C only while performing operations involving standard input and output devices, such as reading from the keyboard or writing to the display, printer, or serial ports. If a running program enters a tight computational loop or performs extensive disk read and write operations without accessing the standard I/O devices, pressing Ctrl+C will not stop the execution.

Turning BREAK on extends this checking routine to all standard DOS system calls (Interrupt 21h), including disk read and write operations. This enables users to terminate unresponsive programs or lengthy disk-bound tasks much more reliably.

Configuring BREAK in CONFIG.SYS

To enable extended checking globally at startup, the BREAK directive is placed in the CONFIG.SYS file.

The syntax in CONFIG.SYS is:

BREAK=ON

If set to BREAK=OFF or omitted entirely, MS-DOS defaults to the standard, restricted checking mode.

Managing BREAK from the Command Line

The BREAK command can also be viewed or toggled dynamically in the MS-DOS command interpreter (COMMAND.COM) or via batch files without rebooting the system.

  • View current status: Type BREAK and press Enter. The system returns either BREAK is on or BREAK is off.
  • Enable extended checking: Type BREAK ON.
  • Disable extended checking: Type BREAK OFF.

Performance Considerations

When BREAK is set to ON, the operating system must execute additional verification instructions during virtually every system service call. On earlier x86 hardware (such as 8086 or 80286 systems), this introduced a measurable drop in file I/O performance.

By the release of MS-DOS 6.22 on 486 and Pentium-class hardware, the processing overhead of extended break checking became negligible for most applications. Consequently, setting BREAK=ON became standard practice in CONFIG.SYS to ensure greater administrative control over running software.