You can use Reshacker for that purpose.Quote:
Is it possible to maintain the old icon and file properties after protect it?
[Only registered and activated users can see links. Click Here To Register...]
You can use Reshacker for that purpose.Quote:
Is it possible to maintain the old icon and file properties after protect it?
Will have a look at it, yes. ;)Quote:
@STORM: thanks :)
I know about Resources Hacker, but if we have many exe we want to protect and those exe files updated regulary, it will spend time.
In the protecter.exe, it will be great if before press "Start" button we can choose the ico file and at the same time can define FileVersion and Copyright information.
So if it's not possible to retain those information from the old exe file, is it possible to add 3 more inputbox to protecter.exe?
1 for ico file (#AutoIt3Wrapper_Icon)
1 for FileVersion (#AutoIt3Wrapper_Res_Fileversion)
1 for Copyright (#AutoIt3Wrapper_Res_LegalCopyright)
I just try ResHacker, it can change icon on the protected file, but could not change FileVersion and Copyright
Penner xDQuote:
doch, doch, hatte es auch direkt in Exe2Aut eingebaut, aber noch nicht hochgeladen :P
[Only registered and activated users can see links. Click Here To Register...]
Thank you very much, Shadow992 :)Quote:
Will have a look at it, yes. ;)
But at first I am working at a more secure version, which hopefully also makes it much harder for link who at the moment cracked my protection (but just by hand and he even did not write any program that could decompile it, but still if you are going to share some vulnerable texts/scripts wait for my next version).
Even dont know what these directives are for but i think it will be very hard to implement this.Quote:
Thank you very much, Shadow992 :)
Cant wait for your next version :)
Current protector.exe seems doesn't honor any directives, including command line (CUI) directive (#AutoIt3Wrapper_Change2CUI). It will be great if on the next version, it does support directives.
Thanks again! :handsdown:
This directive (#AutoIt3Wrapper_Change2CUI) is pretty common, it tell this script is a command line application, not GUI, so when we run it from command prompt, any output (including ConsoleWrite) will written to current command prompt (dos) window, it doesn't open a new window for it.Quote:
Even dont know what these directives are for but i think it will be very hard to implement this.
Ok this is possible to add but i have to look how i could do this. But i will have added it for sure in next version.Quote:
This directive (#AutoIt3Wrapper_Change2CUI) is pretty common, it tell this script is a command line application, not GUI, so when we run it from command prompt, any output (including ConsoleWrite) will written to current command prompt (dos) window, it doesn't open a new window for it.
In the protecer.exe GUI, you might want to add a checkbox "Is a CUI script". If checked, then compile it with #AutoIt3Wrapper_Change2CUI=y
:)
Das Design-Problem scheint etwas Windows/AutoIt spezifisches zu sein das lässt sich leider nur schwer ändern sorry.Quote:
Danke Shadow992 für das nützliche Tool.
Ich habe leider auch das von FlutterShy auf Seite 2 beschriebene Design-Problem - nur unter Windows 7.
Ansonsten hätte ich nur noch einen Makel: Die Dateien, die mit FileInstall installiert werden sollen, haben keinen Inhalt, sprich sind 0-KB-Dateien.
Klasse Arbeit aber auf jeden Fall ;)
Nockiro
Danke erstmal für die Antwort - sind ja alles keine so sehr großen Probleme.Quote:
Das Design-Problem scheint etwas Windows/AutoIt spezifisches zu sein das lässt sich leider nur schwer ändern sorry.
Das mit dem FileInstall hatte ich schon vermutet, werde mir das auch einmal anschaue ist nur die Frage ob ich das hinbekomme mal sehen.
Edit:
Erstmal steht jetzt aber Links Decompiler im Vordergrund und danach sehen wir weiter :D
Wird Zeit dass er mal die neue Datei hochlädt. :) Sonst kann ich sie ja net analysieren :D