Skybuck Flying wrote:
> http://www.treehugger.com/files/2006...windows_xp.php
>
> 25 billion dollars wasted on power/electricty because of three little bugs.
Whatever increased electrical consumption Windows XP's imperfect power
management might have 'caused' is dwarfed by the energy consumption of
CRT monitors, most of which have proven not to consume significantly
less power even when in standby mode.
There are so many flaws, unsupported assertions, and assumption-based
logic in the anti-Microsoft article I hardly know where to begin. But,
to start with...
The vast majority of PCs worldwide are not DIY or custom built, but OEM
mass produced (e.g. HP, Compaq, Dell, Gateway, Packard Bell, IBM, et.
al.). These companies actually have a fairly good (though not great)
track record of delivering PCs with working power management, due to
their closer (direct) relationships with hardware and peripheral
vendors who supply their components, and the engineering level staff
they have doing product development, testing, and support.
Its mostly the DIY and custom built machines that have power management
issues, because these machines will be used with the broadest spectrum
of hardware and peripherals from the broadest spectrum of vendors; only
a tiny fraction of which will be fully tested by the motherboard
manufacturer before mass production. It is the system integrator,
designer, or builder that is responsible for validating/testing
specific hardware combinations before production and roll-out, and this
is where DIY and custom builders are largely just playing darts in a
trial-and-error manner, often having to settle for some glitches due to
cost or time constraints.
By in large, power management issues are not caused by any flaw in
Microsoft's power management implementation or some 'bug' in
Microsoft's code, but by poorly designed device drivers on the part of
hardware and peripheral manufacturers (the same underlying cause of
most so-called 'IRQ conflicts').
You can imagine, then, the backlash and criticism Microsoft would face
if its operating system were designed by default to just slam a system
into standby or hibernation no matter what other devices were doing or
why. e.g.
_Someone trying to download SuSE Linux distro on DVD and their computer
keeps going into standby or hibernation @ 30 minutes whether or not
their download is finished.
_A PC being used as security DVR is forced into standby or hibernation
@ 60 minutes.
There are dozens of other scenarios where the consequences or costs of
forcing a PC into a PM state without regard for what the PC is doing at
the time or user preference would far outweigh the energy savings. The
same reason why a ****-poor device driver can prevent a PC from
entering standby or hibernation also prevents the PC from entering a PM
state when it is not safe to do so from a task objective or data
integrity standpoint.
But how nice and simple the world must be to view every problem with
narrow single-issue mindedness, which in this case seems to be driven
more by some juvenile disdain for Microsoft than sincere 'concern' for
the environment (typical of environmentalists). By this guy's logic, a
worse polluter would have to be the frame-rate zealots who build raging
dual-core SLI systems sporting dual monitors and 600+ watt PSUs for
browsing the web and running benchmarks, when they could be out doing
something constructive with their time and money instead of playing
games, like 'saving the environment'.
Regards,
Tim