In DOS startup configuration, which file contains commands that configure system devices and drivers during boot?

Introduction / Context:
Classic DOS systems relied on two key startup files: CONFIG.SYS and AUTOEXEC.BAT. Understanding their roles is critical for loading device drivers, setting buffers, and preparing the environment for applications. This distinguishes kernel-level configuration from user-level initialization scripts.

Given Data / Assumptions:

• Platform: MS-DOS 5/6 era.
• Goal: identify the file that configures devices/drivers at boot.
• Typical entries include DEVICE, DEVICEHIGH, FILES, BUFFERS, LASTDRIVE.

Concept / Approach:

CONFIG.SYS is processed by DOS during boot to load low-level device drivers (e.g., HIMEM.SYS, EMM386.EXE, OAKCDROM.SYS) and set kernel parameters. AUTOEXEC.BAT runs afterward to set environment variables and start TSRs. COMMAND.COM is the command interpreter itself, not the configuration file. WIN.INI applies to Windows 3.x/9x, not pure DOS hardware configuration.

Step-by-Step Solution:

Verification / Alternative check:

Typical line: DEVICEHIGH=C:\DOS\OAKCDROM.SYS /D:MSCD001 confirms CONFIG.SYS's role in device setup prior to the command interpreter launching.

Why Other Options Are Wrong:

• Command.com: the shell, not a config script.
• Autoexec.bat: user-level initialization after CONFIG.SYS.
• Win.ini: Windows-specific, not DOS hardware drivers.
• None of the above: incorrect because CONFIG.SYS is correct.

Common Pitfalls:

• Placing DEVICE lines in AUTOEXEC.BAT—drivers won't load properly.
• Forgetting DEVICEHIGH to conserve conventional memory.

Final Answer:

Config.sys.