MSFN Forums > Mr Jinje DISM Tool™

MrJinje

Oct 14 2009, 05:19 PM

Mr Jinje DISM Tool™

This is tool I whip up for mounting Install.wim to offline service Windows 7 OEM installation media. It is Free for Non-Commercial Use.

Few Notes:

How to create OEM DVD Recovery Disk for readers with SLIC in BIOS.

1) Click Mount Wim (choose WIM file and empty folder to mount and be sure to set image index # in combo box)
2) Press Integrate Cert, and choose you cert file
3) Copy/Paste you key into text field and push Install Key button
4) Commit WIM changes
5) Dis-Mount WIM

How to Add Drivers to your Image.

1) Put all you drivers into any folder.
2) Click Mount WIM and then Add Drivers

Afterwards, run the More Info button and check Drivers.txt for to see if and how it worked.

Be sure to Commit WIM before hitting the dis-mount button, otherwise you will lose all your changes.

Supported OS - Windows 7 only
Unsupported OS - Vista XP 2K3 or 2K8 (but could work if user can supplies DISM files from Windows 7 installation - YMMV)

Supported WIM Type - Windows 7 Format only
Unsupported WIM Type - Vista or W2K8 Format (again some functions may be working but YMMV)

Just thought I would share this here. Maybe some of you will find it useful.

Another note - I decided to use the Commit WIM button without UnMounting the Image - Always hated having to unmount to save using other GUI's. But this means, that you first need to Commit WIM, before you can Dis-Mount the WIM, as the Dis-Mount WIM is set to Discard changes (in case you don't like the changes you made) It is programmed in Powershell, obviously you will need to enable Powershell before it can run. Greater detail on all this can be found in the original thread at MDL

To enable Powershell, open Powershell Command prompt and type

CODE

Set-ExecutionPolicy RemoteSigned

Here is a ULZ file that is up to date so one can download all W7 x86/x64, Office 2007, and W2K8 R2 Updates for use with the Add-Packages feature.

Find More Details Here

gosh

Oct 16 2009, 12:17 PM

Thats a nice tool. It would be nice if it had a debug mode so you could see the commands it runs for learning purposes. Ive also heard a new feature of windows 7 is you can remove a driver from the store - before you could only add, not update any drivers. DISM looks like a cool tool in windows 7.

Noise

Oct 16 2009, 01:38 PM

This is fantastic. I'd love to see the source for this...

MAVERICKS CHOICE

Oct 16 2009, 02:37 PM

Is a great tool, thankyou will come in very handy.
NB: Also good to see Gosh frequent here.

sp00f

Oct 16 2009, 05:45 PM

commit button doesnt work

BKR III

Oct 17 2009, 10:19 PM

Great Job and seems to be awesome

MrJinje

Oct 18 2009, 03:36 PM

@others, thanks, hope everyone likes.

@spoof - answered your question in the first post - See "Another Note" section.

@gosh - It is a sendkeys hack, so save for a few commands, all the buttons should open up a new command window before running any DISM commands. Should be able to see if any errors occur there. I'll have to look into how a Remove Driver function might work (if possible)

@noise - Maybe in the future, but not for now, apart from the DISM sendkeys commands it has a few re-useable functions for dialogs, msg boxes, and about 1000 lines of auto-generated windows forms code.

I built a ULZ for myself (and others) that is up to date (as of 10/13/2009) so one can download all W7 x86/x64 and W2K8 R2 Updates for use with the Add-Packages feature. Here is the link

MitsuMan

Oct 27 2009, 03:33 AM

Hello

i have make like this

Work folder where everything is in. under that folder i have one called Win7 and Mount and updates in the root of work folder i have put Disntool.

Then i set the folder option in dismtool and then hit Mount and now it ask for a file i think it need the Install.win and then it ask for a folder i show it to to the Mount folder.

then i get this error.

QUOTE

PS C:\> DISM.exe /Mount-Wim /wimfile:F:\work\win7\urc
untDir:F:\work\empty

Værktøjet Deployment Image Servicing and Management
Version: 6.1.7600.16385

Fejl! 3

The system cannot find the path specified.

DISM-logfilen findes på C:\Windows\Logs\DISM\dism.log
PS C:\>

tacneplong

