Topic: Potential bug with driver signing repression

Edit: I'm going to make a new post

Last edited by jdub (2009-03-01 08:02:38)

Re: Potential bug with driver signing repression

First, I'd disable KTD.  It's not needed anymore since we developed SAD (Stand Alone Driver disc).
Second. Don't use nlite to remove/integrate drivers, or to disable driver signing.  Let DriverPacks BASE handle that for you.
Can you  "read before you post" and post the info requested?
For that laptop, you'd want DriverPack Graphics C for the drivers, and DriverPack Graphics A for the control panel/CCC.  DriverPack Graphics A doesn't contain any drivers for that graphics card.

Please try the above and retest with a fresh source, then post the files requested if you have any other issues.
Thanks for posting.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Potential bug with driver signing repression

I dont use nLite for driver removal or integration. Why should I set nLite to leave driver signing on? It's disabled by default... I think a few other people would have had problems by now if it was to blame. Can anyone tell me if thats causing problems how its doing it?