Thx for the new version but am wondering if removing components can be sped up? It takes 40 seconds to remove just one component. I think you got it down to about 10 seconds at one point with v9.3.2
The ToolKit full pack files are around 40-50 GB and each time making changes to the Pack files and uploading them is not so easy here since I do have a very low upload speed here. And, Also keeping them unpacked will make it easier to update and makes it comfortable for users to only download what they need. You can always right click on the set of folders and download them as zip files.
@MSMG Which build v1903 is better to use for modification? 18362.0, 18362.1, 18362.30, 18362.175, 18362.239?
Use chrome browser since the IE or Firefox don't have much buffer to download from MEGA also you can use the MEGA Extensions to download more efficiently. I do use the MEGA hosting for many reasons like - 50 GB Free storage space, now my MEGA account space has reached full. - Convenient for me to upload and maintain. - So far haven't got one take down notice. You don't need to download all the pack files, just make a note of only required folders and download them, you can also select a couple of folders and download them as zipped. Will try to see If I can provide any other download mirror.
Yes that's due to: - Component removal data is not gathered dynamically at run time but instead it is pre-processed and thus the code size is big. - Component removal MUI data has been added for v1809 and v1903 which makes a large chunk of code size. - For v1809 the component removal is done more in-depth, check out the final install.wim with the older version. But that's not which makes the removal slow but it's the code protection added to Toolkit's component removal program which takes more time to execute the code, even I have reduced the compression level to 1 to make it more faster then the previous version but still it take quite a amount of time due to the MUI data added. I need to work on dynamic processing of gathering component removal data which will make the total code size and execution speed to minimal.
Ok. One more thing. Empty subfolders will not be downloaded from mega even I have selected, e.g. ten subfolders. (download as zip) So, can You include these empty subfolders (for Packs folder) into Toolkit distribution archive?
It is just empty subfolders in Packs folders. Problem is, I have to make manually new subfolders every time, now. E.g. CustomRegistry\w10\x64. New folder option, three times.
Yes, will move all the Custom related things like Custom Files, Registry, TS, WinRE etc which are just place holders to something like <ToolKit\Custom> folder so that it will ship along with the main archive instead as Pack files.
I have just begun my own testing of v9.4 Toolkit, but thank you once again @MSMG for your very hard work! Currently using my old method below, so this will change as I progress - I will update soon. Spoiler: METHOD Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Remove all metro apps (4 > 1 > 1 > 8) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) The README.txt says: So should I do a cleanup after integrating Win32Calc before removing apps?
Please do not take me as grammar nazi (even my ChinEnglish is poor ), but You know: Code: echo.Making Custom Registry compatiable with ToolKit's Image Registry...
Yes all feature integrations other than .NET FX 3.5, Updates and custom features need to be done before the removal.
Spoiler: METHOD Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Cleanup (6 > 1) Remove all metro apps (4 > 1 > 1 > 8) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) Is the above method correct (ignore menu numbers and choices just now)? I have added what I believe is the needed extra step in bold. During testing I too have noticed that Toolkit Helper takes about 30 seconds per item. I believe it was 20 seconds with v9.3.2.
Yes, nowadays I do skip typing the words which I do have in my mind and later do correct them often by re-checking. Also due to very fast typing some times I do misplace the characters or do skip it, now I have corrected it in the script. Code: echo.Making Custom Registry compatible with ToolKit's Image Registry...