🚀 go-pugleaf

On Thu, 12 Aug 2010 13:30:06 -0500, Doug Jacobs <djacobs@rawbw.com>
wrote:

>Loren Pechtel <lorenpechtel@hotmail.invalid.com> wrote:
>
>> I also have 20 years of programming for a living and I fully agree
>> with you.  Had Blizzard noticed it during development they should have
>> taken precautions but there is no expectation for them to notice
>> something like this.  It's a hardware problem.
>
>I mostly agree, but then I have some questions:
>1: Why hasn't this happened with other software?  It's not as though 
>this game was designed to push the limits of PC hardware, unlike other 
>games in the past.  So obviously Blizzard has done something differently.

Yeah.  They had a bug that at the menu screen pegged the GPU at
100%--it did push the limits.

>2: When it was discovered that Starforce was damaging CD drives, people 
>weren't blaming the makers of the hardware - they were blaming Starforce 
>(and the companies who protected their products with Starforce.)  How is 
>this situation different?

Because Starforce pushed the drives in a fashion that would not
normally occur.

>Sure, the hardware should have failsafes in place to try and protect 
>itself against overheating, and the drivers should have failsafes to deal 
>with potentially dangerous and damaging input.  At any rate, put yourself 
>in the shoes of the victims here.  All they did was start up Starcraft2 
>and then their video card died.  Regardless of the actual cause, all they 
>know is that starting Starcraft2 killed their video card.  Expecting 
>customers to act as QA/testing/engineering is just ridiculous.

They have a legitimate beef with the manufacturer of their card.