OverFlow wrote:

SAD uses the inf files in the driver folders... the "list" is the inf files themselves.

if your driver is not matched then windows does not think that your driver is contained in any of the folders they are searched recursively.

Thank you- this is the answer I needed!

mr_smartepants wrote:

Depends on the content of the affected drivers.  Not all drivers are built the same.

...still waiting for the answers to the above questions.

Don't mean to hijack this guys thread- I will make a new one if needed. But here is my situation-


PCI\VEN_10DE&DEV_1056&SUBSYS_14941028&REV_A1\4&143E46F0&0&0008: NVIDIA NVS 4200M   
PCI\VEN_8086&DEV_0126&SUBSYS_04941028&REV_09\3&11583659&0&10: Intel(R) HD Graphics 3000

http://www.dell.com/support/drivers/us/ … tude-e6520 (go to video tab, select win7 x64 as OS)

Looking to get the x64 Win7 drivers for these devices in a pack for SAD2 use.

So- if I extract all of the contents from the nvidia driver, then place them in this location of the 7z file:


am I done then? Is there some list that SAD2 looks at so it knows what drivers are in the packs?

mr_smartepants wrote:

You could post a request in the appropriate threads (with links to the drivers). 
Basically, the way SAD2 works is it extracts all DP_*.7z files and as long as all the files required by each .inf are available, dpinst will install the drivers.

If I place extra drivers into the DP_*.7z files, then run SAD2- will SAD2 be able to install them?