Windows 2000 (processor affinity): You want a specific application to run only on one CPU in a multiprocessor system. What is the correct way to assign the process to a single processor?

Introduction / Context:
Processor affinity lets administrators constrain a process to run on a subset of available CPUs. This can mitigate cache thrashing, isolate workloads, or troubleshoot CPU-specific issues. Windows 2000 exposes per-process affinity controls via Task Manager for interactive adjustments.

Given Data / Assumptions:

• Multiprocessor (or multicore) Windows 2000 system.
• Administrative rights to manage processes.
• Goal: bind one application to a single CPU.

Concept / Approach:
Task Manager allows modifying a running process’s CPU mask. The correct method is to locate the process on the Processes tab, right-click it, select Set Affinity…, and check only the desired CPU. This sets the affinity mask until the process restarts (or policy tools reapply it).

Step-by-Step Solution:
Open Task Manager → Processes tab.Right-click the target process and choose Set Affinity…Uncheck all but one CPU (e.g., CPU 0).Confirm and monitor CPU usage to verify adherence.

Verification / Alternative check:
Use Performance Monitor to chart % Processor Time per CPU and confirm the process stays on the selected CPU. Command-line tools or registry-based service affinity can be used for persistent settings.

Why Other Options Are Wrong:
Executable Properties: No GUI option there for CPU assignment in Windows 2000.

Task Manager Options/Performance views: Visual and global settings, not per-process affinity controls.

None of the above: Incorrect because Task Manager → Set Affinity is valid.

Common Pitfalls:
Expecting affinity to persist across restarts without reapplication; using affinity to mask broader performance problems.

Final Answer:
Right-click the application's process in Task Manager, choose Set Affinity, and select the target processor