In DOS-based diagnostics, which command is commonly used to display memory usage details, including TSRs (Terminate-and-Stay-Resident programs)?

Introduction / Context:
Legacy DOS systems often loaded small programs that remained resident in memory (TSRs). Diagnosing conflicts and free memory required tools to list resident modules and memory maps. The standard command-line utility for this purpose is well known.

Given Data / Assumptions:

• Environment: MS-DOS or DOS-mode in early Windows.
• Goal: View memory layout and identify TSRs.

Concept / Approach:
The MEM command displays memory usage, and with switches like /C or /D it lists details of conventional, upper, and loaded programs, including TSRs. Other options listed are either incorrect names or unrelated tools (Memmaker optimizes memory but does not serve as the primary display utility).

Step-by-Step Solution:
Use MEM to display memory; MEM /C or MEM /D shows module breakdowns.Scan the listing to identify TSRs and their memory footprints.Use this information to remove or reconfigure TSRs as needed.

Verification / Alternative check:
DOS help and manuals document MEM as the standard memory reporting tool; TSR managers also rely on MEM outputs for diagnostics.

Why Other Options Are Wrong:

• Memory: Not a valid DOS command.
• SYS /M: SYS transfers system files; not a memory viewer.
• Memmaker: Attempts to optimize memory but is not the readout utility.
• None of the above: Incorrect because MEM is correct.

Common Pitfalls:
Forgetting to use switches like /C or /D for detailed module listings, leading to incomplete information about TSRs.

Final Answer:
MEM