Discussion in 'Windows 7' started by Enthousiast, Apr 16, 2019.
Can you show the progress and tell us what updatepack you've used? And maybe show a picture?
You need to login to view this posts content.
1. Never use spaces in iso filenames
2. "MS OFFICIAL DOWNLOAD 2016.24.06" is not an official MSFT iso (filename).
Amazing job @Enthousiast !
Thank you to all contributors as well
The tool is meant to do the specific job of creating a working windows 7 ISO with an install.esd inside (using the windows 10 iso and the windows 7 iso).
It's better to use the base tool and copy over the content of the driver folders from the full tool download to the base tool folders, you also have to provide the latest WA addons.
I was planning to update the full tool download next week when the new simplix updatepack is expected (due to not having the time to do it now). But i will look at it tomorrow (it's 2:10 AM over here).
it was ALL my fault!!
i did not put Windows 10 ISO into its folder, i thought working for Windows 7 there is no need of 10
so, after all, i understood ESD files can be handled only with a Windows 8-10 system, so that turned on my brain and help me to put a Windows 10 iso just where Enthousiast wanted it to be.
now the Windows 7 setup runs good as always, with an esd compressed and updated image.
thanks again and sorry for the time
No worries, i found an error in the W7_x64_Ultimate_Only.cmd, fixing it and running a full test now.
Can you put some "options" inside your batch ??
; Integrate DART
; Integrate .Net 4.8
; Edition Home Basic
; Edition Home Premium
; Edition ....
so, deleting/leaving the ";" you can enable/disable that job
The integration of .net 48 is handled by the updatepack, leaving it out will result in not integrating it.
As i said at the OP, this tool is not properly coded with variables, it's a fixed script but should be easy to adjust by most people.
I am planning on some sort of main script that will ask for user input and next run the desired options (by help from @mxman2k), but i am dependent on the help of other members with coding skills too, like @Windows_Addict did before.
well, it was just a question
i edited by myself your script to NOT include the Ultimate edition and edited the "name" and "description" of editions
it is a great tool just like that!!
I always wish to see such tools to be perfect and error free, and last time I sent you a couple of codes to fix few things but they weren't even acknowledged by you. I had to refrain myself from sending you more codes.
There is more then this tool in life, i just didn't have the time for it at the moment.
It's my wife's holiday, went for the first time in our life, on our own, on vacation.
Last night i was up till 5am to fix problems in the scripts.
That's fine. but I sent that in april. Kinda makes me wonder if you want to improve it/accept help.
I accept help, and appreciate it, this tool just didn't have priority for me (it worked for me as initially intended, create an AiO win 7 iso with install.esd).
If i have to justify what and when i do things...
there is NO license agreement between MDL developer and tester and user
this forum could switch off everything just now, and nobody have to complain
we have to thanks for every tool they made, they made my (and our) software experience better than before, and they gave all the tools and support for free
Updated the full download tool with the 19.6.15 updatepack, the latest WA's and the fixed W7_x64_Ultimate_Only.cmd.
Updated the bare tool with the fixed W7_x64_Ultimate_Only.cmd.