Hi guys I've been racking my brains all day trying to find a way to create a working script. I've just finished some tests. I'm going to make the script available for testing purposes only, since there are so many variables and options. The model remains the same. We'll have the option to create a Slim image and another to create a default image. Just answer the questions for the process of your choice. I'll post the package in a few minutes...
thank you @SunLion, you have worked hard to make many wishes come true. Your script keeps getting better and better. But I know enough and thank you, you've given more than my expectations.
@SunLion With 7.8.7 if I would like to remove a particular capability eg. WordPad where should I edit the script, noticed the capability section of the script has now changed? EDIT: I made the test & found WordPad is deleted by default now, which is good for my purpose, the script is great! I don't think it can be refined much further!!
SunLion, I wanted to ask you: in your tool you offer two Start options - 24H2_Integrator_7.8_Start.cmd and Start78.cmd. What is the difference between them for the processed image. Or does it matter which one you use, the result will be the same? Personally, I always use the simplified one - Start78.cmd.
Use the Start 7 x.cmd script, which will not create a log file at the end.This is the difference from 24H2_Integrator_7.x_Start.cmd
Yes, it is now simpler and there are fewer configuration options. I understand that it is better this way.
Yes, that's the only difference. This was created because the codes from the other start can generate errors in some OS, so here is the simple alternative...
I also had an error on the main system Windows_11_IoTEnterpriseS_amd64, but when I installed Windows_10_Core_amd64 as the main system, and launched 24H2_Integrator_7.8_Start, there are no errors, look in the Docs folder. SunLion has the main system installed there, Windows_10_IoT EnterpriseS_amd64. Maybe this is the case, on which main system is 24H2_Integrator_7.8 being checked
Indeed, this could be the cause of the errors, because I don't have any errors here. Let's do a test. Look at the lines below, which are on lines 579 onwards in script 7.8: Notice the code in bold/blue. I added this now, for testing purposes, @fs2com. Copy this code in bold and add it to the script in the same position as above. Save the script and run it again. Let's see what happens...
SunLion, ru-ru_windows_11_enterprise_ltsc_2024_x64_dvd_f9af5773 Upgrading image LTSC to IoT LTSC It won't work on 24H2_Integrator_7.8, now You can add it to the script without breaking the main script 24H2_Integrator_7.8 The script is great! Refined much further !!! Thanks!!! P.S.SunLion, there is no need to fix the script, it is very good, I have already translated it into ru-ru_windows_11_iotenterprise_ltsc_2024_x64_dvd_f9af5773 Thanks!!!
Okay it make sense, since I don't take note which windows edition I used when running the script... sometimes Windows 10, sometimes Windows 11. But the last 2 version I definitely running the script on Windows 11 IOT Enterprise LTSC 24H2 Thanks for your pointer @SunLion, will try with the added code tomorrow.
Guys, I’ll probably ask a strange question: in what way do you open .cmd files for editing so that the line numbers are visible? I use F4 to view and edit Total Comander and I don’t see any line numbers.