You plan to install a new internal CD-ROM drive in a Windows NT system and want to verify there will be no IRQ conflicts beforehand. Which built-in tool should you use to inspect current hardware resources (IRQs, I/O ports, DMA)?

Introduction / Context:
On Windows NT, hardware resource conflicts such as IRQ overlaps can cause device malfunctions. The system includes a diagnostics utility that inventories hardware and shows assigned resources so administrators can plan safe installations without guesswork.

Given Data / Assumptions:

• Target OS: Windows NT Workstation/Server.
• Goal: view current IRQ, I/O, DMA assignments before adding hardware.
• Need: a tool that reports hardware resources, not software configuration.

Concept / Approach:
Windows NT Diagnostics (WINMSD) enumerates devices and lists resource usage including IRQs, I/O ranges, DMA channels, and memory. This is the correct tool to assess potential conflicts. Other listed utilities either manage servers and domains (Server Manager), control service startup types (Devices), install software (Add/Remove Programs), or manage disks/partitions (Disk Administrator)—none of which display IRQ assignments comprehensively.

Step-by-Step Solution:

Verification / Alternative check:
WINMSD was the canonical NT-era tool used by administrators to troubleshoot blue screens or device failures caused by resource conflicts, confirming its role for pre-installation checks.

Why Other Options Are Wrong:

• Server Manager: focuses on server/domain management.
• Devices: sets service startup; does not inventory IRQs in detail.
• Add/Remove Programs: installs/removes software only.
• Disk Administrator: partition and volume management.

Common Pitfalls:
Assuming Plug and Play will resolve everything automatically on NT (limited PnP support); forgetting to check motherboard documentation for reserved IRQs.

Final Answer:
Windows NT Diagnostics (WINMSD)