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.

    Acer Aspire 5633WLMI Continuous Beeps

    Discussion in 'Acer' started by nlel1975, Mar 25, 2008.

  1. nlel1975

    nlel1975 Notebook Enthusiast

    Reputations:
    0
    Messages:
    33
    Likes Received:
    0
    Trophy Points:
    15
    Hi

    My laptop had 1x 1GB stick in originally and last week I added a 1 x 2GB stick so I have 3GB in total, everything was fine for 2 days, the extra RAM was detected by the machine and all seemed well.

    Then I started getting continuous beeps at the Acer logo screen when the blue bar goes across it paused and beeped continuously untill I pressed the spacebar when it proceded to load Vista. Press F2 to enter setup was also displayed.

    In Vista the touchpad tap function wasn't working and trying to select things with the left button was not working right, I posted on various forums and someone said the same thing happened to him whenever he changed memory configuration and he cured it by going into the BIOS and resaving the configuation.

    So I went into my BIOS and noticed that the DVD drive was no longer the primary boot device, so the BIOS must of lost its configuration sometime after I added the new RAM. I`ve then saved the configuration and exited, so I`m hoping that will cure the problem.

    Is there anything written down anywhere on the Internet that says you should re-save the BIOS configuration after changing amount of total memory?
     
    nlel1975, Mar 25, 2008
    #1
  2. bigozone

    bigozone JellyRoll touring now

    Reputations:
    1,112
    Messages:
    2,730
    Likes Received:
    0
    Trophy Points:
    55
    in the old days (486's and such) BIOS's would often detect a change in the installed ram size and display an error on screen telling the user to enter setup and then save changes and exit.. basically the bios wanted to have it's information match the actual configuration. with newer MBs and bios's i've not encountered this nearly as often as i used to, but it's always good practice to check the bios after such an upgrade just to verify the bios is seeing your changes.

    just my 3 cents,
    bigozone
     
    bigozone, Mar 25, 2008
    #2