'not a valid Win32 application'

Started by
4 comments, last by Jason Z 11 years ago

Hi everyone,

I've recently tried some programs I wrote in DirectX on Windows 7 on two older WIndows XP PCs and both have given me the message '<application>.exe is not a valid Win32 program". Is this a problem with my coding, or is it that I don't have the right redistributable stuff installed on the XP computers? Is there a reason why this would happen, given that it certainly IS a Win32 program, and it runs fine on my Win7 PC?

Thanks!

Advertisement

Have you ever used the tool called "Depends.exe"? It can tell you what libraries your application depends on, and can help you resolve these types of questions.

Thanks, I haven't seen that. I ran it and it seems that my application doesn't depend on anything that shouldn't be present in XP. It is dependent on some .DLLs such as the ones I'm using for my sound engine (and DirectX itself, of course), but I don't think they would produce a 'not a valid Win32 application' message - probably just a 'XXX.DLL wasn't found' or similar.

I've been looking around a bit and it seems that VS2012 compiled programs won't work on XP anyway (people have been getting the same message as me and it's because of the compiler). Perhaps I should try and recompile in VS2008 instead...

Actually there is an update to VS2012 that allows compiling for WinXP. I think it is a different compiler toolchain setting if I recall correctly....

Oh, OK - for now I just set the Platform Toolset to VS2008 mode - I guess that should work too?

To be honest, I haven't tried it out - I don't have any XP machines anymore... :(

This topic is closed to new replies.

Advertisement