ege914, ok, build 6622 is up, it fixes the main issues, duplicate lines removal and Turkish characters breaking the lines.
Let me know if now you can integrate updates and it's functional, then we can deal about polishing it up.
Notes:
- Turkish special characters in your status text (non-functional part of the script) are replaced to preserve the text, will be improving this in the future with better codepage detection, for now this is just cosmetics but I do understand it's not perfect
- RD and Del of Scripts folder is trimmed and moved after the updates insertions, naturally so the files don't get removed before executed, those that require it. But I need your input if your complex call statements are still intact in their intent
- You should be able to use the Placeholder row to position the updates insertion on the Post-setup page. Same for any row on that page.
As for OOBE.cmd, should not be influenced by configuring Windows, but do make sure your OOBE compatibility is turned on if removing components, and potentially errors in SetupComplete make it abort, so we should first deal with the main task at hand.
You can also add .NET CAB to the Updates page and integrate earlier, no need for execution during setup.
Let me know how it goes.
Thanks.
Let me know if now you can integrate updates and it's functional, then we can deal about polishing it up.
Notes:
- Turkish special characters in your status text (non-functional part of the script) are replaced to preserve the text, will be improving this in the future with better codepage detection, for now this is just cosmetics but I do understand it's not perfect
- RD and Del of Scripts folder is trimmed and moved after the updates insertions, naturally so the files don't get removed before executed, those that require it. But I need your input if your complex call statements are still intact in their intent
- You should be able to use the Placeholder row to position the updates insertion on the Post-setup page. Same for any row on that page.
As for OOBE.cmd, should not be influenced by configuring Windows, but do make sure your OOBE compatibility is turned on if removing components, and potentially errors in SetupComplete make it abort, so we should first deal with the main task at hand.
You can also add .NET CAB to the Updates page and integrate earlier, no need for execution during setup.
Let me know how it goes.
Thanks.