MS-DOS memory diagnostics: Viewing TSR load order After attempting to unload a terminate-and-stay-resident (TSR) program, you are warned that other TSRs were loaded afterward. Which DOS command displays current memory allocation and load order of TSRs and drivers?

Introduction / Context:
Classic DOS systems load device drivers and TSRs into conventional or upper memory. Unloading requires reverse order (last in, first out). The right command reveals what is resident and in which order.

Given Data / Assumptions:

• Environment: MS-DOS or DOS mode in early Windows.
• Goal: list resident programs and drivers with segment addresses and order.
• Need: a built-in command that shows memory blocks and owners.

Concept / Approach:

MEM with the /C (Modules) switch lists memory allocation by program name, showing TSRs and drivers in the order they were loaded, along with sizes and memory regions. This is the canonical way to plan safe unloading or reconfiguration.

Step-by-Step Solution:

Verification / Alternative check:

Comparing MEM /C output before and after changing CONFIG.SYS/AUTOEXEC.BAT lines shows how load order changes. Third-party tools (e.g., QEMM) corroborate module mapping.

Why Other Options Are Wrong:

• MEM /P: only paginates MEM output; without /C it does not list modules.
• MEMMAKER: a separate optimizer for memory usage; not a direct listing of current load order.
• SYS: transfers system files to a disk; unrelated to TSR listing.
• None of the above: incorrect because MEM /C is valid.

Common Pitfalls:

Confusing /C with /D (which shows memory in different formats) and assuming TSRs can always be unloaded safely; many cannot.

Final Answer:

MEM /C