[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

[MrJinje]

RickSteele, on Nov 4 2009, 11:21 AM, said:

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.

This post has been edited by MrJinje: 04 November 2009 - 11:53 AM

[RickSteele]

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...ead.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]

RickSteele, on Nov 4 2009, 12:13 PM, said:

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

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

[RickSteele]

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]

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...?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

[pakito121]

thanks for the tool.

PS C:\> DISM.exe /Mount-Wim /wimfile:C:\W7\urces\install.wim /index:1 /MountDir:
C:\mount

Herramienta Administración y mantenimiento de imágenes de implementación
Versión: 6.1.7600.16385


Error: 3

El sistema no puede encontrar la ruta especificada.

El archivo de registro de DISM se encuentra en C:\Windows\Logs\DISM\dism.log
PS C:\>



this error for me.

This post has been edited by pakito121: 21 November 2009 - 08:51 AM

[alekz2]

I tried to use dism on Windows 7. I mounted wim successfully. Folders and files became available in the folder where I mounted it.

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Mounted images:

Mount Dir : C:\Downloads\WIM
Image File : C:\Downloads\Windows 7\sources\install.wim
Image Index : 1
Mounted Read/Write : Yes
Status : Ok

The operation completed successfully.

But when I tried to perform any of servicing commands, I got similar errors about lack providers that support the command.

dism.exe /image:C:\Downloads\WIM /Get-Packages>1

Error: 87

The get-packages option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Extract from dism.log
2009-11-21 18:08:04, Error DISM DISM.EXE: No providers were found that support the command(get-packages). HRESULT=0

What do I do wrong ? Why dism can't find a provider ?

[MrJinje]

Error87 is usually related to a space in the Install.WIM path. The fix has been to move the files to a space without path or the root of the drive.

Error3 is usually reported as dropping off the So in sources during the sendkeys command while using a non-english language pack. Sadly the fix is the same, move the WIM file to the Root of your partition and it should work fine. Source code for this error has been posted earlier, we have not heard any solution for why "So" is only being dropped while running non-english language packs. (however in this case unicode does not seem to be the issue)

I would be curious to know if the "So" error goes away after switching locale back to english. and if it returns when going non-english again.

Jaclaz, looks good, since my Sapien IDE 45 day trial is long past, it looks like I will be re-writing the whole thing using a real IDE.

This post has been edited by MrJinje: 21 November 2009 - 08:02 PM

[alekz2]

Thank you for the response.

It was a problem with WIM file. I had tried to service it before using vLite. So, when I refreshed contents from Win7 installation image, get-packages started to work correctly.
But I have another strange result.
get-packages found only 2 packages (see below the output). I tried get-drivers command, and it returned only one driver. I believe, that it should be rather long list of packages and drivers. Any idea ?

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Packages listing:

Package Identity : Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7600.16385
State : Installed
Release Type : Language Pack
Install Time : 14.07.2009 4:46

Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7600.16385
State : Installed
Release Type : Foundation
Install Time : 14.07.2009 4:46

The operation completed successfully.

I applied install_wim_tweak.exe and resolved problem with packages list. But list of drivers still conatains only one item. Is it ok ?

This post has been edited by alekz2: 22 November 2009 - 07:27 AM