w700. Throttling is fate?

raging_user
raging_user Member Posts: 1 New User

Why it cant be solved? Current "settings" is not intel spec.

I want at my own risk disable throttling and get amazing tablet, like tablet from others RESPONSIVE manufacturers.

Please give me unlocked BIOS or new bios without throttling,do not let me think that I wasted my money.

Thanks !

 

Answers

  • Milleh
    Milleh Member Posts: 3 New User

    Given the response that you got from one of their engineers (http://community.acer.com/t5/Acer-Ideas/How-about-fix-w700-throttling-and-make-consumers-happy/idi-p/238926), I think that we can safely say that Acer is going to do exactly nothing about this. It doesn't seem like they care, really, and the numerous threads on this prove that (see the archived 2012 thread).

     

    It seems that they cheaped out on design - example, the MS Surface has 2 heat pipes for heat dissipation, whereas the W700 has 1.

     

    Unfortunately, consumers buying the W700 are not told this, and are never aware of it until they see the throttling themselves, or until they stumble onto threads like these and usually by then it is too late.

     

    Acer can say what they want (requirement to keep the tablet light weight, to increase battery life etc), but at the end of the day it boils down to misleading consumers by omitting a very important fact. Many of us buying windows 8 tablets do so for casual gaming, and the reality is that throttling on this unit makes it almost useless for gaming compared to its equally priced compeition (example, Surface 1). I wish I had saved my money and bought something else.

     

    I was burned by buying a W700 because of this (oh, and the wonderful burn in issue affecting virtually all i5 w700 units), and as a result I will never buy another product from Acer again.

     

    My only hope is that other potential buyers' Google searches bring them to these threads so that they may make an informed decision before buying this hobbled product.

     

    Sigh.

This discussion has been closed.