[jaclaz]

tacneplong, on Oct 27 2009, 11:19 AM, said:

how can I supplies DISM files from Windows 7 installation
Where and what I need to place files from W7 installation to it works on XP

See here:
http://www.boot-land...?showtopic=9113

I guess that some Registry keys need to be added.

jaclaz

[MrJinje]

jaclaz, on Oct 27 2009, 11:04 AM, said:

tacneplong, on Oct 27 2009, 11:19 AM, said:

how can I supplies DISM files from Windows 7 installation
Where and what I need to place files from W7 installation to it works on XP

See here:
http://www.boot-land...?showtopic=9113

I guess that some Registry keys need to be added.

jaclaz

Meh, looks like it requires Winbuilder, wouldn't want have to support that. Would be useful if converted back into a reg file / batch script.

Probably could work for tacneplong if he wants to guinea pig for us.

[jaclaz]

MrJinje, on Oct 27 2009, 06:40 PM, said:

Meh, looks like it requires Winbuilder, wouldn't want have to support that. Would be useful if converted back into a reg file / batch script.

Probably could work for tacneplong if he wants to guinea pig for us.

Yep , the idea was to get the Winbuilder .script and see what Registry changes it makes.

Winbuilder is after all a batch processor and the Syntax is very similar to "normal" batch.

Here is (at first sight ) the relevant part:

 
If,Not,EXISTDIR,%WindowsDir%\System32\Dism,DirMake,%WindowsDir%\System32\Dism
If,Not,EXISTDIR,%WindowsDir%\System32\Dism\%WimLanguage%,DirMake,%WindowsDir%\System32\Dism\%WimLanguage%
FileCopy,%SourceDir%\sources\Dism.exe,%WindowsDir%\System32
FileCopy,%SourceDir%\sources\wdscore.dll,%WindowsDir%\System32
ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\wimgapi.dll#$q"
ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\wimserv.exe#$q"
ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Drivers#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\drivers\wimmount.sys#$q"
ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Dism#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\Dism\*.*#$q"
ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Dism\%WimLanguage%#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\Dism\%WimLanguage%\*.*#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\CbsProvider.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\CompatProvider.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismCore.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismCorePS.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismProv.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\IntlProvider.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\MsiProvider.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\SmiProvider.dll#$q"
ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\UnattendProvider.dll#$q"
RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT,NextInstance,1
RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Service,wimmount
RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Legacy,1
RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,ConfigFlags,0
RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Class,LegacyDriver
RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,ClassGUID,{8ECC055D-047F-11D1-A537-0000F8753ED1}
RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,DeviceDesc,wimmount
RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000\Control,*NewlyCreated*,0
RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000\Control,ActiveService,wimmount
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Type,2
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Start,3
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,ErrorControl,1
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Tag,5
RegWrite,HKLM,0x2,System\CurrentControlSet\Services\wimmount,ImagePath,system32\DRIVERS\wimmount.sys
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,DisplayName,wimmount
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,Group,FSFilter#$sActivity#$sMonitor
RegWrite,HKLM,0x7,System\CurrentControlSet\Services\wimmount,DependOnService,FltMgr,
RegWrite,HKLM,0x7,System\CurrentControlSet\Services\wimmount,DependOnGroup,
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,Description,Wim#$sMounting#$sDriver
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,DebugFlags,0
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Instances,DefaultInstance,Wimmount#$sInstance
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Instances\Wimmount Instance,Altitude,180700
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Instances\Wimmount Instance,Flags,0
RegWrite,HKLM,0x3,System\CurrentControlSet\Services\wimmount\Security,Security,01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,00,1c,00,01,00
,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,00,00,02,00,60,00,04,00,00,00,00,00,14,0
0,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,
00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,00,18,00,fd,01,02
,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,0
0,00,00,05,12,00,00,00
RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Enum,0,Root\LEGACY_WIMMOUNT\0000
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Enum,Count,1
RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Enum,NextInstance,1
Set,%DismProg%,%WindowsDir%\System32\Dism.exe,PERMANENT

 

jaclaz

[Sydnelson]

Doens't work for me, I try open program here and before several seconds of black screen the following mensage appears:

DISMTOOL.EXE - Application Error

Application has generated a exception that could not be handled.

Process ID=0x1238 (4664), Thread ID=0x111c (4380).

Click OK to terminate.
Click CANCEL to debug.

If I try debug, debug say that JIT debugger was not specified.


I using a Windows 7 x64 with lastest updates and have fully working version of WAIK installed.

Anyone can help me?

[MitsuMan]

Hello

it work just fine to move the install.wim to the root.

today i just need to try to make a new one because i make few errors on the image. but now i get this error

first i open DISMtool and the set the folder for WIM and MOUNT folder and then i click Mount and that works fine then i click ADD Packages

then i get this new error

Quote

