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.

    How to enable ACPI in T410

    Discussion in 'Lenovo' started by hatboy, Mar 1, 2010.

  1. hatboy

    hatboy Notebook Enthusiast

    Reputations:
    0
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    15
    Does anyone know how to enable ACPI function in the T410? I look in the BIOS but couldn't find it. The reason I need to enable this because I can't seem to use daemon tool or alcohol 120% to mount a virtual drive if ACPI function is disable.

    Thanks!
     
  2. ertw

    ertw Notebook Enthusiast

    Reputations:
    16
    Messages:
    26
    Likes Received:
    0
    Trophy Points:
    5
    I had the exact same problem as you when trying to install daemon tools or Alcohol 120%. ACPI is always enabled in the bios, as previously mentioned, and there isn't an option for turning it on or off. My solution was to use Virtual CloneDrive instead. It doesn't rely on SPTD like deamon tools and Alcohol 120% and it's also freeware. I also posted this response in your thread over on the Lenovo forums.
     
  3. hatboy

    hatboy Notebook Enthusiast

    Reputations:
    0
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    15
    Thank ertw, I'll give Virtual CloneDrive a try.
     
  4. hceuterpe

    hceuterpe Notebook Evangelist

    Reputations:
    111
    Messages:
    380
    Likes Received:
    0
    Trophy Points:
    30
    There's no reason why ACPI should EVER be disabled for your T410. Unless you like working on a single core of your two. Sounds like an incompatiblity with their driver.
    Virtual CloneDrive seems to work for me. They self sign their driver which is sorta cheapy (not like Microsoft would ever let them sign anyways considering the number of gray areas Slysoft is involved in), but at least it's better than no signing in x64...