looks like it's almost imposible to protect the code.

Thanks for the info,
Javier.

>I haven't messed with that one in a while...but last time I played with it you could get passed it by using a debugger like NuMega's SoftICE.
>
>>How about armadillo?
>>
>>>There is a crack avail for that already. It would be tricky for someone to do it though if they didn't know you had used thinstall...problem is a cracker would know what was used becuase the message that pops up when you try to do a pdump.
>>>
>>>>I've tried Thinstall and works with VFP EXE's. They say that is uncrackable. I don't know if it's true (I don't believe it, but I didn't find a decompressor/decrypter for it either, so maybe IS true). Compress and protect .NET executables too.
>>>>http://thinstall.com/
>>>>And about security
>>>>http://thinstall.com/help/programsecurity.htm
>>>>
>>>>Dorin
>>>>
>>>>>>Anyone found a protection against ReFox?
>>>>>
>>>>>There is none.
>>>>>
>>>>>>Should servicepacks protect our code?
>>>>>
>>>>>They don't.
>>>>>
>>>>>
>>>>>>Ionut,
>>>>>>There is no protection against ReFox, except ReFox.
>>>>>
>>>>>Also known as 'extortion'. Even a VFP application branded with refox can still be decompiled though.
>>>>>
>>>>>
>>>>>>Decompilers work on VFP compiled code. If you purchase ReFox and use its "branding" option, ReFox will not decompile your code because it will respect the bytes inserted into your code base. However, this does not stop another decompiler from working on your code.
>>>>>>
>>>>>>In addition, Victor Anderson (sp?) has posted that he knows where the "branding" bytes are inserted and removing them with a simple hex editor defeats the branding altogether.
>>>>>
>>>>>>Bottom line is that there is no sure fire way to protect your VFP code from people that really want it.
>>>>>
>>>>>This is correct. About the only thing you can really do is to find some way to compress your .exe, so that it doesnt decompress until you run it (thus decompressing it in memory). Only thing is that even this won't completely protect you either. The makers of Refox have some other little gizmo called KONxiSE that does this. Problem is that once the .exe is decompressed in memory, you can do a memory dump and end up with the uncompressed .exe - then run refox or unfoxall or whatever on it.