Such is life with any file hosting site. At the time I couldn't remember the mirror creator site I used and usercloud seemed reliable to me. I expect MDL users to be smart enough not to click on random exe files, especially when I state that I am not giving exe files.
Your Script is Awesome . Thanks a lot lot for putting hard efforts to release latest 1.3.0 update. Regards, [COIN]
@murphy78, remember i once asked for a little modification to support MCT like ISOs (with the separate x86 and x64 folders) for the $OEM$ copy option? Any chance this could be implemented?
Okay, let's say hypothetically I did an auto-copy of these folders. Would I then need to tie them to the index being applied? Because this could get complicated quickly if I'm supposed to differentiate between the x64 version on a x64 applied image. Generally an $oem$ folder will copy over and whatever exists in the the folder will have to sort itself out post-install. But if we have both an x64 and an x86 version with their own $oem$ folders they will both get copied over unless specified.
I dunno if it can be coded but when using the x64 edition of the MCT ISO, the "ISO:\x64\Sources\$OEM$" folder will be copied. ps, ignoring the white noise.
Well I answered my own question I suppose. It's just going to take some work because up until this point the location was independent except for the drive letter. Now the function needs to keep track of the architecture of the index being applied and pass on the information until the oemcopy function is done. So I need to find the architecture, save it to a variable, check that variable when copying the oem folder and look for a subfolder if the existing sources\$oem$ structure doesn't exist. Then if that architecture $oem$ subfolder does exist, copy that instead. Okay... I guess it isn't that daunting of a task...
@murphy78, for the time being i always used the mixed arch. alternative ISO option from "multi_arch_iso.cmd" by @abbodi1406 then the folder structure is default but then the $OEM$ folder needs to contain x86/x64 compatible stuff too. Not related but to inform: Apart from the $OEM$ folder copying is working that method has only one more advantage, the alternative ISO can boot x86 UEFI on x86 UEFI compatible systems, the standard multi-arch MCT ISO can't (and the alt. ISO can be a bit smaller than the MCT ISO). The x86 UEFI stuff is not used that much (i think) but the $OEM$ copying capability is (for me), so if the script can support Multi-Arch. MCT ISOs then we only need to create that one
Well it was not very hard to implement actually, but I still have to test it... So I have to make an oem folder. I guess I could just put a single file called x64.txt or x86.txt in the proper folder structure in the MCT and load it in a vm.
When booting the MCT (like) ISO, you select x86 or x64 and next a normal setup starts and menu.cmd works too.
New Version 1.3.1: Spoiler File Name: murphy78-Diskpart-Apply-v1.3.1.zip File Size: 2.4.1 MB File type: zip/pw PW: MDL2021 sha-1 hash: D0D59CB47AE8A3135998D309CD4A46AC660CC327 File link: https://mir.cr/0TQGML1N 1.3.1 Added Media Creation Tool style x86/x64 $oem$ folder copying that would detect the architecture of the install applied and seek the appropriate $oem$ subfolder to copy Re-worked the add diskpart apply image script to be in line with the support for the default and dual boot format Added esd and split wim support for the add diskpart apply image script for the line that used to detect information from the install.wim Minor other tinkerings not worth mentioning, mostly wording or spacing issues
Confirmed working Spoiler: MCT Like Multi-arch ISO installed by using v1.3.1 Spoiler: Full Installation Video
Added full installation video https://forums.mydigitallife.net/th...apply-image-script.53532/page-13#post-1674975