>>Hi ALL !
>>The large commercial project has approached to completion. Many corporations have addressed behind the demonstration version of the program. But how to protect the program from decompiling if REFOX produces all initial text of the program (In Russia it is very urgent) :((((
>>Prompt possible ways of protection.
>>I in a shock...
>>Thanks
>Denis,
>When code is decompiled the real problem is not changing protection code but setting environment what protection waits. A hardware key such as Hasp seem to be a necessity to prevent that besides software protection. Decompiled code (by Refox) is fortunately has many logical errors :) I say that because for an old app I lost the source code and requested it to be refoxed. The refoxed code (while I know what I was doing in code), wasted my one week to correct the parts in wrongly decompiled code (recompilation after decompilation seem to give same size compiled code but only the size is same :). If I didn't know the logic, I think I would prefer writing it from scratch.
>I'm trying the Hasp key, it has a secondary protection for the exe and I think it will be good. Besides hardware protection, I have included many traps and software protection in addition. Yet it doesn't mean they can't be passed I know. A contract with the buyer would be another level of protection I think.
>Since I know there are very good crackers in Russia like here in Turkey, I can understand you. Hope one day we will be lucky to thrust to law in protection :)
>Cetin

Hi Cetin
Thanks for your reply.
The danger consists that hacker can make from Demo of the version the working version (Having expanded functionality of the program) having removed naturally all some keys from main.prg. I believe, that it will be uneasy to delete these lines of the code... Or on other them to process not getting inside of the application and not understanding in its logic... And further again to construct exe file.
Denis