Version 1.17b14 invalid win32 app in win 2000?

[muquit]

From ctalip...@bellsouth.net on January 11, 2014 19:31:47

What steps will reproduce the problem? 1. execute the program What is the expected output? What do you see instead? Expected is to see the program work but rather it says "mailsend.exe is not a valid win32 application" What version of the product are you using? On what operating system? 1.17b14 on win 2000 Please provide any additional information below. I realize you say you fixed a 2000 issue on 1.17b5 so i was hoping that would address my problem so i downloaded 1.17b14 and still had teh same problem. I was orginally trying with version 1.17b1. I just wanted to report this in case you wanted to know

Attachment: mailsend-1.17b14.JPG

Original issue: http://code.google.com/p/mailsend/issues/detail?id=43

[muquit]

From muq...@gmail.com on January 13, 2014 11:58:10

I don't have access to Windows 2000, so unfortunately I can not verify.

[TekBear]

Tip: If you don't have a smart hex editor tool you can upload your EXE file to virustotal.com it will show the data in the PE32 headers. For mailsend v1.17b15 - https://www.virustotal.com/en/file/f58d923b9da10f0bb50fa6137d1a1a70ef468a73f9cb68fbe5ec8e9c01d82343/analysis/ it has PE header:

Required OS version 5.01 Image version 0.00 Subsystem version 5.01

You need:

Required OS version 5.01 Image version 0.00 Subsystem version 5.00

ref: http://blogs.msdn.com/b/astebner/archive/2007/10/17/5502005.aspx http://stackoverflow.com/questions/4866352/what-are-the-effects-of-the-pe-header-subsystem-field

mailsend v1.14 subsystem was 4.0 mailsend v.15b5 subsystem was 4.0 mailsend v1.16 subsystem was 5.01 If mailsend v.15b5 runs ok tweaking the subsystem version number maybe worth a try. A tweak with a hex editor may fix the issue. Most likely the defaults on the updated MS compiler uses for win32 compatibility just slipped that in because they can.

[jcjdominguez]

I can confirm that this bug is still present on 1.19 version, on windows xp and windows server 2003 (same kernel).

I wanted to run any version after 1.16 because the -log parameter.

@muquit Could you try to have a look, please? Maybe running windows xp on a virtual machine? At least, it should be quoted on the main page that newer versions don't work on old Windows versions.

Thank you very much.

I've downloaded the source code and also a C compiler for windows (codeblocks). If you explain me how to compile it, I'll do it for you.

[muquit]

Sorry I do not have access to Windows XP or Windows 2003. mailsend v1.19 is compiled on Windows 10. The Supplied Makefile.mnake is specific to Microsoft Visual Studio. If you can install some version of Microsoft Visual Studio, I will try to help on compiling. It is also possible to generate Makefile and compile if you install cygwin development environment (instructions are just like compiling on linux or Mac OS X). However, if you are not familiar with development, it can be frustrating.

[davesoft]

For those who hit a similar problem, here's a very very unadvised way to get it working on win2003. Open the exe in a hex editor, change symbol 333 from 06 to 04, then do the same for symbol 320 (from 06 to 04).

All praise to TekBear.

And, of course, don't do this in production ;)