EmuGUI can't open QEMU when it switches to subprocess.run on Windows

[Tech-FZ]

I know, I was underestimating the issue. It was first reported by lewellyn on the EmuGUI Discord server and the date doesn't seem to matter. I could verify it while working on the next pre-release of EmuGUI.

lewellyn's logs:

c
2000-01-01T00:00:00
[('C:/Program Files/qemu/qemu-system-x86_64.exe',)]
Qemu couldn't be executed. Trying subprocess.run
qemu-system-x86_64.exe: invalid datetime format
valid formats: '2006-06-17T16:01:21' or '2006-06-17'

My specs:

• OS: Windows 10 Pro 22H2 x64
• CPU: Intel Core 2 Duo E8400 (Dual-Core, 3 GHz)
• RAM: 12 GB DDR3
• GPU: AMD Radeon R7 240 4 GB (Sapphire)
• HDD: 250 GB SATA HDD + 500 GB SATA HDD + 320 GB USB HDD
• EmuGUI: 1.2.0.5500_dev (Script version)
• QEMU: 8.0.2

lewellyn's specs:

• OS: Windows x64
• EmuGUI: 1.0.2.5312 (Windows)
• QEMU: 8.0.2

Workarounds

• One way is to use WSL and run the Linux binaries.
• If you wanted to switch to Linux anyway, you could also use that.

Linux probably uses subprocess.run. Is it affected as well? Fortunately, it isn't. You can use EmuGUI on Linux as-is.

Which versions of EmuGUI are affected? So far, I assume EmuGUI 1.0.2.5312 and onwards are affected. I'll try to fix it as soon as possible tho.

[KoghaandSooga]

I think QEMU is meant for NON Windows OS (To boot on not actual emulation) even though it has Windows support I think it's more of an afterthought which is why there is no GUI yet that actually works. The devs that tried these GUI's realized that QEMU made a complete ass out of them and gave up plus the bad economy everywhere means less free time to deal with such headaches.

We are in an era of electronics making an ass out of us because of the broken generation we are in.