DOS configuration files: In classic MS-DOS, the BUFFERS statement (used to set disk buffer count) belongs in which startup configuration file?

Introduction / Context:
Legacy DOS systems relied on two primary boot-time files for configuration: CONFIG.SYS and AUTOEXEC.BAT. Distinguishing which directives go where is a common certification and troubleshooting topic for retrocomputing and embedded DOS deployments.

Given Data / Assumptions:

• BUFFERS controls the number of disk buffers for DOS file I/O.
• We are dealing with standard MS-DOS, not third-party shells or NetWare configuration files.
• The question targets the correct file placement.

Concept / Approach:

CONFIG.SYS contains directives processed by the DOS kernel during initialization (e.g., DEVICE, FILES, BUFFERS, DOS=HIGH, LASTDRIVE). AUTOEXEC.BAT runs after DOS loads, executing commands like PATH, SET, and TSR loading. Since BUFFERS tunes a kernel file I/O parameter, it belongs in CONFIG.SYS.

Step-by-Step Solution:

Verification / Alternative check:

DOS manuals list BUFFERS=n under CONFIG.SYS examples alongside FILES=n and DEVICE=HIMEM.SYS lines. AUTOEXEC.BAT contains command-line executables, not kernel configuration keywords.

Why Other Options Are Wrong:

• AUTOEXEC.BAT: post-boot batch commands, not kernel directives.
• AUTOEXEC.NCF and NEB.CFG: not standard DOS configuration files.
• None of the above: incorrect because CONFIG.SYS is correct.

Common Pitfalls:

Placing BUFFERS in AUTOEXEC.BAT (ignored) or assuming modern OS concepts apply to DOS initialization. Always separate kernel config (CONFIG.SYS) from runtime commands (AUTOEXEC.BAT).

Final Answer:

CONFIG.SYS