i've compiled it on windows7 32 bit
it must be worked!
why it can't be executed?
i'm going to search and tell you!
i've compiled it on windows7 32 bit
it must be worked!
why it can't be executed?
i'm going to search and tell you!
go to the control panel,
select user accounts,
then select change user account control settings
after that you see a slider
turn it to 0% and press OK
when asked a question, select yes and press OK in all of the dialogs that happens and close control panel
I feel like running a random exe that requires UAC to be disabled is a terribly unsafe thing to do.
While I agree with Jake that you must not require the users to disable UAC in order to run your software, I trust that you haven't provided any malicious software and did try it with UAC turned off. However, the result is the same after telling Windows to execute the application even though the supplier is unknown Windows gives me the error that the application cannot be executed on this PC without any further detail about why.
I had a quick look at the exe - coz I'm so nosey and enjoy mystery .exe's it's a legit PE, I didn't check for any nasties but it's:
"Allegro Game Creator"
uses:
OpenAL
wxWidgets
OpenGL
some GCC stuff
and a few more
probably doesn't load because it uses a few .dlls
libgcc_s_dw2-1.dll
libgcj-13.dll
and it does have that function above in there:
what should i do now?
i read all of them, but it didn't worked!
thank's shabronic for the information, but i don't know how to fix it!
i dis-assembled it, but nothing happens and i don't found the problem
now see that!:
i can write an operating system, but this application make's me very snappish
please help: i'm losing my eyesight for that!
Windows used to give more information about why an application doesn't run. Especially when it is because of a missing dll. Perhaps Microsoft decided to remove this error reporting in Windows 8 due to confusing the average user. I wonder if there is a way to turn on the detailed error reporting for us developers? I'll see if I can find something.
Anyway, I'll try downloading the dlls that shabtronics mentioned and see if that helps.
I downloaded Dependency Walker to see if there were any other missing dlls.
The dlls that are missing seems to be from Microsoft. My guess is that you're using a different version of the Platform SDK than what I have installed.
What version of the Platform SDK is it that you're using?
No, that had nothing to do with the problem. I ran dependency walker on my own application BMFont, and it reports the same missing dlls, yet my application runs normally.
There is something in AGC.exe that prevents it from running. Could it have been corrupted, e.g. by ftp as text, in the upload to your site? Have you tried downloading the executable and running it on your own machine?
I think that posting your executable for debugging should really be a last resort when you're trying to get help like this.
You should really try to create a minimal program that demonstrates the essential problem. Check out a fresh working copy from version control, or copy your project's source if you're not using version control (hint: you should definitely be using version control). Start by removing third party code, and keep removing more and more code while checking that the application continues to reproduce the unwanted behaviour. Try to avoid any external dependencies, for example, try putting the script source code in a string rather than an external file (presuming Angelcode supports reading a string directly).
Stop when the behaviour does, or when there is no more code to take away.
Sometimes, in the process of reducing the problem you will actually find the source and be able to solve it yourself. In such cases, it would be nice to reply with a note here, so that others experiencing similar issues know what to look out for. During this process, you might also find that trying to remove a piece of otherwise unrelated code also removes the behaviour. This may indicate trickier issues, such as invoking undefined behaviour, For example, somewhere you might be calling a member function on a null, uninitialised or deallocated pointer. If you find this, you at least can (probably) rule out Angelcode as the culprit.
Another possibility is that you end up with a relatively simple program, that fits in a single source file, with no external dependencies, that still shows the issue. Post the code to this program here, someone might be able to spot a mistake, or it could be used as a test case to demonstrate a bug in the library itself.