I renamed boot.wim to source.wim so you can see before and after. I was using Windows 8.1 to create the boot.wim file, I just added the mass storage pack and the disk will still boot fine after. The batch files of course work fine for me with 8.1, just you may need to get some updated tools.
That commands should work with deployment tools from Win 7 WAIK installed and using the tools own CMD as admin .
Still happening though: Spoiler Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Error: 87 The export-image 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 Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Error: 87 The export-image 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 Press any key to continue . . . I installed WADT, rebooted but DISM version remains same, should be 6.3. something
If you ran my batch file, then odds are it will use the DISM for Windows 7... you will need to locate the new path for the updated DISM that you wish to build with... Code: ::Compress the 2 indexes to file boot.wim with max compression dism.exe /Export-Image /SourceImageFile:source.wim /SourceIndex:1 /DestinationImageFile:boot.wim /Compress:Max dism.exe /Export-Image /SourceImageFile:source.wim /SourceIndex:2 /DestinationImageFile:boot.wim /Compress:Max to: Code: ::Compress the 2 indexes to file boot.wim with max compression C:\Program Files\Microsoft DISM Path\dism.exe /Export-Image /SourceImageFile:source.wim /SourceIndex:1 /DestinationImageFile:boot.wim /Compress:Max C:\Program Files\Microsoft DISM Path\dism.exe /Export-Image /SourceImageFile:source.wim /SourceIndex:2 /DestinationImageFile:boot.wim /Compress:Max Then it will not use the Windows 7 DISM but the one you specify.
Hard-coding the DISM worked, I was thinking that last night before hittin the sack. Thanks. Integrated chipset and Mass Storage x86 DriverPacks Next step is .NET integration methinks. Not sure if its best to slipstream this or do post-install UPDATE: Installed pro and starter, checked for updates, ticked option to check for additional MS updates. IE 11 installed ok Left with WAT, Silverlight (which I can do anyway via post-install, talk about that down the line), some MS security essentials & Windows defneder stuff as well as KB2533552. .net 4.5.1 was also part of the list but working on integrating that now. Not bad going, certainly beats the 150~200 updates iv been installing at present manually! UltraIso, just copying the updated files back in and saving to recompile ISO = awesome. UPDATE 2: Got my autounattend.xml working last night for the x86 setup, does all I want now bar license key prompt and prompt for a password (not sure if that can be skipped though. Just placed into the ISO via UltraISO again. Going to look at .Net post install now. UPDATE 3 Have my setupcomplete.cmd copying my standard build software to the desktop now Need to look into .NET 4.5 intergration again, got side tracked lol UPDATE 4 .NET 4.5.2 integrated via post-install Looking at automating a few other things such as Directx 9.0c, Panda USBVaccine etc Got it to delete the PostInst folder and Updates folder too
Update 5 Going well so far, got it installing Directx as well during windows setup, maybe do one or 2 other wee apps - MSE perhaps Had a dab in adding drives to the x64 boot.wim as well - done entirely via a script Will then look at putting it all together (if possible)
When I combined x86 & x64 with updates and sata drivers I got a 4.60GB install.wim Murphy78 does have a few script lines to create a split wim file, on mobile so have a look about for his post.
What does everyone recommend? AIO x86/x64 combined or separate x86 and x64? I would be sure my WIM is > 4GB for an x86/x64 combined image I won't be the only person to use this, there's a few others, they have used my previous AIO without issue and installed software manually.