@puffyduff MDL doesn't force developers about the licensing & the availability of source of their creations. While (F)OSS is no doubt an extra advantage for community development, it's not an necessary prerequisite here as of yet.
Atak_snajpera@ Have you ever experienced some performance issues when using Intel 7-th gen CPU on Windows 7? When gaming I get a sudden fps drop from 200 fps to 20 fps. It doesn't happen on W10. Most likely some driver issue but hey, only Intel GPU isn't officially supported. External GPU should work flawlessly but it doesn't.
You will have to run some logging app in background (HWiNFO) to track down what is causing this drop (CPU/GPU frequency , CPU/GPU usage , SSD/HDD activity and so on). Also make sure that power saving for HDD/SSD is disabled In power Options.
If you're gonna install Win 7 with DVD (to 7th-8th gen CPU's) you won't need to integrate any drivers before installation, is that right? So with a single freaking DVD-ROM all your problems are gone. Sorry for people with laptops, I know manufacturers no longer put em in laptops.
Not really. It may solve the issue of accessing the boot media itself (the USB storage device inserted in USB 3.x port), but other issues will not be resolved (keyboard/mouse without legacy USB support, NVMe, chipset etc.).
Indeed, i also have a "potato" : [2018-04-09 12:09:29] Host OS: Windows 10 Enterprise x64 () [2018-04-09 12:09:29] Available free space for temp files on partition C: 30.3 GiB [2018-04-09 13:08:44] The operation completed successfully. 1 Hour minus 45 Seconds, even with a SSD Raid0, as a note the cpu never spiked and kept a straight line always below 50%. Name AMD A8-3850 Codename Llano Specification AMD A8-3850 APU with Radeon(tm) HD Graphics Package Socket FM1 (905) CPUID F.1.0 Ancient Stuff. What time is taking on yours recent pcs ? Updated: It ended wihout making the iso. Spoiler ----------------[ DECOMPRESSING winre.wim ]---------------- [2018-04-09 13:07:45] [2018-04-09 13:07:45] [ERROR] Can't open "C:\Users\pmc\Desktop\Windows_7_Image_Updater\Mount\windows\system32\recovery\winre.wim" read-only: No such file or directory [2018-04-09 13:07:45] ERROR: Exiting with error code 47: [2018-04-09 13:07:45] Failed to open a file. ----------------[ install.wim -> Windows Embedded Standard 7 -> winre.wim -> Windows Recovery Environment ]---------------- [2018-04-09 13:07:51] [2018-04-09 13:07:51] Deployment Image Servicing and Management tool [2018-04-09 13:07:52] Version: 10.0.16299.15 [2018-04-09 13:07:52] [2018-04-09 13:07:52] [2018-04-09 13:07:52] Error: 2 [2018-04-09 13:07:52] [2018-04-09 13:07:52] The system cannot find the file specified. [2018-04-09 13:07:52] [2018-04-09 13:07:52] The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ----------------[ CHECKING FOR MOUNTED IMAGE ]---------------- [2018-04-09 13:08:01] [2018-04-09 13:08:01] Deployment Image Servicing and Management tool [2018-04-09 13:08:01] Version: 10.0.16299.15 [2018-04-09 13:08:01] [2018-04-09 13:08:01] Mounted images: [2018-04-09 13:08:02] [2018-04-09 13:08:02] Mount Dir : C:\Users\pmc\Desktop\Windows_7_Image_Updater\Mount [2018-04-09 13:08:02] Image File : C:\Users\pmc\Desktop\Windows_7_Image_Updater\Image\sources\install.wim [2018-04-09 13:08:02] Image Index : 1 [2018-04-09 13:08:02] Mounted Read/Write : Yes [2018-04-09 13:08:02] Status : Ok [2018-04-09 13:08:02] [2018-04-09 13:08:02] The operation completed successfully.
There is something wrong with your iso because selected image "Windows Embedded Standard 7" does not have winre.wim ! Xeon 2690 (8C/16T) , 64 GiB RAM , SSD Single image: ~1h Four images: ~2h
Did you use Delphi or Lazarus? I did a lot of work with Delphi 5 and 7. I also played around with FPC and lazarus. Personally, I would not release the source because you invite all kinds of copy-cat versions of your code. Best of luck with your development. And welcome to the programmers' guild.
@Atak_Snajpera On Windows7\Import\Windows\Setup\Scripts There are several gadgets, intel GPU driver (of which you previously said wouldn't work?) and some other unnecessary stuff. I guess SetupComplete.cmd will install them when convenient. Can we just delete folders of what we wouldn't need?
Included Intel driver will work with SkyLake/KabyLake iGPU (HD 630). It won't work with CoffeLake iGPU (UHD 630). Like what? Audio Driver or VC redistributable and .Net ? Good luck in running apps compiled in Visual Studio without these components installed. Maybe you mean WuaCPUfix?
Almost anything could be unnecessary for some people. For example I would never, ever need IE11 in all eternity. Also I won't need WuaCpuFix since I won't be using built-in windows update(all hail simplix). Options to exclude those things could look good on the tool. But since we don't have it, I'm thinking it's ok to delete the folders manually, right? One more question, does "updated installer" offer anything beneficial to someone without a NVMe drive?
Does this tool work with non-english isos ? I'm getting an error when I'm trying to update and/or integrate drivers in a French iso It works fine when I'm using an English iso though Thanks
Do the Intel Chipset (KabyLake) need to be integrated into the install.wim in order to successfully install Win7 on a KabyLake CPU. Or can the drivers be added after the install?
Intel's chipset "drivers" aren't actually drivers. It's just .inf files that clear up triangles in device manager. You need only storage drivers(USB3.x, SATA AHCI/RAID, NVMe(if you have such storage)). I managed to integrate said drivers(plus kaby chipset "drivers") in a clean windows 7 sp1 x64 image(boot.wim and install.wim) and it booted and detected all storage on a B250/G4600 machine without problems. It's obvious you need all necessary compatibility options enabled(and maybe xHCI hand-off tinkering), but other than that the procedure is no big deal. Safe to say you don't need a tool for the job(at least not one that's 1.3GB in size and, as seen above, problematic at times).
Thnx for the clarification. So hypothetically, if you hadn't added the KabyLake chipset "drivers" to the install or boot.wim (and only the USB3.x, AHCI.RAID, et.c), would the Win7 install on a Kaby CPU be successful?
Yes, it would. At least in my experience it did(no brutal modding/crippling of the os was performed).
Often for unknown reasons the integration process is interrupted. It does not create an ISO image. Depends on the host system. In older versions, this was not a problem. Statement: "Registry settings do not allow you to perform an action." Similarly: https://forums.mydigitallife.net/th...ryzen-threadripper.76335/page-12#post-1425352