[ipxe-devel] boot.wim overlay?

[Brian Rak]

We have a simple startup script in boot.wim that mounts a remote 
directory via SMB, and executes a script from that.  This gives us a 
mostly-static boot.wim, but we can still easily add customizations.

On 2/17/2014 9:20 AM, Oliver Rath wrote:
> Hi list,
>
> taken from the howto
> http://ipxe.org/howto/winpe#windows_assessment_and_deployment_toolkit_adk i
> can start WinPE via ipxe over net. This runs fine.
>
> If I understand right, wimboot takes all the files (loaded by initrd)
> into a directory and boots the this struct. When booting, at last
> boot.wim will be startet, which is an embedded ramdisk, So this ramdisk
> will be extractet and started (a kind of initramfs for windows?).
>
> Here my question. Could it be possible to load an additional file (i.e.
> boot-enhancements.wim), which is also extracted into the ramdisk as
> overlay? So the boot.wim-system could be customized dynamicly very easy.
> I.e.:
>
> #!ipxe
>    
>    cpuid --ext 29 && set arch amd64 || set arch x86
>    kernel wimboot
>    initrd ${arch}/media/bootmgr                      bootmgr
>    initrd ${arch}/media/Boot/BCD                     BCD
>    initrd ${arch}/media/Boot/Fonts/segmono_boot.ttf  segmono_boot.ttf
>    initrd ${arch}/media/Boot/Fonts/segoe_slboot.ttf  segoe_slboot.ttf
>    initrd ${arch}/media/Boot/Fonts/segoen_slboot.ttf segoen_slboot.ttf
>    initrd ${arch}/media/Boot/Fonts/wgl4_boot.ttf     wgl4_boot.ttf
>    initrd ${arch}/media/Boot/boot.sdi                boot.sdi
>    initrd ${arch}/media/sources/boot.wim             boot.wim
> # here is the new one:
>    initrd ${arch}/media/sources/boot-addons.wim      boot-addons.wim
>    boot
>
>
> I think, the problem is how to instruct wimboot to extract both
> wim-files one upon the other.
>
> Alternativly, is there a way to access to files on another way as
> commiting it in boot.wim and loading it over net?
>
> Tfh!
>
> Regards,
> Oliver
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel