Unable to start EXE (?)

[WSinc]

It happened again....

This time I have included everything that was in the two project folders.

Also included the RSA3.EXE that was built, that it couldn't start.

Hope you can find something here - the program runs fine when it doesn't

hang after the build step.

Curious - are you able to run the EXE without a rebuild?

Well, it was in DEBUG config, so probably not - - -

[Steven_L_Intel1]

Interesting. I get "Not a valid Win32 application", but so far, can't see why. That it is a debug build is not an issue for me - I have all the DLLs and the total image size doesn't seem to be an issue. My theory is file corruption, but am not sure how I'd diagose that. I will look.

[Steven_L_Intel1]

Bill,

I'm left with the conclusion that something on your system is corrupting the executable. If I simply relink your existing objects, using the same linker and libraries you are, I get an executable that is oddly different. The things I note are:

- The size of initialized data in your EXE is reported as twice the size of mine, though the actual image sections for initialized data are the same

- A dump of the headers reports the entry point in my EXE to be _mainCRTStartup, but in yours it shows blank

- My EXE has a .rsrc image section of size 1B4 (hex) while yours is size zero (there should not be a zero-sized image section.)

This could be a virus, or it could be a hardware problem, or maybe something else. In any event it does not seem to be the compiler (since I can run the EXE I build by relinking your objects). Supporting this is your earlier comment that sometimes it works and sometimes it doesn't.

[WSinc]

Yes, I sometimes get that same message, even though it runs when it's in the same directory where I built it.

It's as if moving it around corrupts it somehow.

What happens when you build it in the release configuration?

[WSinc]

Perhaps so, but I still don't see why I can rebuild the same EXE and run it again with no problem.

If it was a hardware problem, then rebuilding the EXE would always give the same result.

But about 9 times out of 10, the EXE runs without any difficulty.

Plus - I don't experience any mysterious problems of this type when running other programs.

I did an experiment where I rebuilt the same EXE, and it checks against the problem EXE,

identically bit for bit. But - why would it be different?

I ran Spyware Doctor to check for viruses, and it couldn't find anything. I'm wondering if there is a new

virus that it wouldn't know about (?)

Can you suggest a way to find out what process (if any) is attaching the EXE when I try to run it?

This is where Remote Assist might turn something up, since it's in MY environment that the problem occurs.

[WSinc]

Just curious - Isn't that post "executable hangs in Windows 7" related to this problem?

[Steven_L_Intel1]

I very much doubt it. First of all, the symptoms are very different, and the Windows 7 hang issues are all QuickWin applications that hang on exit.