Q: “By setting those values, you’re declaring my app and Qt to be fully compatible with Windows XP. exe file, Windows XP and Win2k3 server should run the file fine. exe file, you’re supposed to instead change to 05 00 02 00 00 00 00 00 (two times). However, the linker complained when I tried SUBSYSTEM:WINDOWS,5, so let’s humor Microsoft here and set the binary numbers equivalent to SUBSYSTEM:WINDOWS,5.01 This binary editing is equivalent to the linker setting I mention above, but actually it suffices to change the two 06 numbers to 05. There’s two consecutive series, change both of them to 05 00 01 00 00 00 00 00. exe file with it, go to almost the beginning of the file, you’ll see something along the following lines:
I promised you a more thrilling choice as well, it requires you to have a binary/hex file editor. exe file (and thus targeting 64-bits Windows XP) you instead should set to /SUBSYSTEM:WINDOWS,5.02 Note: if you’re compiling a 64-bits flavored. I thought originally it should be enough to specify /SUBSYSTEM:WINDOWS,5 but then the linker complains: LNK4010: invalid subsystem version number, and it resets it back to 6 🙁 So 5.01 it is. (Those numbers 5 and 6 are the internal Windows version numbers.) By changing it to 5, we declare XP and Win2k3 as kosher chaps too. This means it can run on Windows Vista and later and why Windows XP rejects it. exe file, you see that the SUBSYSTEM:WINDOWS version is set to 6. Why 5.01? Well if you look at the original settings, using for example dumpbin/headers on your. QMAKE_LFLAGS_WINDOWS = /SUBSYSTEM:WINDOWS,5.01 pro file for your project and insert this line (I usually do it at the end): (In case you’re targeting multiple Windows versions.) I have verified this works on Windows XP Service Pack 3 and Windows Server 2003 Service Pack 1 and 2 systems.
One way to verify the bitness: launch your app in Windows 7 or 10, start Task Manager, in the process tab check that your app’s name has a “* 32” suffix.Īlso: This tweaking do not affect or disturb deployment to other, later Windows versions like Windows 7. not a valid Win32 application.”) occurs if you try to start a 64-bit app on a 32-bit Windows XP or Windows 2003 system, so make sure your app is really 32-bit flavored. exe file.Īnd yes, this has to be applied for every app you develop, until XP is gone gone gone… pro file, or you can be more adventurous and binary-patch your app’s. Update thanks to comment below: (use QMAKE_LFLAGS_WINDOWS instead of tweaking the project’s setting): There are basically two ways to fix this the easy way is to add one extra line to your project’s. This error will not occur for Qt with Visual Studio 2010, but it will when using Visual Studio 2012, 2013 or Visual Studio 2015.
0 kommentar(er)
