Jump to content
Sign in to follow this  

Stupid noob question about protecting .exe's

Recommended Posts

I don't want people to undecompile my .exe. I know there's programs like obfuscator, but they say that you can't use lines like Call("") or HotKeySet in them, and well, that's all over my script. Anyone know of any protectors that can support the Call and HotKeySet functions? I don't care if it CAN be decompiled, I just want it to be harder than them doing it with the unprotected normal compiled script. Thanks

Share this post

Link to post
Share on other sites


If you are really serious about protecting your exes, you might like to look here. :)


Public_Domain.png.2d871819fcb9957cf44f4514551a2935.png Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind

Open spoiler to see my UDFs:


ArrayMultiColSort ---- Sort arrays on multiple columns
ChooseFileFolder ---- Single and multiple selections from specified path treeview listing
Date_Time_Convert -- Easily convert date/time formats, including the language used
ExtMsgBox --------- A highly customisable replacement for MsgBox
GUIExtender -------- Extend and retract multiple sections within a GUI
GUIFrame ---------- Subdivide GUIs into many adjustable frames
GUIListViewEx ------- Insert, delete, move, drag, sort, edit and colour ListView items
GUITreeViewEx ------ Check/clear parent and child checkboxes in a TreeView
Marquee ----------- Scrolling tickertape GUIs
NoFocusLines ------- Remove the dotted focus lines from buttons, sliders, radios and checkboxes
Notify ------------- Small notifications on the edge of the display
Scrollbars ----------Automatically sized scrollbars with a single command
StringSize ---------- Automatically size controls to fit text
Toast -------------- Small GUIs which pop out of the notification area


Share this post

Link to post
Share on other sites

With the best will in the world m8 you will never stop someone decompiling your exe, there is always a way.

You have to have a balance between enough to stop the casual cracker but not spending hundreds of hours coding to stop one person.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...