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.

    M1210 broken mute button

    Discussion in 'Dell' started by some_guy282, Mar 24, 2007.

  1. some_guy282

    some_guy282 Notebook Enthusiast

    Reputations:
    0
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    5
    The mute button on my M1210 seems to be buggy as of today. I first noticed the problem when listening to a podcast on iTunes while browsing with Firefox. iTunes was operating in the background, and I hit the mute button to listen to someone near me, but the computer didn't mute completely. It only muted for a fraction of a second and then went on with sound. I had to pause iTunes. Upon further examination I discovered that this only happens when I hit mute and iTunes is in the background. If I'm focusing on iTunes in Windows and hit the mute button, the system will mute fine.

    I also just discovered the opposite problem with Firefox and web based sound. I was at a friend's Myspace page which had music, and I tried to mute my system briefly. Same problem - it only muted for a fraction of a second and then went on.

    The only recent change in my system I can think of that may be connected is that I just installed the latest version of iTunes (7.1.1.5). Any ideas?
     
  2. PCModifiers

    PCModifiers Notebook Consultant

    Reputations:
    61
    Messages:
    192
    Likes Received:
    0
    Trophy Points:
    30
    i would reinstall quickset for starters
     
  3. some_guy282

    some_guy282 Notebook Enthusiast

    Reputations:
    0
    Messages:
    25
    Likes Received:
    0
    Trophy Points:
    5
    Good idea, and something I should have done anyway as I didn't have the latest version. However, that hasn't fixed the problem...