Regarding the last post in which I updated the issue template, it seems that it's not working. For that, check out issue 159 of the repo, where someone has done the same thing: create the issue with no information. I'm fed up with these issues because I have to tell issue creators to add details to no avail (they don't come back), so I have to close them as "not planned". I feel disappointed as well, because those issues may have arisen from actual program exceptions that I don't know what they are, due to the lack of information. I need your help with this one. What would you do in a situation like that? As an example, here's the exception dialog. Could it be an issue with that?
You can now test nightly installers from the "dt_pre_2491_infosaver" branch, which contains the revamped Markdown capabilities. This work will be merged with the main "dt_pre_2491" branch. An example report is this one: However, printing support is temporarily disabled because of 2 reasons: Lack of time for the next preview release It won't look pretty on paper, especially with unordered lists There are plans to integrate Markdig so that you can start printing the Markdown content in HTML. And, as a possible solution to the problem in the previous post, look at issue 160. It will separate bug and program exceptions in their respective templates, which I hope will solve the problems
Now, when installing operating systems using the ISO creation tools, you will see a cleaner output:
How portable is this app? Does it leave a zero footprint other than maybe an .ini file. Just trying it out and I ran into this.
For settings, it's just the INI file. It also leaves temporary files if you add AppX packages, to speed things up. As per the Initial Setup Wizard, you'll need to complete it. It's just 4 pages
Ok. the pop-up was misleading for me. I assumed no as an answer to do you want to proceed would quit the app.
Now, you can see Markdown reports in HTML with the web view: Also, for any packages with absurd creation and last update times, the program will append "Preposterous time and date" to the fields. Hint, it's going to be a UNIX system. Experience these changes in the nightly installers of "dt_pre_2492_infosaver".
@hoak, MicroWin has a single purpose: to debloat images. This and other tools go further with manual customizations. However, this is not the thread to be talking exclusively about that
I've got an issue with creating the autounattend.xml file. Once configured I get the following error: Any ideas? Same error appears in .5.1 and the latest nightly build for .6 Appreciate all your hard work. TIA....