This version v1.A8c now has support for the .isoPELD and isoPELD1 file extension.
Also version v1.A8d now includes support for dual-architecture 32\64-bit Windows Install ISOs with WIMBOOT. Note: v1.A8d was updated on 2019-01-05 for language strings + other tweaks.
Using the .isoPELD file extension causes an ISO containing a \sources\boot.wim file to boot as usual, but then uses WIMBOOT and ImDisk to load the ISO as a Virtual CD\DVD (usually as drive Y:) so that the files inside the ISO are automatically available to WinPE. .isoPELD runs image #2 in boot.wim while .isoPELD1 runs image #1 in boot.wim. I have not actually found a use for these yet however!
This new Beta version also fixes some typos in all the Sample Disk1 XML files for use with VMs. It seems that Setup is case-sensitive and I had accidentally used...
<Diskid>1</DiskID>
instead of
<DiskID>1</DiskID>
which causes Setup to complain about a bad XML file at line xx in C:\AutoUnattend.xml!
By using VirtualBox+VMUB and the Disk1 XML files, you can now test out an automated install (including an SDI_CHOCO install). Note that you need to allocate 1.5GB or more of RAM to the VM.
See also the previous blog for other changes.
Also version v1.A8d now includes support for dual-architecture 32\64-bit Windows Install ISOs with WIMBOOT. Note: v1.A8d was updated on 2019-01-05 for language strings + other tweaks.
Using the .isoPELD file extension causes an ISO containing a \sources\boot.wim file to boot as usual, but then uses WIMBOOT and ImDisk to load the ISO as a Virtual CD\DVD (usually as drive Y:) so that the files inside the ISO are automatically available to WinPE. .isoPELD runs image #2 in boot.wim while .isoPELD1 runs image #1 in boot.wim. I have not actually found a use for these yet however!
This new Beta version also fixes some typos in all the Sample Disk1 XML files for use with VMs. It seems that Setup is case-sensitive and I had accidentally used...
<Diskid>1</DiskID>
instead of
<DiskID>1</DiskID>
which causes Setup to complain about a bad XML file at line xx in C:\AutoUnattend.xml!
By using VirtualBox+VMUB and the Disk1 XML files, you can now test out an automated install (including an SDI_CHOCO install). Note that you need to allocate 1.5GB or more of RAM to the VM.
See also the previous blog for other changes.