AutoCamo - 98.18b

[legend]

Hi Mobius

Great to see that your still working on autocamo is it possible I also can try your current build?:p

[Mobius]

Hi Legend, it's been a while

The last one I put out there was a debacle which I'm currently in the process of rectifying.

I will surely let you know when it is ready/released.

 

Edit: Just recieved another "it does nay do wot it sez on da tin" style pm's so I might make certain components that are currently optional no longer optional to subdue negative first impressions of first time users regardless of the AV attention this default mode will bring.

Unless there are any objections of course.

Edited March 29, 2017 by Mobius

[legend]

Hi Mobious, hope your doing good, yeah it's been a while  good to see your still around .

I can't wait  to try it your future release of camo  

[MyDream]

Let me know when a new version is ready, Keep up the good work.

[Mobius]

Will do guys, its on its way

Ed: Never mind its dead as.

Edited February 16, 2018 by Mobius

[Mobius]

Hi All,

It has been a while.

It is my belief that the defence of Autoit applications is pretty much a cold case these days but I have been away for some time and as such am out of touch with its development so could be mistaken.

If not would those that previously used this tool accept a console only/ command line (configuration file) driven alternative that is easier to maintain and much more powerful and modular than the gui tool I tried to release before (I suck at guI tools I know this now as I did then).

Also if the rules of engagement have changed on this forum (mods/devs) please let me know.

The only good thing that can come of the 2020 coof is the time to be productive

Stay safe y'all

Vlad

 

Edited October 5, 2020 by Mobius
Ed: grammar

[Ontosy]

It doesn't seem to work anymore in 3.3.15.3.

Console only/ command line is better.

 

Edited October 30, 2020 by Ontosy

[Mobius]

On 10/30/2020 at 7:03 AM, Ontosy said:

It doesn't seem to work anymore in 3.3.15.3.

Console only/ command line is better.

 

Hi,

When that build is released i'll be sure to check it out

[Ontosy]

It is released as beta.

 

[Mobius]

21 minutes ago, Ontosy said:

It is released as beta.

 

Excellent thanks.

Ed: Additionally the current build of AC can actually be used as a pure console program (log output goes to stdout) if you prefer, you do this by patching its pe subsystem.

Edited November 2, 2020 by Mobius
Additional info

[Mobius]

Ontosy,

I've just checked it and the a3x mods and package containers produce a working binary from the beta 3,3,15,3

Could you please explain what you mean by no longer works, I'd prefer we use this thread for discussion but if an explanation requires details that are frowned upon then you can pm me if you wish.

Vlad

[Ontosy]

2 hours ago, Mobius said:

Ed: Additionally the current build of AC can actually be used as a pure console program (log output goes to stdout) if you prefer, you do this by patching its pe subsystem.

I'm not undstand how to patch it?

1 hour ago, Mobius said:

Could you please explain what you mean by no longer works, I'd prefer we use this thread for discussion but if an explanation requires details that are frowned upon then you can pm me if you wish.

 

 

I have tested the file test.au3 with test.cfg.
When I use MPRESS enabled I get testPacked.exe (empty messagebox).
A3C.exe test.au3 test.cfg
When I use MPRESS disabled  I get test1.exe (Unable to open the script file).
A3C.exe test.au3 test.cfg
Not problem with release version.
If I use test.cfg with MPRESS enabled
A3C.exe ~SS test.au3 test.cfg
I get same that test1.exe but also without custom header and without compression.
The problem with header from command line I have also with release version.

I find a A3C_EEPJSVQCJWXLJ.exe in Aut2Exe folder.

The result is here.

Edited November 2, 2020 by Ontosy

[Mobius]

1 hour ago, Ontosy said:

I'm not undstand how to patch it?

 

I have tested the file test.au3 with test.cfg.
When I use MPRESS enabled I get testPacked.exe.
A3C.exe test.au3 test.cfg
When I use MPRESS disabled  I get test1.exe.
A3C.exe test.au3 test.cfg
Not problem with release version.
If I use test.cfg with MPRESS enabled
A3C.exe ~SS test.au3 test.cfg
I get same that test1.exe but also without custom header and without compression.
The problem with header from command line I have also with release version.

The result is here.

To patch ac to console by default  from the gui:

Click on the star toolbar button > execute - DRXL - Swap Autocamo interface

A console window should appear, close the autocamo window which closes the process allowing it to be patched, then press "Y" and enter as instructed in the console window.

Success or failure should be reported in the console, if everything went ok AC should now be a console program by default.