PS C:\> DISM.exe /image:F:\work\mounting /Add-Package /PackagePath:F:\work\updat
es

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 0x801f0005

An error occurred while attempting to start the servicing process for the image
located at F:\work\mounting.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\>

[cluberti]

# for hex 0x801f0005 / decimal -2145452027
  ERROR_FLT_INVALID_NAME_REQUEST								 winerror.h
# An invalid name request was made. The name requested cannot
# be retrieved at this time.
# as an HRESULT: Severity: FAILURE (1), FACILITY_USERMODE_FILTER_MANAGER (0x1f),
 Code 0x5
# for hex 0x5 / decimal 5
  ERROR_ACCESS_DENIED											winerror.h
# Access is denied.

So either you don't have access to that directory (or whomever the app is impersonating doesn't have access), or there's something wrong with the request being made. Perhaps procmon.exe running while the app fails would tell you more as to what actually failed.

[MitsuMan]

Hello...

i have another question.

i have now add packages in the dismtool. and i have too install Danish packages..

but how do i make to it install danish instead of english.

Thank you so much for all the help and for this great tool

[urie]

MitsuMan, on Oct 28 2009, 05:34 PM, said:

Hello

it work just fine to move the install.wim to the root.

today i just need to try to make a new one because i make few errors on the image. but now i get this error

first i open DISMtool and the set the folder for WIM and MOUNT folder and then i click Mount and that works fine then i click ADD Packages

then i get this new error

Quote

PS C:\> DISM.exe /image:F:\work\mounting /Add-Package /PackagePath:F:\work\updat
es

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Error: 0x801f0005

An error occurred while attempting to start the servicing process for the image
located at F:\work\mounting.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
PS C:\>

did you dismount and cleanup-wim from earlier on

[MitsuMan]

Hello

i found out why... so now it works again..

[tacneplong]

Can U make it works with xp
I can not use it in XP after put dism file 2 C:\Windows\Sys32
I just do like you show me MrJinje
Should I need to run Winbuilder script
Thanks

[jaclaz]

tacneplong, on Oct 31 2009, 12:36 PM, said:

Can U make it works with xp
I can not use it in XP after put dism file 2 C:\Windows\Sys32
I just do like you show me MrJinje
Should I need to run Winbuilder script
Thanks

Re-read, SLOWLY this time, posts #12,#13 and #14:
http://www.msfn.org/board/je-jins-dism-too...04-page-11.html

Summed up:

• Je Jin is NOT going to support this thing under XP.
  
• There is (hopefully) a way to run DISM under XP.
  
• You DO NOT use Winbuilder for it.
  
• You may EXTRACT from the Winbuilder .script the commands needed to register the .dlls and add the Registry entries
  
• YOU will need to do the experimenting.

Examples:
This line:

Quote

ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\CbsProvider.dll#$q"

"translates" to:
http://winbuilder.net/help/scripts/script_..._ShellExecuteEx

regsvr32.exe /s %Windir%\System32\Dism\CbsProvider.dll

This line:

Quote

RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT,NextInstance,1

means:
http://winbuilder.net/help/scripts/script_...x.html#RegWrite
Add a new key in the Registry, in Hkey_Local_Machine, under \System\CurrentControlSet\Enum\Root\, call it LEGACY_WIMMOUNT, add to it a new value of type 0x04 (Dword) name it Nextinstance and set it's value to 1.
You may also want to strudy the sintax of the Reg.exe app that comes with XP.

I don't want to seem unfriendly , but you are asking for something "advanced" and that will take lots of time to do, you are expected to have "advanced" knowledge (or learn a bit) and do yourself the steps needed to achieve the "advanced" result you are looking for.

jaclaz

[TripNRaVeR]

i used this tool to integrate some updates but i have a tiny question thoes this tool integrate the updates to all the versions on the image?

[cluberti]

It does not, but you can use GImageX to export all of the indexes from all of the .WIM file images you want as sources to combine them into one new .WIM file that you can use, that will work.

[MrJinje]

TripNRaVeR, on Oct 31 2009, 12:15 PM, said:

i used this tool to integrate some updates but i have a tiny question thoes this tool integrate the updates to all the versions on the image?

Actually it can, but you have to mount each version separately and run Add-Packages against it. Since x86 has 5 versions, you will have to repeat the process 5 times.

mmm.. Tastes Like Chicken

This post has been edited by MrJinje: 02 November 2009 - 09:03 AM

[cluberti]

[RickSteele]

I was able to modiy the WIM file with no errors, but, none of the hotfixes or drivers installed upon performing a fresh install; the xml answer file is good. Refer to the attachment for the logs. I must be missing a step; any ideas-Windows 7 Ultimate (x64). Thanks.

[MrJinje]

RickSteele, on Nov 4 2009, 07:39 AM, said:

