I trouble shoot PC's based on the Windows platform for a living, and know first hand the complications they can cause.
WindowsXP (for example) has MILLIONS of lines of code, and then when you add in the external installation of various drivers, the addition of other software (and removal), the removal of older hardware (and its drivers, and some dont get properly removed) and then add in the new hardware (and installation of drivers) and add in the fact that most of the software are programmed and written for windows by "other" organizations (and can contain BUGS and incompatabilities)---curing a PC problem can get complicated dependent on the nature of the problem. And, its obvious it is NOT solely and "completely" Microsoft Windows fault.
A lot of software/drivers get registered in the OS registry (and file structure) and/or startup functions (unknown to the user in the back ground), and hog RAM memory, slow performance.......even when the user thinks they removed the software. Is this Windows fault or the installation software? Its actually BOTH.
In other words the platform which is already dirty gets enhanced when there are other fingers in the pie associated with programming certain hardware and software for an OS.
Add in a inexperienced user, and it can get worse.
However, this OS can drive an experienced user to the nut farm even trying to work with it--correctly. (I raise hand high.........>

)
Windows IS FAR FROM PERFECT, LOL. One can do NOTHING wrong, for example, install a USB printer, then its drivers, and it works flawless one day, and the next day, its having convulsions (seemingly smoking crack) trying to locate the same printer, when it worked perfectly printing a 10 page document the day before and the user wasnt even on the pc for a day----> WTF??!
Therefore, Windows "can be" completely at fault at times--unless its the driver (programming from the organization separate from Microsoft) being the chief cause.....of windows not recognizing the printer (as in the example above

).
Ever have Windows recognize your printer, but the "software" you are using not recognize it? The OS and the Software MUST programically communicate.....and if the software (written for windows by another organization) has flaws this ISNT the OS's fault--its the programming of the software being used. (the fingers in the pie).
Some of it is the user, but let me tell you......some of it ISNT. Some of it is purely the faults of the OS, no question about it.
GotFit, I didnt read the entire thread (soooorrrry!

), what is your problem? Maybe I can help you with it. Win 2000 Pro, has many driver, hardware, and software incompatabilities--even by the ones that claim its compatable, and its no longer supported by most producers of hardware/software, though most "traditionally" used software can function on it.
Best wishes,
Chillen