@Luke’s first post: yea, it affects the high end cards as well. But I have seen this kind of error with ATI cards as well. It’s not as prevalent but it does happen.
]]>My dad doesn’t really use a computer. He actually got a broken laptop from a relative. I replaced the display, added more memory and it’s like brand new – it’s a 2.6 GHz with 1GB of memory and it runs WinXP almost effortlessly.
But, he doesn’t know how to use it. He wants me to teach him, but he never has time to sit down and learn how to even turn it on or browse the web. :P
Sigh… Maybe one day I’ll finally get him online…
This was actually the machine I was using while my desktop was on the fritz – cause frankly, it’s faster than my work laptop. :P
]]>hehe, I get to fix a lot of “instant hero” problems. My dad quite often has some small thing get a little screwed up, which I can quickly fix and re-affirm my status as a techno-God
This happens a lot if I’ve had to reformat and reinstall Windows as a solution to a bigger problem, and forgotten to set everything back the way it was – stuff like keyboard layout not being properly localised, or certain little things in Firefox.
I’ve done these things enough times to be able to do them off the top of my head, some of them are practically in muscle memory (if you push me I could probably recite from memory the registry location that changes where XP looks for the “Documents and Settings” special folders).
]]>Are the high end cards affected too? I guess this is a good reason to stay with ATI for now.
]]>I see this problem on a monthly basis. It’s been an ongoing issue with nvidia’s drivers for sometime now. Usually updating the drivers fix it, but they have a tendency to fudge themselves and you have to re-install again.
]]>