Ed: alternatively you can pop A3C.exe into a hex editor and at offset 220 flip the byte from 02 to 03 in the Pe header and save, if it does not work or you don't have DRXL.exe for some reason.

I am looking into your primary issue

 

Edited November 2, 2020 by Mobius
More info

[Mobius]

Ontosy,

Your primary problem is that you are running mpress before the build, this option should be reserved for older overlay dependent builds of Autoit. In your config file change the B at the end of the mpress execution line to A to tell it to run after the build.

You probably are already but if not you must use the most recent build of mpress 2.1.9 as older builds are known for corrupting 64 bit exes that are even the slightest bit abstract.

You don't really need to define aut2exe_x64.exe just aut2exe.exe when using the 64 bit interpreter  (gui) A3C_X64 (cfg) option since this option runs the builder with the /x64 command line switch when enabled. 

Hope this helps you.

Vlad

Edited November 2, 2020 by Mobius

[Ontosy]

59 minutes ago, Mobius said:

Your primary problem is that you are running mpress before the build, this option should be reserved for older overlay dependent builds of Autoit. In your config file change the B at the end of the mpress execution line to A to tell it to run after the build.

I have changed B to A, now it not compress target also if:

Created
k:\test.exe
<< A3C_LNXNKEDLFHRJB.bin >>
PE32+/x64 987.12kB -> 379.0kB  Ratio: 38.3%

 

Quote

You probably are already but if not you must use the most recent build of mpress 2.1.9 as older builds are known for corrupting 64 bit exes that are even the slightest bit abstract.

Yes, I use the last 2.1.9 version.

Quote

You don't really need to define aut2exe_x64.exe just aut2exe.exe when using the 64 bit interpreter  (gui) A3C_X64 (cfg) option since this option runs the builder with the /x64 command line switch when enabled. 

Also this not change the error result.

Do you have tested header missing when user A3C.exe ~SS test.au3 test.cfg ?

The AutoCamo not work for me with beta but work fine with same configuration in release: "Unable to open the script file".

I get every file as "A3C_BCLNTPDRCBEKC.exe" in Aut2Exe folder but not if I use A3C_A2E=@CMPD>Aut2exe.exe.

 

Edited November 2, 2020 by Ontosy

[Hao]

Can i get a new link for this version ? I can not download with this link. 😓

[Belini]

I would also like to test the latest version, does anyone have a download link?

[Mobius]

98.18b pretty old and no longer relevant these days.

Compiled and tested on windows 10 pro 64 bit under a virtual machine.

Baseline functionality tested with Autoit v3.3.15.4-beta only with distributed examples. This does not mean it will work with your advanced scripts since the resources example that uses a significant but older Autoit source header does not work correctly.

It is simpler to say this program is not compatible with 64 bit Autoit interpreters so avoid if that is a requirement.

The interface was sluggish as all hell to initialize for me under build/test os conditions so a reminder if you want to run it as a console program:

To patch it to console run

DRXL. exe A3C.exe @PB 3{220

To patch it to windows run

DRXL. exe A3C.exe @PB 2{220

Or you can use the interface menu option.

Or these batch files - a hex editor or script etc.

 

 

A3C_WINCON_BAT.zip

[Ontosy]

with

#include-once
Opt("MustDeclareVars", 1)
Opt("TrayIconDebug", 1)
Opt("TrayIconHide", 0)
;Const $My="by Alex Manti", $au3Base=StringLeft(@ScriptDir, StringLen(@ScriptDir)-StringInStr(@ScriptDir, "\"))
Dim $a='test',$b,$i

MsgBox(0,"Alx aaaa: " & @Error,$a)
;ClipPut($a)
ConsoleWrite($a)

I Get MessageBox

Quote

Unable to open the script file.

When I use also I Get a empty MessageBox.

[Mobius]

1 hour ago, Ontosy said:

with

#include-once
Opt("MustDeclareVars", 1)
Opt("TrayIconDebug", 1)
Opt("TrayIconHide", 0)
;Const $My="by Alex Manti", $au3Base=StringLeft(@ScriptDir, StringLen(@ScriptDir)-StringInStr(@ScriptDir, "\"))
Dim $a='test',$b,$i

MsgBox(0,"Alx aaaa: " & @Error,$a)
;ClipPut($a)
ConsoleWrite($a)

I Get MessageBox

When I use also I Get a empty MessageBox.

Don't know the cause your end but the same code my end generated the following working binaries:

test.exe just the source built

testapcc.exe as above but with apc option c checked.

Is your chosen autoit build in the program files directory or somewhere else that requires admin rights?

ONTOSY_test.7z

Edited October 9, 2021 by Mobius