Windows 7 DISM & driver packages

[razormoon]

Alright, there's obvious limitations to the batch file for this (think directory names with underscores...). I've left the batch and put something together in code for those of you that update drivers frequently, use dism and need to decompress many driver files at once.

Put the file anywhere and when prompted, point it to the ROOT directory of your drivers. It will save the driver directory for future runs and safely decompress driver files while keeping names intact.

If you want to start over (pick new root) just delete the *.ini file.

If there are any bugs to this ultra simple file, please let me know.

W7_DRVPREP

Edited September 4, 2009 by razormoon

[hfeldman]

In case no one has figured it out yet

You have to expand the drivers first then run the inject

for example inside your driver directory run

expand *.* c:\target -- this will expand the all the files to the Directory c:\target

then run

dism /image:C:\mountpoint /add-driver /driver:"c:\target" /recurse

This worked for me. Hope it helps

Howard.

[hfeldman]

In case no one has figured it out yet

You have to expand the drivers first then run the inject

for example inside your driver directory run

expand *.* c:\target -- this will expand the all the files to the Directory c:\target

then run

dism /image:C:\mountpoint /add-driver /driver:"c:\target" /recurse

This worked for me. Hope it helps

Howard.

Edited September 23, 2009 by Tripredacus
removed url

[razormoon]

Correct. You must uncompress files in order for DISM to behave.

[maxXPsoft]

then when you unmount you get

Processing 1 of 1 - Adding package Package_for_KB974332~31bf3856ad364e35~amd64~~6.1.1.1
[==========================100.0%==========================]
The operation completed successfully.

[sp00f]

then when you unmount you get

Processing 1 of 1 - Adding package Package_for_KB974332~31bf3856ad364e35~amd64~~6.1.1.1
[==========================100.0%==========================]
The operation completed successfully.

Thats a package, and not a driver

[tomatthe]

The thread was very helpful in sorting out video drivers for various machines. It may be nice to have the basic info from it stickied at the top of the forum.

[neuropass]

i don't understand... How do you expand the files???

1. downloaded nvidia installation file available at:

http://www.nvidia.com/Download/index.aspx?lang=en-us

and for the GeForce 6800 driver:

http://www.nvidia.com/object/win7_x86_181.71_beta.html

2. doubleclick the file: 181.71_geforce_win7_32bit_international_beta.exe

extract the files to a temp dir like C:\temp\nvidia

close/finish the install program

3. expand all files with an underscore to a seperate directory *.??_

C:\temp\nvidia>expand.exe NvPVEnc.ax_ C:\temp\nvextr\NvPVEnc.ax_

C:\temp\nvidia>expand.exe nvcpl.cp_ C:\temp\nvextr\nvcpl.cp_

C:\temp\nvidia>expand.exe nvapi.dl_ C:\temp\nvextr\nvapi.dl_

... etc. (36 *.??_ files in 181.71_geforce_win7_32bit_international_beta.exe)

but beware to let the extension with the underscore untouched. After

extraction it should be the same name => *.??_

This is the expected name for the integration defined in nv_disp.inf

Copy the rest of the uncompressed files (files with no underscore) to the dir

where the expande files resides and use that path with /add-driver like:

dism.exe /image:C:\temp\mountdir /add-driver /driver:C:\temp\nvextr

(see below)

But now I have a big problem with the commit command. First I type:

dism.exe /mount-wim /wimfile:install.vim /index:1 /mountdir:G:\pub\win7mnt

and the vim file is mounting. After that I type

dism.exe /image:G:\pub\win7mnt /add-driver /driver:G:\pub\nvextr

[MrJinje]

i don't understand... How do you expand the files???

Easy way is to install them into a live OS, then use something like Driver Magician Lite to export them. Here is the link for the portable version.

http://www.drivermagician.com/PortableDML.zip

[neuropass]

Thanks for your reply i got it to work..

[leen2]

Seems like you all made a lot of progress on this. However when scanning through all the posts I failed to see any mention of the biggest problem with DISM here, so I am adding this note to assist those who don't know, or have not figured it out.

Basically DISM is horribly case sensitive, particularly when it comes to file paths. As a result the paths "E:\drivers\driver.inf" and "E:\DRIVERS\DRIVER.INF and any variations of these are completely different to DISM, yet identical to windows. To fix the issue, I found I needed to copy and paste the actual paths in Windows explorer into the command line to get it to work. I also found that if I copied this to Notepad, and constucted the command line in Notepad first, then copied it to the command prompt it also worked. However you also have to be careful when doing this with smart quotes as some text editors convert quotes to smart quotes and this will also appear to be an invalid path to DISM.

Hope this helps.

[MrJinje]

Hadn't heard of that before, can you go into greater detail ?

[maxXPsoft]

Me either

Don't edit cmd files with wordpad or it will add bad stuff.

{\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Calibri;}}
}

Use notepad instead. I use Context a free editor here.

Any long path names with spaces in them have to have quotes around them " "

Dos interpretes spaces in cmd line as starting a new command. even Windows 7 Dos

But if I call Dism and tell it to /Recurse a driver folder it has no problems and doesn't need quotes around something like this

Intel® ICH10 Family SMBus Controller - 3A30

Edited February 12, 2010 by maxXPsoft

[mrookie]

Pardon me for such silly question - but did any one has any success integrating ATI Catalsyt Driver 10.1?? I've nothing but headaches with DISM not able to integrate driver....

[MrJinje]

Pardon me for such silly question - but did any one has any success integrating ATI Catalsyt Driver 10.1?? I've nothing but headaches with DISM not able to integrate driver....

Nothing silly about that question. (save for the fact it's already been answered).

i don't understand... How do you expand the files???

Easy way is to install them into a live OS, then use something like Driver Magician Lite to export them. Here is the link for the portable version.

http://www.drivermagician.com/PortableDML.zip

If you have your catalyst drivers in your OS, just export them, is very easy. Then they can be integrated properly using DISM (or DISM Tool™)