When I first used the script without modifying it, the editions said "Windows 7 Starter SiMPLiXED", "Windows 7 HomeBasic SiMPLiXED", so on. Now, when I modified the script to remove the branding (I hope I didn't inadvertently break something), one of the editions "Windows 7 Home Professional", like a genuine ISO would have it. I still have some questions: 1. How is Starter integrated into the x64 AiO ISO? I thought Starter was IA-32 only. 2. I made a slight error when modifying the x64 AiO script, and Home Basic says "Windows 7 Home" and says "Windows 7 Starter" as the description. How do I fix this without rebuilding the entire ISO? That takes a long while (half a day when you use .ESD compression). 3. . Obviously it's your choice what you support, but why is the modern script worse? I find that 10's bootloader tends to be more compatible, since it doesn't rely on legacy bios interrupts at all times. The purple background suddenly becoming the Se7en setup background is weird. I think you're supposed to take "background_cli.bmp" from a Se7en ISO:\sources and put it in to the result ISO's sources folder, but MSDN isos have a bunch of files in the sources folder when the result ISO doesn't. How is this so? Plus, that doesn't work. The background stays purple. I know I've been bugging you with questions that are probably dumb, I'm sorry about that. Hopefully I'll be able to make something useful and put it up here For now, I'll just keep lurking I guess.
That's correct, the tool uses simplix packs so i used it in the index names. Long story, it is created to be used for all other SKU creations, based on info by Whatever127 (RIP). The legacy script is currently the most advanced/developped and only needed script. Win 7 is not really a supported OS anymore, i was planning on unifying the modern and legacy scripts but not high on my todo list atm.
OK, makes sense, even if a little narcissistic. Weird that the most limited edition is used as a base, but it works I guess. OK, I'll take your word for it I guess. Right now I'm building a w7 x64 AIO legacy ISO with your tool. I already knew that, it's just that if I need se7en for a specific case (se7en only software, family member insists on it) I can at least not have to install 5 trillion updates with reboots in between then. Also, the unification sounds cool, I hope you get to it sometime.
Sorry if this is obvious, but i just need someone to point me in the right way. I want to integrate my graphics driver (which i obtain from Snappy Driver Installer Origin) so i extract their zip and put both extracted x64 & x32 drivers in the Drivers\ folder. I ran the x64 AiO modern script and it seems to ran just fine and i can install the AiO iso. But after checking device manager, it doesn't seem that my graphics driver is integrated at all. When i check the log i also notice that the usb3 drivers, which present in the Drivers\ folder, is not mentioned. Do i need to append some line in the *Modern.cmd files or *Simplix.bat file to add custom drivers or all i need is to copy files in the respective folder?
Is it able to integrate your own drivers and not just the basic nvme/usb3 ones? did you use the right ones and not the exe?
Thanks for this great solution. I see it creates two temp folders in my system drive C (SSD) to do its thing: AiO_Mount WinRE_Mount I put the tool folder in my drive I: (external HDD) I don't want the tool two write anything to my SSD to prevent wear. Is it possible for this tool to detect and create both folders in the drive were the tool is? TIA
No garantuees but change basically every "%SystemDrive%\AiO_Mount" with "x:\AiO_mount" X=driveletter of your partition same for winre
Thanks it worked. Tool should be able to ask user a custom workpath though. Also Simplix pack should be able to handle a cmd line to set a custom workpath. C:\Windows\Temp is the default working path. Great tool of course! Thanks!
change "%SystemDrive%\AiO_Mount" to aiomountpath or whatever and somewhere in the beginning of script uset "set /p aiomountpath=Choose AIO Mount" or something similar.
I tried running the script without Simplix pack. It worked, thank you. However when I include the Simplix pack it still unpacking in C:\Windows\Temp\
Change the last line in SiMPLiX.bat and SiMPLiX_Boot.bat to include the Code: /Temp=X:\DesiredTempfolder parameter. Make also sure the chosen Temp directory exists.
Something like these lines? Code: "%~dp0exe\UpdatePack7R2-%VER%.exe /Temp=X:\DesiredTempfolder" /WimFile="%~dp0temp\wim\aio.install.wim" /FixOff /Index=* and "%~dp0exe\UpdatePack7R2-%VER%.exe /Temp=X:\DesiredTempfolder" /WimFile="%~dp0temp\wim\aio.install.wim" /boot="%~dp0TEMP\WIN7ISO\Sources\boot.wim" /FixOff /Index=*
Exactly, except for the first double quotes. The first double quotes must enclose the executable path only. The Temp path should not contain spaces etc, but this path (and only the path) can also be enclosed in double quotes. Code: /Temp="X:\Temp"
https://forums.mydigitallife.net/at..._iso_full_tool_3_0_22-4-14_content-txt.59266/ How do you get such layout? It looks like a tree. Nice and handy.
Sorry for the late reply. yes, i have extracted the DP archive and copied the folder containing the .inf file inside to the Drivers folder. then i added one line of code inside the legacy script. Code: :Install_wim ECHO. echo================================================================================= echo Integrating %warch% Drivers into Install.wim... echo================================================================================= %_dism% /mount-wim /wimfile:"TEMP\WIM\aio.install.wim" /index:1 /mountdir:"%SystemDrive%\AiO_Mount" %_dism% /image:"%SystemDrive%\AiO_Mount" /Add-Driver /driver:"Drivers\(W)LAN_7_%warch%" /recurse /ForceUnsigned %_dism% /image:"%SystemDrive%\AiO_Mount" /Add-Driver /driver:"Drivers\nVME_7_%warch%" /recurse /ForceUnsigned %_dism% /image:"%SystemDrive%\AiO_Mount" /Add-Driver /driver:"Drivers\SDIO_7_%warch%" /recurse /ForceUnsigned %_dism% /Unmount-Wim /MountDir:"%SystemDrive%\AiO_Mount" /Commit :RESUME3 It was able to integrate some of my drivers but failed to integrate others. Here's what it printed on the console: Code: Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 6.1.7601.17514 Searching for driver packages to install... Found 8 driver package(s) to install. Installing 1 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-Catalyst-7x64\23.20.15016.15_WU\C7323435.inf: The driver package was successfully installed. Installing 2 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-Catalyst-7x64\26.20.15029.27017_20.4.2\C7355312.inf: Error - An error occurred. The driver package could not be installed. For more information, check for log files in the <windir>\inf folder of the target image. Installing 3 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-Catalyst-7x64\27.20.20912.1002_22.6.1\C7380405.inf: Error - An error occurred. The driver package could not be installed. For more information, check for log files in the <windir>\inf folder of the target image. Installing 4 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-Catalyst-7x64\27.20.20912.1002_22.6.1\C7380461.inf: Error - An error occurred. The driver package could not be installed. For more information, check for log files in the <windir>\inf folder of the target image. Installing 5 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-IOV-7x64\1.2.0.0043\AmdIOV.inf: The driver package was successfully installed. Installing 6 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-PSP-7x64\4.10.0.1\amdpsp.inf: The driver package was successfully installed. Installing 7 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-PSP-7x64\4.5.0.0\amdpsp.inf: The driver package was successfully installed. Installing 8 of 8 - D:\-MASTERFILES\MDL\SiMPLiX_AiO_ISO_Bare_Tool_4_0_23.12.12\Drivers\SDIO_7_x64\AMD-SMBus-NTx64\5.12.0.38\SMBUSamd.inf: The driver package was successfully installed. Error: 30 The command completed with errors. For more information, refer to the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log i could not find the log file and i could not understand the error reference. I checked my current windows 7 installation and i believe my current display driver is the 27.20.20912.1002_22.6.1\C7380461.inf
I never integrate VGA drivers, only the minimum needed ones which the tool provides: (W)Lan/Storage/USB. When these are installed you should have a working system on which you can manually install (or by WU) the other drivers like vga and audio. I can take a look at this (no guarantees) if you provide me your drivers (or the direct download links to the OEM driver page).
That's true. Sorry if my English confuses you. What i mean is that i installed windows 7 on my current machine with iso i created from your tool, later i add some missing drivers using Snappy Driver Installer Origin. I believe you can check their driver packs in download0 [dot] driverpack [dot] io/driverpacks/ (sorry i can't post a link yet). I want to integrate some of that missing drivers so that everytime i reinstall my machine, i can get it running immediately. But in the meantime, i guess this current method is plenty sufficient.