[Release] Tool to prevent decompilation of your Autoit-Code

Thanks, Shadow for the confirmation :)
Hopefully you will have some sparetime to enhanced the protector to support FileInstall anytime soon :)

Quote:

Originally Posted by superman8855 Thanks, Shadow for the confirmation :) Hopefully you will have some sparetime to enhanced the protector to support FileInstall anytime soon :)

Had have a look at FileInstall.
There is a big problem I already know what the problem is and I also managed to solve problem by hand, but I really do not know how I should solve this by program... I do even not know if FileInstall will ever work probably.

Works fine! Thanks Shadow :)

The rapid appearance of the CMD black screen at the beginning of the execution of the the protected scripts is intentional?

can you remove the cmd at beginnig ?

#Updated
- Made Safe.exe better in protection and removed crashes
- Added FileInstall-Support
- CMD will now only appear if you select "CUI"
- Removed just some little Bugs

What?? FileInstall support?? Let me test it

Edit: just tried it, can't run. Error: "Please copy 'SecureAu3.exe' and 'Executor.exe' in the same directory as the script.

There is no Executor.exe in the download file, only Executor1.exe and Executor2.exe

Edit 2 : I rename "Executor2.exe" to "Executor.exe", now it works (hasn't test the FileInstall yet). Should I rename Executor2.exe or Executor1.exe ?

Edit 3: seems like executor1.exe is for CUI and executor2.exe is for GUI. So far the only glitch I found is this, need to test the FileInstall though

Quote:

Originally Posted by superman8855 What?? FileInstall support?? Let me test it Edit: just tried it, can't run. Error: "Please copy 'SecureAu3.exe' and 'Executor.exe' in the same directory as the script. There is no Executor.exe in the download file, only Executor1.exe and Executor2.exe Edit 2 : I rename "Executor2.exe" to "Executor.exe", now it works (hasn't test the FileInstall yet). Should I rename Executor2.exe or Executor1.exe ? Edit 3: seems like executor1.exe is for CUI and executor2.exe is for GUI. So far the only glitch I found is this, need to test the FileInstall though

Yes this is a little bug. Just rename in "Protecter.au3" the "FileExists" whre it asks for Executor.exe to "Executor1.exe" this will fix it. ;)

Quote:

Originally Posted by Shadow992 Yes this is a little bug. Just rename in "Protecter.au3" the "FileExists" whre it asks for Executor.exe to "Executor1.exe" this will fix it. ;)

Thank you, Shadow :)

FileInstall tested, it works great great great :handsdown:

This is the best version so far, and I could say it's PERFECT

The version 0.2.0 do not works for me. When I run the protected file, only apears a cmd window with "Press any key to continue". I used the Executor2, no CUI.

Shuaua, please download again the 0.2.0 version and replace line 853 on the protecter.au3 from:

If FileExists("SecureAu3.exe") = 1 And FileExists("Executor.exe") = 1 Then

become:

If FileExists("SecureAu3.exe") = 1 And FileExists("Executor1.exe") = 1 Then

Compile the protecter.au3 and run it. It should solve your problem.

Shadow: is it possible on next release the protecter accept command line (parameter)? Something like:

protecter.exe /source:i-want-to-protect-this-script.exe /auto1:s1.exe /auto2:s2.exe /auto3:s3.exe /output:secure-script.exe /cui /upx

That feature will save a lot of time and make it even more perfect

Quote:

Originally Posted by superman8855 Shuaua, please download again the 0.2.0 version and replace line 853 on the protecter.au3 from: If FileExists("SecureAu3.exe") = 1 And FileExists("Executor.exe") = 1 Then become: If FileExists("SecureAu3.exe") = 1 And FileExists("Executor1.exe") = 1 Then Compile the protecter.au3 and run it. It should solve your problem. Shadow: is it possible on next release the protecter accept command line (parameter)? Something like: protecter.exe /source:i-want-to-protect-this-script.exe /auto1:s1.exe /auto2:s2.exe /auto3:s3.exe /output:secure-script.exe /cui /upx That feature will save a lot of time and make it even more perfect

Of cause it is but I am away for around 7 day so it will take a little bit until i will be able to add something like that. ;)

Quote:

Originally Posted by Shadow992 Of cause it is but I am away for around 7 day so it will take a little bit until i will be able to add something like that. ;)

Great, thanks Shadow! :)

Have a nice holiday :)

Quote:

Originally Posted by superman8855 Shuaua, please download again the 0.2.0 version and replace line 853 on the protecter.au3 from: If FileExists("SecureAu3.exe") = 1 And FileExists("Executor.exe") = 1 Then become: If FileExists("SecureAu3.exe") = 1 And FileExists("Executor1.exe") = 1 Then Compile the protecter.au3 and run it. It should solve your problem.

Hi superman.

This is the same as renaming "Executor1.exe" or "Executor2.exe" to "Executor.exe", not? But I followed your instructions, changing the line 853, and the problem yet happens. The protected exe does not working, when I execute only shows a cmd "Press any key to continue".

I am using the Executor2.exe because I am not using CUI. I just raname it to Executor.exe. No error reported by SecureAU3 during the protection process.

Shuaua,
I dont remember which one is for CUI, is it executor2.exe or executor1.exe.
If you try with executor2.exe and it didn't work, please try executor1.exe

rename one of them to executor.exe and run the protector.exe

Good luck :)

Nothing :(

I tried all possibilities.
I need Shadow's help.
Thanks Superman.

Edit: The problem was incompatibility of SecureAU3 v0.2.0 with Windows 8. I used on Windows 7 and works! After protected, the files works in Windows 8 too:D

But if it's possible add compatibility, Shadow, with Windows 8, would be great.

Thanks.