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 install custom drivers on Vista x64/7 x64

    Discussion in 'Gaming (Software and Graphics Cards)' started by Ruckus, Dec 12, 2010.

  1. Ruckus

    Ruckus Notebook Deity

    Reputations:
    363
    Messages:
    832
    Likes Received:
    1
    Trophy Points:
    0
    This is for those who want to install custom, modded drivers if they are running x64 versions of Windows Vista or Windows 7.

    There is a risk, with any unsigned drivers, there is a reason for Microsoft for having this system, though I believe should have the option to turn off this driver signature enforcer.

    For example, many who use ATi believe the 10.5a drivers are the best so far, but no mobile support. I am using TWL's 10.5a modded for mobile, but you need to disable driver signature enforcer to do so.

    This is where EasyBCD 2.0 comes in.

    Download EasyBCD 2.0: Download EasyBCD 2.0.2 - NeoSmart Technologies
    - Install EasyBCD 2.0
    - After running, click on the Advanced Settings on the left column. Click the advanced tab on the right panel. Near the bottom you'll see a check box for allow installation of unsigned drivers. Click that.
    - Restart. Install drivers. Voila.

    [​IMG]

    Now you can install unsigned drivers on Windows 7 x64 and Windows Vista x64. You can also boot normally.

    Why is this different from other methods.

    First method. Press F8 at bootup. And then choose option to disable driver enforcer. You have to do this every single time you bootup or the unsigned drivers you installed won't work.

    Second method. Use a program like ReadyDriverPlus that does the above automatically for you. You still have to watch it press F8 and so on. If you hate long bootup times, this makes it even worse.

    Third Method. You can use Driver Signature Enforcement Overrider. This program will have you run Windows in dev mode. You get a watermark which you have to install something else to remove. And then you have to manually sign all the drivers. If you miss a few and don't do it right, it won't work and overall tedious, time consuming and sometimes as said, doesn't work leading to frustration.

    EasyBCD 2.0 gets rid of all that.

    Have fun.
     
  2. ViciousXUSMC

    ViciousXUSMC Master Viking NBR Reviewer

    Reputations:
    11,461
    Messages:
    16,824
    Likes Received:
    76
    Trophy Points:
    466
    Have you tested this? You can manually edit the BCD to do the same thing this program should be doing, but it is only the same as running the command prompt to disable enforcement.

    It does not stick between reboots and thats why the F8 method is still needed, or a automation program like ReadyDriver.

    So I am only asking that you tested this, with unsigned drivers because I wonder if it works or not.

    I see not way for it to work unless its automating the F8 like process like ReadyDriver does.

    Be sure that your testing with a file that requires signing, and that you have not previously signed before testing.

    I see your used a 10.5 driver, but I know there are 10.5 drivers out there that install without mod now because the mod creators are getting better at this and finding ways to do it using the original signature of the mobility drivers.
     
  3. Ruckus

    Ruckus Notebook Deity

    Reputations:
    363
    Messages:
    832
    Likes Received:
    1
    Trophy Points:
    0
    Yeah it works for me. I've used the ReadyDriver and Overrider before. Booting up is just like booting up normal, and the custom modded drivers are working.

    I found this originally when I read a post about someone who uses DNA's custom drivers that don't use the method that you mentioned.