Oct 27 2009, 04:19 AM

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

MrJinje

Oct 27 2009, 04:37 AM

QUOTE (tacneplong @ Oct 27 2009, 05:19 AM)

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

Should just need this file.

CODE

C:\Windows\System32\DISM.exe

and the entire DISM folder

CODE

C:\Windows\System32\DISM

Probably be easiest to put both in XP System32 folder so the script can find them. This is untested, report back.

MrJinje

Oct 27 2009, 04:43 AM

QUOTE (MitsuMan @ Oct 27 2009, 04:33 AM)

Hello

i have make like this

Work folder where everything is in. under that folder i have one called Win7 and Mount and updates in the root of work folder i have put Disntool.

Then i set the folder option in dismtool and then hit Mount and now it ask for a file i think it need the Install.win and then it ask for a folder i show it to to the Mount folder.

then i get this error.

We have been having issues with Non-English language packs, apparently something is affecting the sendkeys syntax in utero and the until the next release the current fix is to move the WIM to the root of the drive.
Like F:\Install.wim More details here. and here

For some unknown reason it is chopping off the "SO" in source from peoples install.wim paths. But only on builds using a non-english language pack ? Any ideas ?

Here is the source for the Quick Mount button. Basically I read the Variables from the Text Fields, then Prompt the user OK/Cancel, and if they hit OK, if spawns a new command window and runs the DISM command via sendkeys

CODE

$WIM = $SOURCE_WIM.text
$MNT = $MOUNT_DIR.text
$INDEX = $IMAGE_INDEX.Text

$PROMPT = [Microsoft.VisualBasic.Interaction]::MsgBox("Quick Mount the WIM", 'OKCancel,Question', "Last Chance to Cancel");switch ($PROMPT) {'OK' {

Invoke-Item C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Start-Sleep 1
[System.Windows.Forms.SendKeys]::Send("c:{ENTER}CD \{ENTER}CLS{ENTER}DISM.exe /Mount-Wim /wimfile:$WIM /index:$INDEX /MountDir:$MNT{ENTER}")

}'Cancel'{ }}

Somehow the $WIM variable is being passed to the Sendkeys command, minus the SO in source. Can anyone re-create this error for me ? I have not been able to from English Ultimate.

jaclaz

Oct 27 2009, 10:04 AM

QUOTE (tacneplong @ Oct 27 2009, 11:19 AM)

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.net/forums/index.php?showtopic=9113

I guess that some Registry keys need to be added.

jaclaz

MrJinje

Oct 27 2009, 11:40 AM

QUOTE (jaclaz @ Oct 27 2009, 11:04 AM)

QUOTE (tacneplong @ Oct 27 2009, 11:19 AM)

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.net/forums/index.php?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

Oct 27 2009, 11:49 AM

QUOTE (MrJinje @ Oct 27 2009, 06:40 PM)

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:

CODE

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

Oct 28 2009, 11:16 AM

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

Oct 28 2009, 11:34 AM

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

Oct 28 2009, 11:37 AM

CODE

# 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

Oct 28 2009, 01:17 PM

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

Oct 28 2009, 01:35 PM

QUOTE (MitsuMan @ Oct 28 2009, 05:34 PM)

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

Oct 28 2009, 01:40 PM

Hello

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

tacneplong

Oct 31 2009, 05:36 AM

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

Oct 31 2009, 06:09 AM

QUOTE (tacneplong @ Oct 31 2009, 12:36 PM)

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

CODE

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

Oct 31 2009, 11:15 AM

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

Nov 1 2009, 07:40 PM

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

Nov 2 2009, 09:03 AM

QUOTE (TripNRaVeR @ Oct 31 2009, 12:15 PM)

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

cluberti

Nov 2 2009, 10:24 AM

RickSteele

Nov 4 2009, 07:39 AM

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

Nov 4 2009, 08:44 AM

QUOTE (RickSteele @ Nov 4 2009, 07:39 AM)

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.

RickSteele

Nov 4 2009, 09:05 AM

QUOTE (MrJinje @ Nov 4 2009, 09:44 AM)

QUOTE (RickSteele @ Nov 4 2009, 07:39 AM)

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.

MrJinje

Nov 4 2009, 09:49 AM

