I've read many a blog, forums, even listened to the official MS video on the tool... getting any driver to integrate in the offline image doesn't work at all, keep getting errors on any INF I try.
Basically I mount the image, nothing hard there, then I expand/extract drivers from the downloaded packages from say ATI and then use the /add-driver /driver:(driver location).
It parses the folder, finds the INF files but then gives errors. Going through the DISM.LOG all I get is that error 0x8007001E is causing the problem and obviously searching on that error doesn't help as there basically zero information about this tool anywhere...
I'm just starting to work on W7 for work, and DISM seems extremely promising, love the idea of packaging the INSANE mess of drivers we have (over 1.5GB) and the supposedly ease of integrating / removing then from an offline mounted image.
Anyways, any help appreciated.
Thanks.
Full Version: Windows 7 DISM & driver packages
Actually, was just able to integrate NIC drivers fine now, but ATI drivers, even the new 9.3 catalyst (downloaded just the driver portion for now) give errors...
Ok, I got other small drivers working as well, but if it has something to do with video, it definitely doesn't work, seems like it's because they're compressed and DISM can't decompress them??
All other drivers were flat out all decompressed (no .dl_ or whatever) and seemed to work. Better get fixed on either MS's side or the driver providers, or keeping tabs on drivers will be more cumbersome that it was before... rather it be ALL old school driver paths or all "new age" packages through DISM than both at the same time...
Ok, I got other small drivers working as well, but if it has something to do with video, it definitely doesn't work, seems like it's because they're compressed and DISM can't decompress them??
All other drivers were flat out all decompressed (no .dl_ or whatever) and seemed to work. Better get fixed on either MS's side or the driver providers, or keeping tabs on drivers will be more cumbersome that it was before... rather it be ALL old school driver paths or all "new age" packages through DISM than both at the same time...
IIRC, ATI drivers require .Net Framework 2.0 to be installed.
Dechy, which ATI driver packages are you trying to intergrate?
Same here with NVidia drivers.
I've tried both 181.71 (Win7) and 182.08 (Vista) with no luck. The Win7 drivers are terrible under Win7. Oddly enough, the Vista version works fantastic!
I've also tried SoundMAX drivers with poor results. Seems at least the NVidia drivers get parsed at least...
About the only thing that worked for me is an IR device driver (for my PVR program).
I've tried both 181.71 (Win7) and 182.08 (Vista) with no luck. The Win7 drivers are terrible under Win7. Oddly enough, the Vista version works fantastic!
I've also tried SoundMAX drivers with poor results. Seems at least the NVidia drivers get parsed at least...
About the only thing that worked for me is an IR device driver (for my PVR program).
CODE
Deployment Image Servicing and Management tool
Version: 6.1.7000.0
Image Version: 6.1.7000.0
Searching for driver packages to install...
Found 8 driver package(s) to install.
Installing 1 of 8 - E:\wimMOUNT\pnpDrivers\1\agrsmv32.inf: The driver package wa
s successfully installed.
Installing 2 of 8 - E:\wimMOUNT\pnpDrivers\2\wdma_emu.inf: The driver package wa
s successfully installed.
Installing 3 of 8 - E:\wimMOUNT\pnpDrivers\3\iaahci.inf: The driver package was
successfully installed.
Installing 4 of 8 - E:\wimMOUNT\pnpDrivers\3\iastor.inf: The driver package was
successfully installed.
Installing 5 of 8 - E:\wimMOUNT\pnpDrivers\4\E1e6032.inf: The driver package was
successfully installed.
Installing 6 of 8 - E:\wimMOUNT\pnpDrivers\4\E1g6032.inf: The driver package was
successfully installed.
Installing 7 of 8 - E:\wimMOUNT\pnpDrivers\5\LXDCprc.inf: Error - An error occur
red. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the targ
et image.
Installing 8 of 8 - E:\wimMOUNT\pnpDrivers\6\NVIDIA_7300GT_X86.inf:
Version: 6.1.7000.0
Image Version: 6.1.7000.0
Searching for driver packages to install...
Found 8 driver package(s) to install.
Installing 1 of 8 - E:\wimMOUNT\pnpDrivers\1\agrsmv32.inf: The driver package wa
s successfully installed.
Installing 2 of 8 - E:\wimMOUNT\pnpDrivers\2\wdma_emu.inf: The driver package wa
s successfully installed.
Installing 3 of 8 - E:\wimMOUNT\pnpDrivers\3\iaahci.inf: The driver package was
successfully installed.
Installing 4 of 8 - E:\wimMOUNT\pnpDrivers\3\iastor.inf: The driver package was
successfully installed.
Installing 5 of 8 - E:\wimMOUNT\pnpDrivers\4\E1e6032.inf: The driver package was
successfully installed.
Installing 6 of 8 - E:\wimMOUNT\pnpDrivers\4\E1g6032.inf: The driver package was
successfully installed.
Installing 7 of 8 - E:\wimMOUNT\pnpDrivers\5\LXDCprc.inf: Error - An error occur
red. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the targ
et image.
Installing 8 of 8 - E:\wimMOUNT\pnpDrivers\6\NVIDIA_7300GT_X86.inf:
only problem is my old Lexmark printer
NVIDIA 181.20_geforce_winvista_32bit_english_whql works fine with Seven here
Could it be my version of 7? I'm vivisecting 7068 currently and trying to keep as up to date with the 7s as possible.
If you can MaxXP, what directories are your drivers in and what was the command line? I'd hate to think I foibled something...
I notice you have a pnp directory..I'm just pointing DISM to an x:\drivers\nVidia folder. <shrug>
I mount with DISM:
Add drivers:
Unmount:
Quite simple, no?
Be aware that this works for my IR drivers...
If you can MaxXP, what directories are your drivers in and what was the command line? I'd hate to think I foibled something...
I notice you have a pnp directory..I'm just pointing DISM to an x:\drivers\nVidia folder. <shrug>
I mount with DISM:
CODE
DISM /MOUNT-WIM /WIMFILE:D:\UA7\SOURCES\INSTALL.WIM /INDEX:1 /MOUNTDIR:D:\TEMP
Add drivers:
CODE
DISM /IMAGE:D:\TEMP /ADD-DRIVER /DRIVER:D:\DRIVERS\NVIDIA
Unmount:
CODE
DISM /UNMOUNT-WIM /MOUNTDIR:D:\TEMP /COMMIT
Quite simple, no?
Be aware that this works for my IR drivers...
you posted the muiz link but i am using the recurse switch. still trying to get all my updates to install so still messin with it.
What recurse are you referring to? I'm trying to point to different directories, even parent. I'm not sure what DISM is looking for. I'd like to know what was your command that made it recursive as I can not figure it out for DISM.
As for parent, I thought an heirarchy of x:\Drivers\display x:\drivers\sound and x:\drivers\printers and point DISM to x:\drivers would work. I don't think so.
EDIT: FYI - I just learned that there is a /forceunsigned switch to add driver (not tested)
ALSO - figured out /recurse
don't know how to use it yet
As for parent, I thought an heirarchy of x:\Drivers\display x:\drivers\sound and x:\drivers\printers and point DISM to x:\drivers would work. I don't think so.
EDIT: FYI - I just learned that there is a /forceunsigned switch to add driver (not tested)
CODE
DISM /IMAGE:D:\TEMP /ADD-DRIVER /DRIVER:D:\DRIVERS\NVIDIA /FORCEUNSIGNED
ALSO - figured out /recurse
don't know how to use it yet
Tried a few other things including the expand command with nothing to show.
Without Expand command:
With Expand command:
I can assure you that nvd3dum.dll is definitely there!
....time to drink a beer....
Without Expand command:
CODE
~
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=37
flq: {_commit_copy_subqueue}
flq: subqueue count=37
flq: source media:
flq: SourcePath - [d:\vista\drivers\display]
flq: SourceFile - [dpinst.exe]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
!!! flq: Error installing file (0x0000001e)
!!! flq: Error 30: The system cannot read from the specified device.
! flq: SourceFile - 'd:\vista\drivers\display\dpinst.ex_'
flq: TempFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\SET4DE1.tmp'
! flq: TargetFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\dpinst.exe'
flq: {SPFQNOTIFY_COPYERROR}
!!! sto: Failed to copy file 'd:\vista\drivers\display\dpinst.ex_' to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\dpinst.exe'. Error = 0x0000001E
flq: {SPFQNOTIFY_COPYERROR - returned 0x00000000}
!!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_copyfile exit(0x000003e3)}
flq: {_commit_copy_subqueue exit(0x000003e3)}
!!! flq: FileQueueCommit aborting!
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_file_queue exit(0x000003e3)}
!!! sto: Failed to copy driver package to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5'. Error = 0x0000001E
!!! sto: Failed to import driver package into Driver Store. Error = 0x0000001E
<<< Section end 2009/04/03 16:07:19.990
<<< [Exit status: FAILURE(0x0000001e)]
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=37
flq: {_commit_copy_subqueue}
flq: subqueue count=37
flq: source media:
flq: SourcePath - [d:\vista\drivers\display]
flq: SourceFile - [dpinst.exe]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
!!! flq: Error installing file (0x0000001e)
!!! flq: Error 30: The system cannot read from the specified device.
! flq: SourceFile - 'd:\vista\drivers\display\dpinst.ex_'
flq: TempFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\SET4DE1.tmp'
! flq: TargetFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\dpinst.exe'
flq: {SPFQNOTIFY_COPYERROR}
!!! sto: Failed to copy file 'd:\vista\drivers\display\dpinst.ex_' to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\dpinst.exe'. Error = 0x0000001E
flq: {SPFQNOTIFY_COPYERROR - returned 0x00000000}
!!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_copyfile exit(0x000003e3)}
flq: {_commit_copy_subqueue exit(0x000003e3)}
!!! flq: FileQueueCommit aborting!
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_file_queue exit(0x000003e3)}
!!! sto: Failed to copy driver package to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5'. Error = 0x0000001E
!!! sto: Failed to import driver package into Driver Store. Error = 0x0000001E
<<< Section end 2009/04/03 16:07:19.990
<<< [Exit status: FAILURE(0x0000001e)]
With Expand command:
CODE
~
flq: source media:
flq: SourcePath - [d:\driver]
flq: SourceFile - [nvd3dum.dll]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
!!! flq: Error installing file (0x00000002)
!!! flq: Error 2: The system cannot find the file specified.
! flq: SourceFile - 'd:\driver\nvd3dum.dll'
! flq: TargetFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\nvd3dum.dll'
flq: {SPFQNOTIFY_COPYERROR}
!!! sto: Failed to copy file 'd:\driver\nvd3dum.dll' to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\nvd3dum.dll'. Error = 0x00000002
flq: {SPFQNOTIFY_COPYERROR - returned 0x00000000}
!!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_copyfile exit(0x000003e3)}
flq: {_commit_copy_subqueue exit(0x000003e3)}
!!! flq: FileQueueCommit aborting!
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_file_queue exit(0x000003e3)}
!!! sto: Failed to copy driver package to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5'. Error = 0x00000002
!!! sto: Failed to import driver package into Driver Store. Error = 0x00000002
<<< Section end 2009/04/03 15:54:24.351
<<< [Exit status: FAILURE(0x00000002)]
flq: source media:
flq: SourcePath - [d:\driver]
flq: SourceFile - [nvd3dum.dll]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
!!! flq: Error installing file (0x00000002)
!!! flq: Error 2: The system cannot find the file specified.
! flq: SourceFile - 'd:\driver\nvd3dum.dll'
! flq: TargetFile - 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\nvd3dum.dll'
flq: {SPFQNOTIFY_COPYERROR}
!!! sto: Failed to copy file 'd:\driver\nvd3dum.dll' to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5\nvd3dum.dll'. Error = 0x00000002
flq: {SPFQNOTIFY_COPYERROR - returned 0x00000000}
!!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_copyfile exit(0x000003e3)}
flq: {_commit_copy_subqueue exit(0x000003e3)}
!!! flq: FileQueueCommit aborting!
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {_commit_file_queue exit(0x000003e3)}
!!! sto: Failed to copy driver package to 'd:\temp\Windows\System32\DriverStore\FileRepository\nv_disp.inf_x86_neutral_a19062f1858dc8d5'. Error = 0x00000002
!!! sto: Failed to import driver package into Driver Store. Error = 0x00000002
<<< Section end 2009/04/03 15:54:24.351
<<< [Exit status: FAILURE(0x00000002)]
I can assure you that nvd3dum.dll is definitely there!
....time to drink a beer....
DISM.exe /image:<path_to_mounted_image_directory> /Add-Driver /driver:c:\drivers /recurse
Lord knows I love my M$, but I feel a hernia coming on thinking of Vista.
I've been doing all of this from within W7 which could be my problem.
I've been doing all of this from within W7 which could be my problem.
QUOTE (fizban2 @ Mar 31 2009, 09:48 AM) 
Dechy, which ATI driver packages are you trying to intergrate?
Sorry, was gone on vacation, holy needed that
So, using the 9-3_vista32_win7_32_dd.exe for ATI (not touching CCC just yet), 181.71 for nVidia.
Like I've mentionned, using dism /image:c:\dism /add-driver /driver:c:\drivers\video\ati /recurse for any drivers and ATI + nVidia won't comply... Realtek sound, Broadcom NIC drivers worked fine.
Exact command line & result:
CODE
C:\Windows\system32>dism /image:c:\dism /add-driver /driver:c:\drivers\video\ati /recurse
Deployment Image Servicing and Management tool
Version: 6.1.7000.0
Image Version: 6.1.7000.0
Searching for driver packages to install...
Found 2 driver package(s) to install.
Installing 1 of 2 - c:\drivers\video\ati\CL_76828.inf: Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
Installing 2 of 2 - c:\drivers\video\ati\CW_77071.inf: Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
Error: 30
The command completed with errors. For more information, refer to the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Deployment Image Servicing and Management tool
Version: 6.1.7000.0
Image Version: 6.1.7000.0
Searching for driver packages to install...
Found 2 driver package(s) to install.
Installing 1 of 2 - c:\drivers\video\ati\CL_76828.inf: Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
Installing 2 of 2 - c:\drivers\video\ati\CW_77071.inf: Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
Error: 30
The command completed with errors. For more information, refer to the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Reading the DISM log file, both end up with the same errors (only took anything not INFO in the log)
CODE
2009-04-06 11:20:20, Warning DISM DISM Provider Store: PID=3532 Failed to Load the provider. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2009-04-06 11:20:23, Error DISM DISM Driver Manager: PID=3532 Failed to install the driver package 'c:\drivers\video\ati\CL_76828.inf'. - CDmiDriverStore::Import(hr:0x8007001e)
2009-04-06 11:20:23, Error DISM DISM Driver Manager: PID=3532 Failed to install the driver package 'c:\drivers\video\ati\CL_76828.inf'. - CDriverPackage::InternalInstall(hr:0x8007001e)
2009-04-06 11:20:23, Error DISM DISM Driver Manager: PID=3532 d:\win7beta\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x8007001e)
2009-04-06 11:20:23, Info DISM DISM Driver Manager: PID=3532 Driver package c:\drivers\video\ati\CL_76828.inf failed to install. (hr:0x8007001e). - CDriverManager::AddDriverPackagesFromCollection
2009-04-06 11:20:24, Error DISM DISM Driver Manager: PID=3532 Failed to install the driver package 'c:\drivers\video\ati\CW_77071.inf'. - CDmiDriverStore::Import(hr:0x8007001e)
2009-04-06 11:20:24, Error DISM DISM Driver Manager: PID=3532 Failed to install the driver package 'c:\drivers\video\ati\CW_77071.inf'. - CDriverPackage::InternalInstall(hr:0x8007001e)
2009-04-06 11:20:24, Error DISM DISM Driver Manager: PID=3532 d:\win7beta\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x8007001e)
2009-04-06 11:20:24, Info DISM DISM Driver Manager: PID=3532 Driver package c:\drivers\video\ati\CW_77071.inf failed to install. (hr:0x8007001e). - CDriverManager::AddDriverPackagesFromCollection
2009-04-06 11:20:24, Error DISM DISM Driver Manager: PID=3532 d:\win7beta\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:1047 - CDriverManager::Internal_DoAddDriverPackage(hr:0x8007001e)
2009-04-06 11:20:24, Error DISM DISM Driver Manager: PID=3532 d:\win7beta\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:512 - CDriverManager::ExecuteCmdLine(hr:0x8007001e)
Why in gods name it's looking for that folder on D is beyond me... that's my CD drive and the only thing it's ever seen if the install DVD (which I left in).
Really at a loss for this
And this is using plain jane build 7000 downloaded from MSDN with only Windows Updates updates installed.
Great info thanks, was not aware Unattended installs were possible under Windows 7.
Cheers
Cheers
Interesting thing to note, I gave MDT 2010 a try, and it "slipstreams" the video drivers fine with no errors... I might just start using that to do all my integration now instead of command line DISM.
QUOTE (Dechy @ Apr 14 2009, 02:16 PM)
Interesting thing to note, I gave MDT 2010 a try, and it "slipstreams" the video drivers fine with no errors... I might just start using that to do all my integration now instead of command line DISM.
does Microsoft Deployment Toolkit 2010 save a log of what switches DISM used ?
/recurse is for if you have more then one driver folder, so you have to point to your driver folder.
/forceunsigned is for non WHQL / BETA drivers , and you have to do those seperate, you have to point to the inf file of the driver.
So first do all your WHQL drivers with /recurse and point to your folder wich contains all your driver folders, then do the non WHQL drivers one by one with : /forceunsigned
CODE
DISM.exe /image:<path_to_mounted_image_directory> /Add-Driver /driver:c:\drivers /recurse
/forceunsigned is for non WHQL / BETA drivers , and you have to do those seperate, you have to point to the inf file of the driver.
CODE
DISM.exe /image:<path_to_mounted_image_directory> /Add-Driver /driver:c:\nonwhqldrivers\ATInonwhql.inf /forceunsigned
So first do all your WHQL drivers with /recurse and point to your folder wich contains all your driver folders, then do the non WHQL drivers one by one with : /forceunsigned
I've tried those, even tried again. Same errors. Also tried MDT 2010...kind of kills the spirit of things and not what I'm looking to do.
Are you using WinPE when deploying? If so, have you tried the "/ScratchDir" argument?
I know that with Vista and Pkgmgr, when using WinPE, you have to set the scratchdir to a local folder (that you create) when injecting ATI and nVidia drivers because the WinPE scratchdir is only like 32 Mb or so, and ATI and nVidia drivers are far larger.
I've only just stated to play with Win7 myself but I found that pkgmgr automaticly calls DISM anyway, which then uses the default scratchdir,so using the DISM command to begin with and specify the sratchdir in the command line should be able to help you out, if you are using WinPE when getting these problems.
I know that with Vista and Pkgmgr, when using WinPE, you have to set the scratchdir to a local folder (that you create) when injecting ATI and nVidia drivers because the WinPE scratchdir is only like 32 Mb or so, and ATI and nVidia drivers are far larger.
I've only just stated to play with Win7 myself but I found that pkgmgr automaticly calls DISM anyway, which then uses the default scratchdir,so using the DISM command to begin with and specify the sratchdir in the command line should be able to help you out, if you are using WinPE when getting these problems.
JohanE,
Tried this and it's no.
Tried this and it's no.
CODE
DISM /IMAGE:D:\TEMP /ADD-DRIVER /DRIVER:D:\DRIVERS\NVIDIA /FORCEUNSIGNED /SCRATCHDIR:D:\TEMP2
OK... this line works for me:
dism.exe /image:"d:\\" /sysdrivedir:"c:\\" /norestart /apply-unattend:"d:\Windows\Panther\Unattend.xml" /scratchdir:d:\uptemp
The only major difference is that I've specified the path to the driver store in the unattend file.
dism.exe /image:"d:\\" /sysdrivedir:"c:\\" /norestart /apply-unattend:"d:\Windows\Panther\Unattend.xml" /scratchdir:d:\uptemp
The only major difference is that I've specified the path to the driver store in the unattend file.
Here's the thing, although I do employ autounattend.xml, I have never dealt with unattend.xml. Without going into too much detail, how does one employ it if there is a difference? I see my own unattend.xml (in panther folder) and it is identical to my autounattend with a few "sensitive deletions". Does one just save autounattend as unattend?
What are the double backslashes as they apply to a DISM command?
Pardon my ignorance.
EDIT***
Ok, I have answered my own questions! However, what kind of code are you using to specifically in your answer file to point to path? And I only ask because I believe there were issues with drive letters once? I could be mistaken... Can you post an example...I can then take it from there.
Thanks!
What are the double backslashes as they apply to a DISM command?
Pardon my ignorance.
EDIT***
Ok, I have answered my own questions! However, what kind of code are you using to specifically in your answer file to point to path? And I only ask because I believe there were issues with drive letters once? I could be mistaken... Can you post an example...I can then take it from there.
Thanks!
Ok, back on this project again... god love the govt; getting pulled from projects and thrown onto other things only to get pushed back onto what you were oing from the get-go...
Anyways, I'm back with the damned DISM / MDT 2010 thing, seems I was wrong about MDT taking in the drivers and not DISM; when I hit the Update on my deployment folder, I get the same errors. But I'm going to leave that one alone for now.
I'm seriously lacking basic knowledge on how DISM & package integration works... but anyways; this scenario is simple! Mount WIM image, add-package for 2 tiny MS updates (KB971180 & KB970858) and the french language pack. No errors, I do the /get-packages and clearly see them there, but with the mention "install pending".
I unmount & commit changes. I then re-mount & re-check /get-packages and yep, they're definitely there. I check WAIK after reloading the WIM and I don't see the packages in there anywhere. Ok. So I copy that WIM file to my USB key & re-install from scratch. The WIM was ~125MB bigger, so another clear indication that the packages are there.
The question: how in hell do I get them to install now? Even after W7 is loaded, it didn't install them automatically (which I thought that's how it was going to do them) and they don't appear anywhere as an option to start the installs...
So yeah, there has to be something basic I'm missing here, like either in my autounattend to tell it to do the install or before closing off the offline image.
The lack of documentation on how DISM works from MS is ridiculous, I'm about to just plug in every darn thing I want to install in the offline image, close the WIM & create a big old ugly script that installs everything instead of using these new "automation tools"
It just really sucks coming from a standpoint where XP tools had no secrets to DISM/WAIK/MDT.
Anyways, I'm back with the damned DISM / MDT 2010 thing, seems I was wrong about MDT taking in the drivers and not DISM; when I hit the Update on my deployment folder, I get the same errors. But I'm going to leave that one alone for now.
I'm seriously lacking basic knowledge on how DISM & package integration works... but anyways; this scenario is simple! Mount WIM image, add-package for 2 tiny MS updates (KB971180 & KB970858) and the french language pack. No errors, I do the /get-packages and clearly see them there, but with the mention "install pending".
I unmount & commit changes. I then re-mount & re-check /get-packages and yep, they're definitely there. I check WAIK after reloading the WIM and I don't see the packages in there anywhere. Ok. So I copy that WIM file to my USB key & re-install from scratch. The WIM was ~125MB bigger, so another clear indication that the packages are there.
The question: how in hell do I get them to install now? Even after W7 is loaded, it didn't install them automatically (which I thought that's how it was going to do them) and they don't appear anywhere as an option to start the installs...
So yeah, there has to be something basic I'm missing here, like either in my autounattend to tell it to do the install or before closing off the offline image.
The lack of documentation on how DISM works from MS is ridiculous, I'm about to just plug in every darn thing I want to install in the offline image, close the WIM & create a big old ugly script that installs everything instead of using these new "automation tools"
It just really sucks coming from a standpoint where XP tools had no secrets to DISM/WAIK/MDT.
So, like I'm just going to chalk it up to the RC/BETA thing...
I'm hoping to get a tip from JohanE as I have never pointed to any drivers from autounattend. That being said, it's only because of the physical drive pointer thing (if that still is an issue). I can get my audio and IR drivers to add...just not the video!
On my journey to working with things that are so-called "robust", it chaps my a** when I run into a brick wall like this. Don't get me wrong...I live to be educated!
Dechy: Have you tried DISM /image:<drive>\<path> /add-package /?
Maybe something there?
I'm hoping to get a tip from JohanE as I have never pointed to any drivers from autounattend. That being said, it's only because of the physical drive pointer thing (if that still is an issue). I can get my audio and IR drivers to add...just not the video!
On my journey to working with things that are so-called "robust", it chaps my a** when I run into a brick wall like this. Don't get me wrong...I live to be educated!
Dechy: Have you tried DISM /image:<drive>\<path> /add-package /?
Maybe something there?
Indeed I did, there's no "install-package" or "enable-package" or something that would tell the OS on first boot (or any pass) to kick off those installs.
I just find it odd, that like you, not all my drivers work, but the ones that do, once "slipstreamed" into the .WIM using DISM, they actually "work" right away, or at least the OS is quite aware of them... but doing the same type of procedures for packages gives completely different results...
Ok, I don't find it odd, I find it frustrating.
I just find it odd, that like you, not all my drivers work, but the ones that do, once "slipstreamed" into the .WIM using DISM, they actually "work" right away, or at least the OS is quite aware of them... but doing the same type of procedures for packages gives completely different results...
Ok, I don't find it odd, I find it frustrating.
check Technet Forum
http://social.technet.microsoft.com/Forums...e2-4135de8fe6b5
some files need expand cmd.
http://social.technet.microsoft.com/Forums...e2-4135de8fe6b5
some files need expand cmd.
@powera
I owe you one.
Here is what I posted on that thread:
===========================================================================
"Working off of INSTALL.WIM of W7x86 7229 in c:\w7 directory.
Extracted nvidia 185.85_desktop_win7_32bit_english_whql.exe to C:\TEMP
EXPAND C:\TEMP\*.*_ C:\DRVRS\NVIDIA
Copied contents of C:\TEMP (minus *.*_) to C:\DRVRS\NVIDIA
At cmd prompt entered:
DISM /MOUNT-WIM /WIMFILE:C:\W7\SOURCES\INSTALL.WIM /INDEX:5 /MOUNTDIR:C:\TEMP
In case you're wondering, Windows 7 Ultimate resides in the 5th index of install.wim...index 4 of x64 install.wim.
DISM /IMAGE:C:\TEMP /ADD-DRIVER /DRIVER:C:\DRVRS\ /RECURSE
I also have audio and IR controller drivers in C:\DRVRS directory.../RECURSE assures that DISM will pick through each directory.
DISM /UNMOUNT-WIM /MOUNTDIR:C:\TEMP /COMMIT
======================================================================================
I owe you one.
Here is what I posted on that thread:
===========================================================================
"Working off of INSTALL.WIM of W7x86 7229 in c:\w7 directory.
Extracted nvidia 185.85_desktop_win7_32bit_english_whql.exe to C:\TEMP
EXPAND C:\TEMP\*.*_ C:\DRVRS\NVIDIA
Copied contents of C:\TEMP (minus *.*_) to C:\DRVRS\NVIDIA
At cmd prompt entered:
DISM /MOUNT-WIM /WIMFILE:C:\W7\SOURCES\INSTALL.WIM /INDEX:5 /MOUNTDIR:C:\TEMP
In case you're wondering, Windows 7 Ultimate resides in the 5th index of install.wim...index 4 of x64 install.wim.
DISM /IMAGE:C:\TEMP /ADD-DRIVER /DRIVER:C:\DRVRS\ /RECURSE
I also have audio and IR controller drivers in C:\DRVRS directory.../RECURSE assures that DISM will pick through each directory.
DISM /UNMOUNT-WIM /MOUNTDIR:C:\TEMP /COMMIT
======================================================================================
Thanks for your efforts razormoon! I've struggled with the integration of ATI Catalyst drivers but the expand command made the difference. 
Would be nice if Dism did that automatically though.
Would be nice if Dism did that automatically though.
Please thank powera and expecially Andreas Weber @ TechNet for this, the missing piece was retaining the *.??_ (underscore) on the expanded files!
And I am sure that software pieces such as MaxXpSoft's Vista 7 UA and newer programmers will take advantage of this...
In eating my own words, I suppose this proves DISM's robustness....<dang it!! ...expecially>
And I am sure that software pieces such as MaxXpSoft's Vista 7 UA and newer programmers will take advantage of this...
In eating my own words, I suppose this proves DISM's robustness....<dang it!! ...expecially>
Pain in the butt having to expand files as soon as new drivers appear! For those of you that are interested in this driver quagmire, I have put together the following...copy and paste to notepad and save as filename.bat:
(Be sure to change the driver directory to match yours...this file can be run from anywhere regardless of driver directory)
As an example, I store all my drivers in E:\driver\32 and E:\driver\64 - within each of these exists DISPLAY, AUDIO, USBUIRT, ETC. This batch will go through every directory if you point it to E:\Driver\.
Known issues: DO NOT add spaces to end of SET and FOR lines or anywhere else for that matter. Trust me!!
Have fun!!
(Be sure to change the driver directory to match yours...this file can be run from anywhere regardless of driver directory)
CODE
REM @echo off
REM Batch file for conversion/expansion of any driver files that do not cooperate with Windows 7 DISM ADD-DRIVER due to compression.
REM This will also parse subdirectories and expand those files as well.
REM For visual confirmation, be sure to refresh your directory to view correct file sizes.
REM Location of original (untouched) driver directory (user defined, don't forget trailing backslash)
SET DRVDIR=C:\DRIVERS\
REM Wildcard pattern to search for compressed files (this example for nvidia, NVAPI.DL_)
SET WILDCARD=*.??_
REM Holds directory\filename of original compressed files (user defined, may be left unchanged)
SET DRIVERS=C:\DRVORG.TXT
REM Holds directory\filename of expanded files (user defined, may be left unchanged)
SET EXPANDED=C:\DRVEXP.TXT
REM Creates log of commands
SET LOG=C:\COOLLOG.TXT
REM Pre-Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q
DEL %LOG% /q
REM Creates standard text file with directory\filename of compressed files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %DRIVERS%
REM Creates second standard text file with directory\filename of expanded files (minus the third ext character (underscore))
for /f "tokens=1,2,3,4,5 delims=_" %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %EXPANDED%
REM Expands files to same directory (expanded files now have only two character extension)
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %DRIVERS%') do EXPAND.EXE -R %%A >> %LOG%
REM Overwrites original files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %EXPANDED%') do MOVE /Y %%A %%A_ >> %LOG%
REM Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q
EXIT
REM Batch file for conversion/expansion of any driver files that do not cooperate with Windows 7 DISM ADD-DRIVER due to compression.
REM This will also parse subdirectories and expand those files as well.
REM For visual confirmation, be sure to refresh your directory to view correct file sizes.
REM Location of original (untouched) driver directory (user defined, don't forget trailing backslash)
SET DRVDIR=C:\DRIVERS\
REM Wildcard pattern to search for compressed files (this example for nvidia, NVAPI.DL_)
SET WILDCARD=*.??_
REM Holds directory\filename of original compressed files (user defined, may be left unchanged)
SET DRIVERS=C:\DRVORG.TXT
REM Holds directory\filename of expanded files (user defined, may be left unchanged)
SET EXPANDED=C:\DRVEXP.TXT
REM Creates log of commands
SET LOG=C:\COOLLOG.TXT
REM Pre-Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q
DEL %LOG% /q
REM Creates standard text file with directory\filename of compressed files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %DRIVERS%
REM Creates second standard text file with directory\filename of expanded files (minus the third ext character (underscore))
for /f "tokens=1,2,3,4,5 delims=_" %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %EXPANDED%
REM Expands files to same directory (expanded files now have only two character extension)
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %DRIVERS%') do EXPAND.EXE -R %%A >> %LOG%
REM Overwrites original files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %EXPANDED%') do MOVE /Y %%A %%A_ >> %LOG%
REM Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q
EXIT
As an example, I store all my drivers in E:\driver\32 and E:\driver\64 - within each of these exists DISPLAY, AUDIO, USBUIRT, ETC. This batch will go through every directory if you point it to E:\Driver\.
Known issues: DO NOT add spaces to end of SET and FOR lines or anywhere else for that matter. Trust me!!
Have fun!!
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
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
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.
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.
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.
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.
Correct. You must uncompress files in order for DISM to behave.
then when you unmount you get
CODE
Processing 1 of 1 - Adding package Package_for_KB974332~31bf3856ad364e35~amd64~~6.1.1.1
[==========================100.0%==========================]
The operation completed successfully.
[==========================100.0%==========================]
The operation completed successfully.
QUOTE (maxXPsoft @ Oct 4 2009, 12:06 AM)
then when you unmount you get
CODE
Processing 1 of 1 - Adding package Package_for_KB974332~31bf3856ad364e35~amd64~~6.1.1.1
[==========================100.0%==========================]
The operation completed successfully.
[==========================100.0%==========================]
The operation completed successfully.
Thats a package, and not a driver
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.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.