Compile problem - after updateing SciTE components

[trancexx]

Beautiful. Now this:

;~ #pragma compile(icon, .\work_black.ico)
#pragma compile(out, .\Test_trancexx.exe)
;~ #pragma compile(x64, true) ; uncomment when you want x64

MsgBox(0, "", @AutoItExe)

[mLipok]

 

Beautiful. Now this:

;~ #pragma compile(icon, .\work_black.ico)
#pragma compile(out, .\Test_trancexx.exe)
;~ #pragma compile(x64, true) ; uncomment when you want x64

MsgBox(0, "", @AutoItExe)

 

MeesageBox

Aut2Exe Error

OK

Error: Unable to add resources.

L:TOOLsMacroWORK--ICONSTest_trancexx.exe

 

and again

When I uncomment

;~ #pragma compile(x64, true) ; uncomment when you want x64
 

everything is fine

[trancexx]

One more and we are hopefully done. Compile this:

;~ #pragma compile(icon, .\work_black.ico)
#pragma compile(out, .\Test_trancexx.exe)
;~ #pragma compile(x64, true) ; uncomment when you want x64

#NoTrayIcon
MsgBox(0, "", @AutoItExe)

[mLipok]

 

One more and we are hopefully done. Compile this:

;~ #pragma compile(icon, .\work_black.ico)
#pragma compile(out, .\Test_trancexx.exe)
;~ #pragma compile(x64, true) ; uncomment when you want x64

#NoTrayIcon
MsgBox(0, "", @AutoItExe)

 

MessageBox:

Aut2Exe Error

OK

Error: Unable to add resources.

L:TOOLsMacroWORK--ICONSTest_trancexx.exe

 

 

and again

 

When I uncomment

;~ #pragma compile(x64, true) ; uncomment when you want x64
 

everything is fine

[trancexx]

So that means three possible things happen. Either your AV deletes/blocks temporary .tmp file Aut3Exe uses as base module for the final executable or your system doesn't support resources updating on .tmp files. Third option is that Jon changed the res updating code so much that he broke it for some cases/users.

First option you can verify if you add exception to your AV regarding Aut2Exe and its working folder and for other two ask Jon. Send him PM, he likes that.

Edited August 26, 2013 by trancexx

[mLipok]

As for the anti-virus:

All I did today, were made with active such exclusions:

 

[trancexx]

You have to exclude C:UsersuserAppDataLocalAutoIt v3Aut2Exe directory.

[mLipok]

even if I add new exlusion "L:TOOLsMacroWORK--ICONS*.*"

results: still the same problem

But it dawned on me, I decided to do one more thing, which proved to be effective.

I disable Antyvirus

ps.

"Children do not do this at home"

[mLipok]

You have to exclude C:UsersuserAppDataLocalAutoIt v3Aut2Exe directory.

 

Edit: Szukalimy We looked everywhere but not here.

Of course helped.

Edited August 26, 2013 by mlipok

[mLipok]

Is this problem is described in the documentation?

I do not see it?

Maybe add it as a FAQ?

[mLipok]

Many thanks trancexx

I have not forgotten about my own signature.

I marked your statement as the best answer.

cheers!

 

remaining in gratitude

mlipok

[trancexx]

 

Edit: Szukalimy We looked everywhere but not here.

Of course helped.

 

That's very helpful information. It means current compiling algorithm should to be changed to avoid situations like this. It's only a matter of time before x64 gets blocked as well. And other AVs will follow very quickly.

What Jon needs to do is extract initial module to memory (not dump it on disk) adjust time-date stamps, recalculate checksums, write that to in-memory module and then write it to disk for further resource manipulation.

[mLipok]

ha ha ha

That's it?

 

I think, he's a super hero, cope with this task in the morning between the first and second breakfast.

 

.....

 

kidding

[mLipok]

But seriously

I saw that Jon was looking for this thread.

Probably it was curious.

 

 

and by the way

I'm glad I could help.

If you want to test, please PM me.

[mLipok]

ps.

Today I pay VAT, and do not have as good a humor as ever.

[trancexx]

 

ha ha ha

That's it?

 

I think, he's a super hero, cope with this task in the morning between the first and second breakfast.

 

.....

 

kidding

 

Yes, that's it! He's super hero. And I say that because he has nice words for me too. He is my super-hero.

[Jon]

That's very helpful information. It means current compiling algorithm should to be changed to avoid situations like this. It's only a matter of time before x64 gets blocked as well. And other AVs will follow very quickly.

What Jon needs to do is extract initial module to memory (not dump it on disk) adjust time-date stamps, recalculate checksums, write that to in-memory module and then write it to disk for further resource manipulation.

 

There's a couple of operations where the base interpreter is extracted to the temp location where there isn't a error check to see if the file actually got there so the error could be the file is blocked straight away or the file is block during a resource update. I've added another error pop for this scenario and also changed all the error messages to display the temp file name (rather than the final destination exe) if there is an error. So that should make it more obvious what directory should be excluded.

I've changed the extension of the temp exe to .exe as well, but I'm not sure it matters really. But it probably won't hurt.

I'd very much doubt that any AV would be relying on PE checksums/timestamps as part of their signatures, so I want to see what the additional error messages bring first before I even think about changing that process.

[trancexx]

I'd very much doubt that any AV would be relying on PE checksums/timestamps as part of their signatures, so I want to see what the additional error messages bring first before I even think about changing that process.

No they won't but different timestamp and checksum mean different SHA1 and different MD5, therefore unique signature.

If I would be AV developer the first thing I would do is calculate SHA1 of the PE file for the first x bytes up until the last IMAGE_SECTION_HEADER. That way I would know with high degree of certainty if I'm dealing with known malware.

[mLipok]

I remove exclusion C:UsersuserAppDataLocalAutoIt v3Aut2Exe

 

Testing:

AutoIt Version 3.3.9.20

;~ http://www.autoitscript.com/forum/topic/153816-compile-problem-after-updateing-scite-components/page-2#entry1111105
#pragma compile(icon, .\work_black.ico)
#pragma compile(out, .\Test_trancexx.exe)
;~ #pragma compile(x64, true) ; uncomment when you want x64

#NoTrayIcon
InputBox("", "")

using: "C:\Program Files (x86)\AutoIt3\Beta\Aut2ExeAut2exe.exe" 

 

Result: message box:

TITLE: Aut2Exe Error

TEXT:

OK

Error: Unable to add resources.

C:UsersuserAppDataLocalAutoIt v3Aut2ExeautB722.exe

[HHS]

I have the same problem with the actual production and beta versions.

Windows 7 x64 with GData Anti Virus.

I can disable GData but the problem is not resolved.