The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Asus Power4Gear Totally N56VM

    Discussion in 'Asus' started by hiohaa, Nov 12, 2012.

  1. hiohaa

    hiohaa Notebook Enthusiast

    Reputations:
    0
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    5
    so pretty much on the first day of using my new asus n56vm (i7, 8gbram, 2gb gt630m), When plugged into the power, would keep flicking constantly between Entertainment and On Battery, it was ridiculous.

    At first I found that keeping the Power4Gear program running as a window seemed to stop it for a bit.
    But then that failed, so I uninstalled it from control panel, and went back to using Windows own plans for Power.

    I just flicked it open from standby just now and the Power4Gear interface came up, and started flicking between Plugged in and on battery!
    I can't seem to get rid of it properly.

    Anyone else had this problem?
     
  2. nipsen

    nipsen Notebook Ditty

    Reputations:
    694
    Messages:
    1,686
    Likes Received:
    131
    Trophy Points:
    81
    Most commonly used phrase in Microsoft's bug database.

    It's probably the user account control thing having a fit. Parts of the program got installed while on admin, the other service not elevated by default on startup, etc.

    If you have an admin account, and then a user account as well on the system, for example - the power4awesomegear doesn't work. Because the function that program is using to get monitor/system access isn't supported in the current UAC scheme. So: parts of the program won't complete, it will be shut down. While the other part of the program detects this, tries to launch the missing component again.

    Rinse, repeat.

    ...

    You know, I actually reported that bug specifically to Asus over a year ago. I'm pretty sure they just "fixed" it by making sure you skip the default "it's recommended to make a user account instead of just the admin account" prompt in their OEM install.

    Of course - for every new revision of Windows they use, they're going to get that problem back in again.