I was able to modiy the WIM file with no errors, but, none of the hotfixes or drivers installed upon performing a fresh install; the xml answer file is good. Refer to the attachment for the logs. I must be missing a step; any ideas-Windows 7 Ultimate (x64). Thanks.

According to you 7z, you integrated around 60+ Drivers and 9 Updates into your image.

Can you run a Windows Update Scan and confirm that these 9 updates are still showing up as not installed. They will not show up in your list of installed updates, because they were never installed, they were integrated. Is that the source of the confusion ?

As for the drivers, they should already be integrated, run a search of C:\Windows\inf\ for oem1.inf and tell me if you find the file. That is where it should appear if integrated properly, you should find you other 60 drivers in there too. (oem0.inf - oem61.inf are you drivers) Whether or not the drivers actually work with Windows 7 is a whole nother story.

This post has been edited by MrJinje: 04 November 2009 - 08:48 AM

[RickSteele]

MrJinje, on Nov 4 2009, 09:44 AM, said:

RickSteele, on Nov 4 2009, 07:39 AM, said:

I was able to modiy the WIM file with no errors, but, none of the hotfixes or drivers installed upon performing a fresh install; the xml answer file is good. Refer to the attachment for the logs. I must be missing a step; any ideas-Windows 7 Ultimate (x64). Thanks.

According to you 7z, you integrated around 60+ Drivers and 9 Updates into your image.

Can you run a Windows Update Scan and confirm that these 9 updates are still showing up as not installed. They will not show up in your list of installed updates, because they were never installed, they were integrated. Is that the source of the confusion ?

Maybe; my understanding is a fresh install after successfully modifying the wim with DISM should install the compatable drivers and any updates included in the modification-n'est pa'?

As for the drivers, they should already be integrated, run a search of C:\Windows\inf\ for oem1.inf and tell me if you find the file. That is where it should appear if integrated properly, you should find you other 60 drivers in there too. (oem0.inf - oem61.inf are you drivers) Whether or not the drivers actually work with Windows 7 is a whole nother story.

Windows Update shows all of the updates required and not installed; device manager showed no drivers installed-they are all Windows 7 64-bit published for the respective chipsets (ie: x38, Sansung 275T, onboard Yukon LAN controller etc.). However, that said, I think I may have discovered the error on my part; I mounted wim index 1 when Ultra is index 4, boy do I feel stupid So, I think I modified the wrong image. I've just completed running your excellent tool, this time specifying wim index 4. I'm going to backup my current install and complete a fresh install using this one and will post back in a few hours. See attached for this DISM log set-you'll notice the "features" set is populated with more than the index 1 uploaded previously.
The wim was committed both times and demounted; all logs are recorded before committing the wim.

This post has been edited by RickSteele: 04 November 2009 - 09:13 AM

[MrJinje]

RickSteele, on Nov 4 2009, 09:05 AM, said:

Windows Update shows all of the updates required and not installed; device manager showed no drivers installed-they are all Windows 7 64-bit published for the respective chipsets (ie: x38, Sansung 275T, onboard Yukon LAN controller etc.). However, that said, I think I may have discovered the error on my part; I mounted wim index 1 when Ultra is index 4, boy do I feel stupid So, I think I modified the wrong image. I've just completed running your excellent tool, this time specifying wim index 4. I'm going to backup my current install and complete a fresh install using this one and will post back in a few hours. See attached for this DISM log set-you'll notice the "features" set is populated with more than the index 1 uploaded previously.
The wim was committed both times and demounted; all logs are recorded before committing the wim.

OK, you right, first Features.txt was definitely not Ultimate. Good Catch, future readers take note, be sure to set the correct Image Index #.

That's a Deal-Breaker Ladies

Let me know if it works this time.

This post has been edited by MrJinje: 04 November 2009 - 09:51 AM

[RickSteele]

It didn't work; I did not let the install proceed past copying files because it spent no time at all before proceeding to extracting the copied windows files; from much experience I know this to mean it is using the M$ generic drivers, so, I'm going to have to do some research. I read somewhere that Windows 7 will ignore the 3rd party drivers if it "doesn't like them"; although I can't see why the install would not recognize the Intel as superior-one thing I noticed; I mounted the completed wim just now after the failure and saved the logs again without making any other changes. All updates and feature removals still show "pending", the inf's/drivers are all showing in the inf/driver folders (ie: oem1.inf, ....2 etc./iastor.sys and so on). I copied the extracted wim to another directory before dismounting it so I could have a look under the hood.
...oh, oh...how can it use the drivers if it has not extracted them yet...did I jump the gun here do you think?; if you browse to load drivers during setup it dwells copying files in this scenerio because it has to load and configure before extracting, but, if there integrated, it will not know anything until it extracts the image and has a look-see-is this correct?
Thanks

This post has been edited by RickSteele: 04 November 2009 - 11:38 AM