Good morning Currently, to insert personal programs, I also use the RunOnce EX method. I wanted to ask if I could use some specific folders in ToolKit to insert for example the additional fonts, Windows7 Games legacy, DesktopGadgetsRevived-2.0, DX9, Silverlight and various Visual_C ++. Thank you
Hi! As ToolKit has some custom Packs for Windows 7 Games, Sidebar, DX9, no need (except if you prefer your own ) to integer that ones. For all others addings (additional fonts, Games, Sidebar Gadgets, icons, wallapapers, UAP...), uses <Packs\CustomFiles> folder (additional items will be add by a simple copy/paste action) Hope this helpfull
With all due respect, Surely the CMD version has to be the priority? The GUI is not much more than a pretty front end over the same code/functionality, isn't it? The CMD version works. What compelling advantages does a GUI version bring over the CMD version, other than it looks nicer? Sorry to hear about your health and personal issues.
None. It is usually wrapped up in an exe. This has advantage only for the developer. People like me can't see the code which makes it tick. This ticks me off to no end. I would love to see the inner workings of the toolkithelper.exe especially for Defender removal. I had to write my own code for that which actually works better IMHO allowing me to remove Defender from ANY build. Oh well...
....I prefer the GUI version for the practicality you have but depends on how the interface is made, but nothing against CMD as well.
This has been discussed earlier about the advantages of a GUI vs CMD, still will list some of them: - Better Visual appearance and User friendliness - Windows API's for better file/registry handling - DISM API's for better WIM Image handling - No more limitations like in Batch scripting - No more dependency of 3rd party tools - More room for adding more features - Make all selection prior to execution - Execute all changes to the Image at once As said earlier, The ToolKitHelper.exe will be merged with GUI in future and will be a closed source, I do have also planned for a new name for the GUI. ToolKitHelper and the GUI both use the same programming language But the Toolkit.cmd uses the DOS batch which is different from the GUI. Still a lot of time is there for that, so for now the CMD version will be updated regularly. Thanks for asking about my health.
Yes, currently working on that - Finished updating v1809 en-us code with fixes and new components, need to add back updated mui data. - Finished updating v1903 en-us code with fixes and new components, need to add back updated mui data. - Testing and Updating v1809, v1903 code for Core and N editions. - Need to yet fix the v1903 removed components returning through WU. And, also re-structuring the Packs folder, overall will take more time as I need to update the Toolkit.cmd to reflect the new packs structure.
When i click on @MSMG his profile and click posts i get to see all posts and just recent he posted this: https://forums.mydigitallife.net/posts/1536356/