Hello @abbodi1406, I hope you are doing well. Is it possible to run W10UI multiple times automatically based on pre-defined settings? For example, making some W10UI.ini files and run W10UI.cmd files one after another with only one command? In this way, I can make multiple updated ISOs with only running one executable. It will be great if we can also write complete log of each session into separate files, so we find if any of the integrations encountered error by reading log files. Regards,
Thanks for your answer. Would you please answer my first question? I mean regarding make W10UI automated.
Put all different projects into different folders and create a script that calls them? I don't see a need for this, i just start one project and when it's finished i start the next one, just do home and after home is finished create all other skus.
@nima1024 Yes, it can work place the multiple scripts in different locations, each with correctly configured W10UI.ini (Target, Repo, AutoStart..) and run them from another batch script example: Code: call C:\1\W10UI.cmd >log1.txt 2>&1 call C:\2\W10UI.cmd >log2.txt 2>&1 call C:\3\W10UI.cmd >log3.txt 2>&1
You'll also have to edit W10UI.CMD and comment out the pause at the end of the script for it to continue...
Isn't it needed for the W10UI script to return to the calling script to resume with the next W10UI process?
I think it will be automatically return to calling script when we use AutoStart feature of W10UI. They do run after each other ant not simultaneously.
Yes, it is one after the other ends. To execute everything at the same time it would be necessary the command: start "" /i cmd.exe /C "folderpath\scriptname.cmd" Simultaneously it will conflict the moment the DISM is running if you have any DISM execution in this case. But I think what he wants is to be able to let the process running and, when he comes back, see everything ready. Also, simultaneous or not, the time difference can be little. Due to increased processing load and memory use. Of course it depends on the power of the machine.
Abbodi implemented AutoExit only in convert-UUP.cmd. For W10UI.exe and for create_virtual_editions.cmd if is useful.
"Call" or "Start" with "/WAIT" runs sequentially and returns. For running all at one, use "Start" without "/WAIT". I highly doubt that DISM could run multiple tasks in parallel. And if it could, they'd run like .
AutoStart will start the script but when it finishes you have a pause: Code: echo Press 9 to exit. choice /c 9 /n If your using your batch file to run W10UI.cmd, you'd want it to return back without having to press 9...
Actually it exits too Code: 10.11: - If AutoStart option is active, the script will not clear initial screen, and will auto exit at the end