I followed the commands from the readme: The USB stick is reported as being 14.4GB in size after performing these steps. Will try again tomorrow. EDIT: I tried another 16GB USB stick and I got the same error.
In the end I went with Rufus, despite not being OP's favorite, it did the job just fine. As for Win7 Platinum itself what can I say, it is indeed blazing fast, great experience so far.
I think so? It installs just fine and is listed under dotnet --list-runtimes. I don't have any .NET 8 app to test it with though. Runtimes seem to work just fine. I remember reading back when .NET 7 was released that it wasn't supposed to have Win7 support but maybe they reconsidered? As both 7 and 8 work and I can't find any mention that they wouldn't work on the official sites anymore. For .NET 8 development you need VS2022 and Windows 7 only supports up to VS2019.
To be honest, I was quite surprised too, that .NET 7/8 works, I was fully expecting the "api-ms-win-core-path-l1-1-0.dll" etc. style unnecessary incompatibility bulls**t or version-check blocked installers nudging not-so-inconspicuously towards a forced upgrade. I'm just speculating here but it almost seems that maybe MS is backpedaling a bit? I mean Embedded / Server got their 4th ESU year extension, it's not impossible that there'll be another "one more year". Windows 7 is a mature, proven and stable OS while everything after it is hot garbage. Sure, you can live with W10/W11 as an office worker, who cares if it has some bugs or crashes every now and then. But if I were to code a mission-critical Windows-based software for an industrial automation controller, I'd definitely use Windows 7 even today knowing that I can trust the machine to chug along happily for the next 20 years without failing. Maybe there are such customers out there who have noticed the same thing, which would never base their industrial/POS/ATM/terminal/whatever systems requiring high reliability, availability and stability with long uptimes on the dumpster fire of W10/W11, and thus can't be forced to "upgrade". Maybe they've come to realization that pushing too hard will just force even the die-hardest of Windows users to other OS, Linux and macOS. Just keeping ESU alive would keep these customers for cheap.
Windows 7 Embedded has even still support for 32bit, unlike its successor 8.x, and unimpeded by the fact that Win7-based Server is also only available in 64bit, like the Win8.x-based variants. If you still can milk Win7/Server 2008R2 customers with ESU, and it's still enough userbase, why stopping it?
ISO creation took quite a while, at times i thought it was in a loop as i saw the same drivers being installed again ad again. But it completed eventually. Diskpart method giving me same error as g2s. Using 16gb sandisk ERROR: Cannot set length for output file : There is not enough space on the disk. : F:\sources\install.swm
Hmm wtf, which OS are you using 'diskpart' on? I'm only using Windows 7 and it never fails, maybe you're using 8/10/11 and their diskpart has introduced some bug, that's the only thing I can think of. Try using the B) option, 'fat32format', to format the drive as FAT32. And yeah, the whole process of creating the ISO takes like 30 minutes. That's normal. No one has ever blamed Microsoft's tools of being fast.
Nobody seems to have answered you so: you're making a fat32 partition and trying to put a >4GB file on it.
Well then I guess 4095 isn't a very safe size(considering fat32). 3999 would probably be much safer. And yes, I understand why it's close to 4100 in the script, milking the individual swm file's size to the maximum allowed by fat32, but if 4095 is a hit or miss, why bother for the extra few megabytes milked? Just go with a size that doesn't even start with "4" and you should be bulletproof.
Thanks for the need to refresh my memories 2^32-1 = 4294967295 bytes = 4GB = 4095.9999990463257 MB As you said, it is hit or miss and we are within the boundary. But lets see what the guys report...
When trying to boot this computer into a fresh installation of Windows 7 Platinum, it sits forever at the "Starting Windows" screen, even if I boot it into safe mode or low-resolution graphics mode. Would anyone be able and willing to help me, please?
You didnt mention anything about UEFI/CSM. Specs say it at least has CSM mode. After we sorted that out, you could try a W7 Installer with Win10 Boot Efis like Enthousiasts
My apologies; I forgot. I was using UEFI mode, and am about to try again using CSM mode. e: CSM mode didn't work, but UEFISeven did. \o/
Can you look into adding the UEFI boot files? It was mentioned that the Win 8 files will work for installation and the Win 10 files for a preexisting install. Have you tried this?