Slashdot Mirror
Windows Vista SP1 Meeting Sour Reception In Places
Stony Stevenson writes "A day after it was released for public download, Windows Vista SP1 is drawing barbs from some computer users who say the software wrecked their systems. 'I downloaded it via Windows Update, and got a bluescreen on the third part of the update,' wrote 'Iggy33' in a comment posted Wednesday on Microsoft's Vista team blog. Iggy33 was just one of dozens of posters complaining about Vista Service Pack 1's effect on their PCs. Other troubles reported by Vista SP1 users ranged from a simple inability to download the software from Microsoft's Windows Update site to sudden spikes in memory usage. To top it all off, the service pack will not install on computers that use peripheral device drivers that Microsoft has deemed incompatible."
Khaaaaaaaan-
uh, I mean,
Gaaaaaaaaaaaaaaates!!!
Hopefully those of you who do support friends and family weren't cruel enough to put Vista on their machines.
All points of time and space are connected.
should be able to uninstall the drivers themselves
With emphasis on should, given Microsoft's history on error messages (my document failed to print!) the message probably says something along the lines of "You have incompatible hardware and we cannot install this service pack, have a nice next three days disabling drivers one at a time trying to figure out which one it is"
... and all the muggles will think that means that just like cheese, this game goes well with wine.
"Ooohh, How thoughtful, this game goes with Merlot. Honey! We need to stop at the liquer store"
Copyright 2010. All rights reserved. This comment may not be copied in any way including, but not limited to caching.
This just in: somewhere, someone on the Internet complains about something. More at 11.
I agree.
That's why when I want an even-handed tech assessment, I always go here first:
http://www.microsoftisawesome.com/
You were mistaken. Which is odd, since memory shouldn't be a problem for you
Ford also expects money for their products. If you never change the oil and the engine blows up, that's ford's problem? That's pretty sad if that is the best reasoning you can come up with.
Posh. You make it sound so hard! You just go to the System log, look for errorcode 0x80000000fc, find the filename in question (EBVIA235C.dll), search the registry for the 3rd occurance of that file name, write down the GUID {23301203-12-3-1-2451-2-231-123122312-23), search for _that_, open the file in a editor, search for strings to find the vendor name and search for it on Google.
Easy peasy!
"Draco dormiens nunquam titillandus."