AutoIt3Wrapper weird compile problem

[Dr.Chi]

This is weird. If I make a script with wrapper commands, I can run autoit3wrapper.exe and it compiles fine. But if I then make changes to the au3 script, and try to make a new exe with autoit3wrapper.exe, it'll compile the Original script, not the changes I made and saved. I don't even know how this is possible. What ever changes I make is completely ignored. The original script isn't even there anymore, it's the saved script with the changes. But somehow autoit3wrapper is compiling the exe from some ghost of the original script.

crazy.

This occurs if I use wrapper command line or gui. The first iteration of my script compiles fine, but following changes are ignored.

[Dr.Chi]

Still an issue, but I found a temp fix. Seems the compile issue exists if when you delete the .exe file (to compile a new one) you let it go to recycle bin. If you instead Shift-Del (skip recycle bin) it'll compile just fine, with changes.

I've never seen a program do that, it's crazy.

[dantay9]

You are going to have to post your full script and describe exactly what buttons you press so the issue can be reproduced. Unless someone has already had this problem, you aren't going to get an answer without a reproduceable issue.

[Dr.Chi]

You are going to have to post your full script and describe exactly what buttons you press so the issue can be reproduced. Unless someone has already had this problem, you aren't going to get an answer without a reproduceable issue.

After a lot of testing, this is how to easily replicate it.

In Windows (I'm XP with all SPs and Updates)

1. Create an autoit script (.au3), any script will do, the actual contents of the script is irrelevant here.

2. Add these descriptors to the top of your script:

#AutoIt3Wrapper_useupx=n
#AutoIt3Wrapper_Res_SaveSource=Y
#AutoIt3Wrapper_run_after="d:\program files\Autoit3\Aut2Exe\upx.exe" --best --compress-resources=0 "%out%"

3. Compile it with AutoIt3Wrapper.exe

4. Check the file with ResHack, look at the source code. Looks right.

Then...

5. Delete the .exe (send to recycle bin, not Shift-Delete!)

6. Now change anything in the script, put a crazy comment or whatever it doesn't matter, then save it (same original filename).

7. redo step #3 to recompile another .exe file.

8. Check the source code with ResHack again, and there's the problem. You'll see the original source, not the changes. The script will even execute as the original, not the new changed one.

But, if in step #5 you either A.) skip the recycle bin via a shift-delete, or B.) rename your source file, you will not have the problem at all.

The actual script doesn't matter, but here's the test script I'm using:

#AutoIt3Wrapper_useupx=n
#AutoIt3Wrapper_Res_SaveSource=Y
#AutoIt3Wrapper_run_after="d:\program files\Autoit3\Aut2Exe\upx.exe" --best --compress-resources=0 "%out%"
;   
;Script Below
;

MsgBox(0, "Test", "test")

[dantay9]

I'm not getting this problem. It recompiles fine for me. One thing i see is instead of running upx afterwards, just compile it with upx. Maybe Jon can help out.

Edited July 16, 2009 by dantay9

[Melba23]

Dr.Chi,

I have just followed your instructions to the letter using your script and cannot reproduce the error. The included script is always the one I have just saved and compiled, whether I am running 3.3.0.0 or Beta 3.3.1.1. I am on Vista HP SP2.

Sorry I cannot throw any more light on it - must be something on your system.

M23

[Dr.Chi]

Dr.Chi,

I have just followed your instructions to the letter using your script and cannot reproduce the error. The included script is always the one I have just saved and compiled, whether I am running 3.3.0.0 or Beta 3.3.1.1. I am on Vista HP SP2.

Sorry I cannot throw any more light on it - must be something on your system.

M23

Weird, but maybe so.

I've got a good/easy workaround for now, so I'll not worry much about it unless it becomes a larger issue.

Thanks!

[Dr.Chi]

I'm not getting this problem. It recompiles fine for me. One thing i see is instead of running upx afterwards, just compile it with upx. Maybe Jon can help out.

The reason it runs afterwords is because without the "compress-resources=0" you can't read the source code without doing a manual UPX -d on the exe first.