QUOTE (RickSteele @ Nov 4 2009, 09:05 AM)

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.

RickSteele

Nov 4 2009, 11:21 AM

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

MrJinje

Nov 4 2009, 11:51 AM

QUOTE (RickSteele @ Nov 4 2009, 11:21 AM)

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,

LOL, you jumped the gun, the file copying happens when the installation is under control fom Boot.wim Image 2 (i.e. the GUI that copies files, extracts, choose partition, etc...). That file extraction has not anything to do with OEM drivers, it is part of windows installation process, and being run from Windows PE - Not your OS.

Just let it fully install and you will be fine. Trust me, it does work, almost 2000 downloads between MSFN and MDL, many happy customers. You OS is not actually running until the second reboot. You OEM drivers (especially Unsigned driver's that prompt for Approval), will not be installed until then. In the case of x64, you will get prompted before first login, (and I think it was before SetupComplete.cmd runs too) to install each unsigned drivers. (pop up message for each driver).

As for the Pending thing, that is non-issue, it is because the image was edited offline, M$ documentation clearly describes that user added packages will be marked pending. This is because they are pending until someone actually installs the OS. To avoid the "Pending" you would need to actually install your Image, Sysprep, reseal, and the Recapture the image into a new WIM. After which they will show as installed. But that is way more trouble than is worth.

EDIT: On a side note, you could integrate you Drivers into your Boot.WIM image 2, that would assist anyone having RAID driver issues. That sort of thing.

RickSteele

Nov 4 2009, 12:13 PM

QUOTE

On a side note, you could integrate you Drivers into your Boot.WIM image 2, that would assist anyone having RAID driver issues. That sort of thing.

Oh, I did not know this....

Check this out, third post down:

http://forum.corsair.com/v3/showthread.php?t=82589

since RTW I cannot install in AHCI, just IDE and switch it all over post install with a reg hack and update drivers to Intel in Device Manager

Well, of to the races...be back in a few......

MrJinje

Nov 4 2009, 03:13 PM

QUOTE (RickSteele @ Nov 4 2009, 12:13 PM)

QUOTE

On a side note, you could integrate you Drivers into your Boot.WIM image 2, that would assist anyone having RAID driver issues. That sort of thing.

since RTW I cannot install in AHCI, just IDE and switch it all over post install with a reg hack and update drivers to Intel in Device Manager

Ayup, probably Boot.wim is missing the AHCI drivers, never tried that before, but sounds like could work. Report back if it does.

Edit: OK, guess it don't work.

FIX IT Ballmer

RickSteele

Nov 5 2009, 06:44 PM

QUOTE

Ayup, probably Boot.wim is missing the AHCI drivers, never tried that before, but sounds like could work. Report back if it does.

Nope, I loaded the boot intel drivers into the boot.wim; no go, Windows 7 just simply will not recogize either the SSD or the BIOS. I had to configure IDE to install, BUT, when I tried the routine to get AHCI up and running....one BSOD after another.
So, I was smart this time! LOL; made two separate DVD's-one with AHCI in boot.wim, and one without.
Wiped the HDD, fresh install with only the boot Intel drivers out and Bob's your uncle; now my post install AHCI routine went without a hitch with one difference-it loads up an intel inf_install driver with AHCI in the name instead of the msahci generic; M$'$ AHCI support in this OS needs to be reworked. I have never had any trouble before...XP 64-bit, 2000; just Windows 7 RTW.

QUOTE

Trust me, it does work, almost 2000 downloads between MSFN and MDL, many happy customers.

...add me to them, all updates, feature removals, inf drivers installed perfectly; veeeery niiiice!!!!

jaclaz

Nov 20 2009, 02:02 PM

Follwowing the "DISM working on XP", there is now a new way to mount .wim images under XP, using just three files from Windows 7 (that you can extract with 7-zip from the DVD allright) and a new app by psc over at boot-land (Peter Schlang):
http://nativeex.boot-land.net/Programs/Wim...x/WimCaptEx.htm

Here are some batches to use it without winbuilder:
http://www.boot-land.net/forums/index.php?showtopic=9765

Please NOTE that it is still widely experimental, so DO NOT trust the batches.

@MrJinje
Cannot say if you can adapt the batch routines to your nice tool, possibly as an option for XP users.

jaclaz