"Not a valid Win32 application" error on Windows XP
RikuKawai opened this issue · 8 comments
I'm trying to run this on Windows XP Home, I have SP3 plus the unofficial SP4 installed.
I can't see any reason why it wouldn't work if it's actually 32-bit as described,
The reason I'm using XP is because this is a rather old PC but it has hardware which can output to a CRT TV.
hi!
that's correct. it would maybe theoretically be possible to run on XP, but i'd have to go through quite a bit of pain.
is there no way you can update your OS?
best, hansi.
This machine would have much difficulty running any newer OS. Specs are Pentium 4 3.2GHz, 2GB DDR 557MHz, GeForce GT 430, Radeon X700 Pro (for composite output). I would also lose my ability to natively play old 16-bit software.
I will try using my other board which has a Phenom II X4 and Windows 10 64-bit as that also has a composite output on the onboard video. If that ends up being too slow (there's no graphics driver for Windows 10), I will try my GTX 280 which is the newest card I have with a TV output.
actually that doesn't sound bad enough, should be easy fast enough for 32bit windows 10.
i think you should be able to run 16 bit programs through qemu/dosbox.
anyways, i like the thought of being able to run the oscilloscope down to xp, but it's just too much work for me at the moment. i'm leaving this open though, in case someone else wants to take a stab.
The reason of this is that XP is unsupported.
Compile with VS 2010 compatible compiler.
Windows 7 introduced some kind of hybrid binaries thing.
this should be easily resolved by adjusting compiler settings.
there is also the v140_xp platform toolset to compile for xp in vs15, but i fear it's not as straight forward as switching toolsets.
ok, i'm closing this, because it's too far out for me and no one else has asked for it. if someone wants to work on it, please submit a PR.
@RikuKawai you can actually upgrade your system to Windows 7 32-bits, and still be able to run 16 bits apps.