I'll add that setting later, as I'm working on the unattended answer file features. Speaking of which, what was originally a disclaimer message is now a Welcome screen: You will not see nightly installers for this yet. That is because this still needs to be polished
cannot, at this stage of development... understand anyone being more concerned with the aesthethics of a thing, rather than it's functionality..... ... patience is a wonderful thing and usually 'mostly' rewarded. my twopence worth, great job.
The initial .NET Runtime checks for UnattendGen have been added. If DISMTools can't detect either a .NET SDK or a .NET runtime, you will see the following dialog: Clicking Yes on the dialog will download the self-contained version of UnattendGen (the first release of which is now available) and will tell DT to use that version. The location where the downloader adds the self-contained version is in the following screenshot: The checks are rudimentary, and only one use case has been tested (since I need to test if it works when the .NET SDK is installed and when the .NET Runtime is installed), but it works correctly so far. And, also, DISMTools will check if the self-contained version is already present before checking for .NET availability so, if it has already downloaded that version, it will use it and bypass the checks. You can test this functionality in the latest nightly installers.
With the ISO creation tools, you can apply your unattended answer files when creating ISOs. Here are screenshots of the option and the answer file... Setting Answer file contents (plus the Manager!) ...and here is the target installation: Home view of Settings - showing first account and computer name Additional users Expect this functionality in the nightly installers that will come out very soon
The final preview release of DISMTools 0.5.1 has been released. No further preview releases of this version will be released, so please report feedback for the stable version of DT 0.5.1.
hello sir i'm back to you I'm on disc 0.5 update 1 thank you for your work, I simply still can't put in my default language fe fr-fr I install the us-us and fr-fr OC's cab packages by mounting the boot image.wim but nothing happens when I am at the command language and regional settings can activate this command I just want to have my boot.wim in fr-fr by default not us-us please in advance thank you
Development of the next version of DISMTools, 0.6 (codenamed "DTVI"), has started. You can begin finding nightly installers in the "dt_pre_2491" branch:
Now, reporting program exceptions on the repo has become easier by including a note that tells you how to report that problem more clearly: I've made that change because some users struggled to understand what to do and have sent me issues that are just the issue template. Hopefully, this resolves the situation. Otherwise, what would you do?
You can now resize the window of the unattended answer file creation wizard in the latest nightly installer:
DISMTools is becoming a fine software package. Thank you for the time and diligence you have put into making this.
Well, it's been a work in progress since October 2022 on GitHub. It actually started in July of that year
Well, would you look at that? Christoph Schneegans has liked my implementation of his library for the unattended answer file features
I'm currently working on a revamped image information report feature. Now, image info reports will be saved as Markdown files. Here's the result after converting to HTML: This is an experiment, but a special one at that. You don't need to pass /exp, but you need to download a nightly installer from the "dt_pre_2491_infosaver" branch. The installers aren't available yet since I need to convert everything to a Markdown-compatible format. Be sure to look out for edits to this message. Once they are made, you can begin downloading nightly installers from that branch. Meanwhile, what do you think about this change?
What is wrong with the program? Lack of support for Windows 7? I've already stated that it was due to the API and the implications it would cause if it were removed...