Sign in to follow this  
Followers 0
Peter Smick

Error: Unable to execute upx.exe to compress stub file

6 posts in this topic

I am new to this, but have an AutoIT script that had been compiling just fine (AutoIt v3.1.1). Today, I made a minor change to the script and got the above error when I tried to convert it to EXE. I have uninstalled and re-installed AutoIt, and get the same error.

On a second machine with AutoIT installed, the script compiles OK.

What might be wrong on my main machine? Any help would be wonderful.

Thanks.

Peter Smick

Share this post


Link to post
Share on other sites



Welcome Peter Smick

What is the error that you receive?

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

Welcome Peter Smick

What is the error that you receive?

Errr, probably the one in the topic title?

Peter, make sure there is a copy of upx.exe in the same folder as AutoItSC.bin and Aut2Exe.exe.

Edit: And perhaps make sure it's a valid application (It's a console application).

Edited by Valik

Share this post


Link to post
Share on other sites

#4 ·  Posted (edited)

Yeah, sorry about using the Subject line that way, I should have repeated it in the text. The error is "Unable to execute upx.exe to compress stub file."

Anyway, UPX.EXE is where it should be and it seems to be a valid file--I get the usage/syntax info when I run UPX straight from the command line--I assume that means it's valid.

Other thoughts?

Thanks again.

Peter.

Edited by Peter Smick

Share this post


Link to post
Share on other sites

Other thoughts?

Is your AV software detecting false positives ?

What is the size of AutoItSC.bin , aut2exe and upx.exe ?


Visit the SciTE4AutoIt3 Download page for the latest versions        Beta files                                                          Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

Well, you know what? The problem seems to have gone away. I just tried it again and it worked. So maybe it was just some underdone potato. The script being compiled creates something of a TSR, and it may have been that the destination file was still running in memory even though I had killed it in the Task Manager. We live and learn.

Thanks for such fast responses.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0