JFX Posted July 5, 2023 Author Posted July 5, 2023 42 minutes ago, Virgus said: Is it already available ? In case affirmative, what is the correct syntax ? Seems, I missed adding this to the F1 Help, there is a -dism: switch taking a file name relative to the DISM folder WinNTSetup_x64.exe NT6 -dism:Sample.ini 1
JFX Posted July 5, 2023 Author Posted July 5, 2023 (edited) 37 minutes ago, Antonino said: I also had jfx tell me to write some RemoveAppx.ini to contain all this, but I do not know if I should use it instead of sample.ini, together with sample.ini in the same subfolder, or someplace else. Yes, create your own RemoveAppx.ini inside DISM folder. Sample.ini is just an example how the .ini it should be formatted. Edited July 5, 2023 by JFX
Antonino Posted July 5, 2023 Posted July 5, 2023 (edited) so when I creeate removeappx.ini, I might as well get rid of sample.ini. I just copy the content from sample to removeappx, right? but to get an overall grasp of the thing, whatever I call an ini file here in the dism subfolder and point to it from the dism slot in the tool mask, it would be processed anyway. I probably have to select one ini, so the inis are mutually exclusive, is this correct? and all in all, do u have any more "harmless", "safe", strings to suggest so we get rid of more things that we do not need, or do we have to go by trial and error on our own? it would be more constructive if each of us told the world here what not to delete lest software x, y and/or z should not work, so we can have a meaningful databank. what do u think of it? Edited July 5, 2023 by Antonino
JFX Posted July 5, 2023 Author Posted July 5, 2023 Yes, sample.ini is just there to give you an idea of the feature, you supposed to create your own *.ini file based on it. 1
Antonino Posted July 5, 2023 Posted July 5, 2023 (edited) for instance, has anyone tried deleting any systemapps to see what happens? I don't know, let's say, another useful thing that I can think of is the different files that guarantee the functioning of ethernet as opposed to the different files that gurarantee the functioning and config of wifi. me I have produced a generous accounting of the nvidia kinda thing. another initiative, probably from someone having ati instead, would be to give all the info possible concerning the minimal dll contribution to have graphic acceleration with ati, as i did with nvidia. I venture to think that miniwin is not to be considered a mere curiosity, but a working os in its own right (at least from a functional point of view), provided one knows what one wants from an os. me, I think i do. Edited July 5, 2023 by Antonino
Antonino Posted July 5, 2023 Posted July 5, 2023 (edited) Another thing I often do when dealing with system32 and syswow64 dlls, is to keep a software-differenced dll bank that I have "set up" thanks to process explorer. when some software so dear to me happens to fail to work on account of a too radical deletion, I run it on a deletion-free system it still works on and while still open, I run process explorer to see what dlls have potentially guaranteed its working. process explorer lets me draw a list of them which i turn int a batch or cmd file that copies all dlls concerned to a folder that I distinctly name and keep, integrate the "chopped" system by copying the dlls to the system32 and/or syswow64 folders without overwriting, and the software concerned resumes working 99% of the times. I think this info would help some other one of us who will have been through "the same movie" another day. Edited July 5, 2023 by Antonino
Virgus Posted July 7, 2023 Posted July 7, 2023 On 7/5/2023 at 7:50 PM, JFX said: Seems, I missed adding this to the F1 Help, there is a -dism: switch taking a file name relative to the DISM folder WinNTSetup_x64.exe NT6 -dism:Sample.ini That's great, I'll extend my scripts with the "new" dism options. Thanks for your prompt reply and talk to you soon. V.
dimo70 Posted July 7, 2023 Posted July 7, 2023 (edited) JFX, thanx for great tool! I have seen the speed of expanding wim and esd is much more hier than if use wimlib for applying images. Is there any trick to reach hiest speed? i saw x4 and x6 after the process of applying. What this digits mean? Edited July 7, 2023 by dimo70
JFX Posted July 7, 2023 Author Posted July 7, 2023 38 minutes ago, dimo70 said: i saw x4 and x6 after the process of applying. What this digits mean? That's the thread count used by wimgapi. See WinNTSetup.ini.txt, by default if uses half of CPU physical cores. You can uses this with imagex.exe or DISM.exe, too. set WIM_FileData_Number_Workers=8 Imagex /apply ... 1
dimo70 Posted July 8, 2023 Posted July 8, 2023 (edited) Greate! i can write this in sample.ini, is it? Or need to do another ini file in DISM? Edited July 8, 2023 by dimo70
Antonino Posted July 8, 2023 Posted July 8, 2023 (edited) U might as well leave sample.ini and modify it instead of creating another 1. Edited July 8, 2023 by Antonino
dimo70 Posted July 8, 2023 Posted July 8, 2023 (edited) 19 minutes ago, Antonino said: U moght as well leave sample.ini and modify it instead of creating another 1. Antonino, you mean i need to write down this one as is: set WIM_FileData_Number_Workers=8 Imagex /apply ... in sample.ini file? or i dont understand ... Edited July 8, 2023 by dimo70
JFX Posted July 8, 2023 Author Posted July 8, 2023 (edited) No, I mean you can use multi threaded WIM apply also with image.exe or DISM.exe on command prompt by just setting WIM_FileData_Number_Workers environment variable. WinNTSetup will load an existing WinNTSetup.ini on start. This .ini can be loaded or saved with Ctrl + L and CTRL + S hotkey and holds most GUI settings. WinNTSetup.ini.txt describes hidden feature than can be added to WinNTSetup.ini. like: [options] UseMultiCore=1 Edited July 8, 2023 by JFX 1
dimo70 Posted July 8, 2023 Posted July 8, 2023 (edited) JFX, this means WinNTSetup by default uses multithread fitures? I insert "UseMultiCore=1" in the [options] of file WinNTSetup.ini and when start setting up Windows 10 it shows 20x Edited July 8, 2023 by dimo70
Antonino Posted July 8, 2023 Posted July 8, 2023 (edited) .@dimo70 The Great Bulgarian I hope ur findings are correct, 20x is like greased lightning! What I initially meant eas that minwin contains txt files that will be processed by the tool if they are meaningful (containing paths to existent files and/or folders), no matter what their files are called (even pamelo.txt is pricessed). In the dism hatch, instead, whatever u specify is processed, so whether it is pamelo, or sample or mangiacaprini, if it is there and u specify it, it will be processed. So, minwin both and Dism either or Edited July 10, 2023 by Antonino
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now