DynaLog was introduced in DISMTools 0.6.1 to provide a logging infrastructure to the program. With version 0.7, this technology will greatly improve with a log viewer. Now, you no longer have to open a text editor to look at events. You will be able to view logs graphically. Version 0.7 will come with 2 versions of this log viewer (which can also be called "DynaViewer"), with differing levels of OS compatibility: The normal edition, for which the source code will be available as part of the solution, will be based on .NET 4.8 and will support Windows 7 SP1 onwards A "Classic" edition, for which the source code won't be available as part of the solution (see below for more info), will be based on .NET 2.0 and can run on operating systems as old as Windows 98: The source code for the Classic edition won't be part of the solution to prevent repetitiveness and any incompatibilities with the rest of the solution. It will most likely be available as a ZIP file inside the solution. I plan on keeping both versions in sync with new features and fixes. Another feature worth mentioning in DynaViewer that's already implemented is command-line support. This allows for an easier integration with DISMTools, specifically in the event of an exception. The implementation of this tool is planned for version 0.7.
Version 0.7 will come with 2 versions still not the language change in boot.wim dism does it very well why not yours I had attached videos I hope that one day he will be like vdism
DISMTools 0.6.2 is now available as a stable release. The update system should pick this version and install it automatically. It will also make its way to WinGet. With this version, you will have to perform slightly different update procedures if you use 0.6.1 (non-Update 1) or earlier: This is also pointed out in the release notes. Please report feedback in order to shape the next version, which is now in development, with some of the planned features now implemented. For instance, DynaViewer is now bundled with DT. Full integration will arrive later. Do note that, from now on, the preview branch "dt_preview" will no longer be used. This is because, when testing PR creation, it still carried over changes from 0.6.2's development. These preview branches will now be called "dt_pre_<version>" (for example, "dt_pre_0.7") and will be deleted once a release is made. Work for a preview release is now on branches with names "dt_prerel_<version>" (for instance, "dt_prerel_2551" for 0.7 Preview 1)
The theme engine is now implemented, and background and foreground colors are starting to use its infrastructure. To test this, a variant of the current color scheme has been created, with darker dark colors and lighter light colors. Screenshot on the left depicts 0.6.2; the one on the right depicts 0.7 Additional changes to the theme engine have been added to modernize parts of the program, primarily glyph getters. Settings are planned to be implemented to change the schemes. The end-user can configure a specific color scheme for each mode (a color scheme for light mode, another one for dark mode). If the program can't find the theme directory (in "bin\themes"), then it will load fallback themes to default to the 0.7 colors. After the changes in the program regarding the theme engine are merged, another thing will be planned for both 0.7 and 0.6.2 Update 1. The restart dialog will be removed for all architectures. This is because multiple AV providers flag it as "malware", even though it just shows a timeout and returns an exit code. Once this change is made, the PE Helper will show the restart dialog, like it used to in the 0.5 Series.
Following the theme engine implementation in Preview 1, a theme editor is now in the works, which will let you create your themes a lot more easily: Like DynaViewer, it will come in 2 versions: a regular one built on .NET 4.8, and a classic one built on .NET 2.0. The latter one, like DynaViewer, does support operating systems as old as Windows 98: The first screenshot depicts Windows 98, the second screenshot depicts Windows Me (no, it still hasn't crashed on me) However, one quirk you will experience on Win9x when saving your themes is that you will see an extra character at the beginning. This is because theme files are saved using Unicode, and 9x uses ASCII. The implementation of the theme designer will be done for Preview 2.
Massive improvements will arrive for those who want to add translations to the program with the language engine. It is a variation of the language engine you'd see in HotInstall, so the big thing now is to move all the translation code into INI files. To speed things up, I had AI generate a PowerShell script that extracts all these blocks, as there are a lot of them scattered across 83 files. Here's the result of that process: I'm quite certain Preview 2 will have fewer changes than usual (much like Preview 1), mostly because of the work for the language engine. I may also use AI to generate more scripts, to speed things up even more. Because of this, there will be quite a bit of inactivity in the repo
After a couple of days, language files are still being ported to INI files, which will later be combined. This, however, has to be done for 88 files, for 5 languages, containing multiple translations. Because of the impending inactivity of the project in the meantime, I decided to continue with the development of the project, primarily on bugfixes or features that don't involve language translations. Will the language engine effort be cancelled? No, it will continue simultaneously with DT. No further changes have been made to that project yet, so the final files can be integrated at any point, and only after that, the code will be refactored. This will most likely mean that these files will not be ready for Preview 2, but for a later one (such as Preview 3 or Preview 4)
Finally starting to tackle a big limitation in the DISMTools PE. Network-based deployments with WDS but, in general, PXE boot. Another thing that has already been done to the PE Helper is the removal of ARMHF (32-bit ARM) support. This is because the market share of 32-bit ARM-based Windows devices is very low (it doesn't go past Windows RT devices), and Windows hasn't supported this architecture since circa 2017, so it's best to move on from this architecture. But the big thing still has to do with networks. Expect new posts regarding improvements.
DISMTools 0.7 Preview 2 now offers basic support for Windows Deployment Services by using the WDS Preparation Script. This script prepares a boot image for WDS compatibility by reinstating Windows Setup as the OS installer. It can also add these images to WDS automatically and set up basic multicast AutoCast transmissions: Sample unicast transmission after preparing the image for WDS Sample multicast AutoCast transmission after preparing the image for WDS When booting clients via PXE, you will see the boot images as usual: These are now available in the latest installers. This is a quick solution to tackle this problem, but the WDS research hasn't finished, and I want to keep using the DT PE and have external helper scripts. Expect to see further announcements in the future.