I can only come to one of two conclusions from this statement. One - you are
purposely misstating things to make a point. or Two - You really have no
idea what you are talking about. Vista is a major rewrite of Windows with
many fundamental differences under the hood. If it wasn't why is it taking
so long for manufacturer's to develop drivers? Why are some security vendors
crying the blues?
I'm kind of funny in that I expect known errors in previous versions
of Windows should be expected to be FIXED in the latest version,
especially if you keep insisiting that Vista is suppose to be a "major
upgrade". It is very easy to dance all around this perennial issue.
The default positon of so many Microsoft apologists and admit it or
not, there are many here is to do exactly that.
Please tell me where this is done any better.
Again with the same excuses you mean.
Are you saying Microsoft should stop all development, ignore all the new hardware
and technology changes, and not release anything until it is 100% tested
foolproof against any possible bug, exploit, whatever, and oh yeah by the
way it should work exactly how I want it to and to heck with everyone else?
Did I say that? I pointed out that Windows is so utterly stupid it
can't find a codec/driver of its own copyright already on my system
and because of it be unable to play the audio portion of a common file
format that other software, some totally free, IS capable of playing.
I just LOVE to watch Microsoft apologists make excuses why it
shouldn't have to.
Worse, I pointed out more boneheaded blunders such as the following:
If Vista was uable to "see" my SATA drives in IDE mode and bring up
the appropriate "new hardware found" "installing" message when such a
drive is "plugged in" as a external device if I then reboot and change
setting in BIOS, (there are many possible combinations, depending on
how the primary IDE channel is set and 3 other lines elsewhere in BIOS
than only effect the SATA channels) in one configuration not only will
Vista refuse to "see" a SATA drive the BIOS reports both by displaying
the appropriate copyright notice for such drives, but also showing the
drive size and channnel they are on. Next Vista attempts but fails to
load the driver, and worse refuses to allow me to remove the line in
Device Manager where Vista next dumbly keeps adding more and more
instances of IDE channels I don't have. This particular MB has a
single IDE channel (one master/slave combination). Device Manger
thinks it has 3 pair. How cute. Frustrating, since Windows refuses to
allow to remove the extra two phantoms no matter what I do.
Yep, I would say that is a Windows problem is additon perhaps to a
driver issue. Since these SATA drives DID work correctly in both IDE
and SATA mode as well as in RAID configuration under XP.
Still worse this very same drive which is a Seagate SATA now doesn't
run at all in even IDE mode unless I set it to USB 2.0 instead of its
much faster and native SATA mode.
Again, if you can admit it or not these are obviously operating system
errors. If I plug in a device that did work under Vista and now no
longer does using its SATA interface configured as a miminal IDE
interface which is a BIOS option, again the blame goes to Microsoft if
one day it "sees it" then next day it can't in spite of the setting
being exactly the same now as when it did see this drive.
What is probably happening here is Vista is too dumb to pick the
correct driver and tries to either load the wrong version (SATA) or
now just ignores the IDE driver having already determined its a SATA
drive. I haven't bothered to look further or cleaned up after Vista,
but you see truly REALLY experienced users like myself understand
these problems for what they are...sloppy programming on Microsoft's
part.