Feedback: We HATE the Acer spash screen / boot screen on our new monitors!

lgstephen
lgstephen Member Posts: 1 New User

Hi, I have seen that there are multiple other threads out there with this complaint. Many of them are "solved" so I can't reply.

 

I want to add my voice to the annoyed chorus of those who want an option to disable the Acer / Energy Star spash screen while the monitor "boots"

 

I see Acer's official response is "there is no way to stop the boot process" (lame, since no other monitor I have ever encounters wastes users' time like this one with a multiple second delay showing logos every time it turns on) or "just run a screen saver" (even LAMER ... I'm not interested in wasting energy just to avoid Acer's decision to show an energy star logo every time I turn the thing on).

 

So, please pass on the feedback to your product team that this splash/logo/boot screen on Acer b243pwl has turned me off Acer monitors from here on. I do purchasing for our department, and although the Acer's price is better than the similar Dell model, we are going with the Dell. No one can fathom why Acer thought it was OK to take so long for a monitor to turn on and show the screen.

Answers

  • chrisstitch
    chrisstitch Member Posts: 1 New User

    I cant agree more with lgstephen.

     

    I have recently bought 4 V226HQL's for our work but I WILL NEVER buy another acer monitor that waists my time everytime they wake up.

    Ive had to swop two of my 4 monitor displays for a pair of samsungs which display almost immediatly so I can start working not sitting until Acers vanity in telling me who they are has passed.

     

    Im sure ACER that the monitor is using about the same ammount of power displaying the Acer /Energy Star logos as if it was displaying my desktop instead. Wake up and fix the problem!

     

    Its a crying shame as the colour and brightness are stunning but do not make up for the usable screen boot time.

     

    Im off to write a 3 out of 10 review for these monitors now.

     

     

This discussion has been closed.