I'm sorry, but that's not even close to accurate.
Win2K is fully multithreaded and multitasking. Meaning it
will schedule the highest priority thread that is ready for
execution to whatever CPUs are available. In that respect
the design identical to most other protected-mode
operating systems of the last 25 years. Win2K Pro will only use
up to 2 CPUs, but this is more a marketing decision than anything
related to the internal design. The same platform in Win2K Server
is used to handle 4 or 8 CPUs just as easily.
There are dozens of threads in Win2K at any given moment,
and a second CPU will get used just on that basis alone.
And many applications are multithreaded at some level: for
example, Word will background print and use a second CPU
for that task, and if you have an inkjet that requires a lot of
in-box rasterizing, offloading that will definitely be noticeable.
But there is scheduling and locking overhead for multiprocessing,
and that's true for any O/S, including NT-based, *nix and OS/X,
or VMS or Multics for that matter. Most desktops do not gain
enough from the second CPU to justify the cost, as they are typically
only doing one thing at a time, and most CPUs are far faster
than what most people really need for day-to-day use anyway.
They mostly just idle faster.
You are certainly correct that an application that is designed
to be multiprocessing will benefit more from a second processor,
but that is of course true to the same degree on any platform
that supports it.
Steve Duff, MCSE
Ergodic Systems, Inc.