Protection of x86 dll can be done with any version of Enigma , I'm talking about ability to set code markers for protection of pieces of code using EP_Marker function, like in example I posted above. If you wish to use version 6.80, you can set markers using .inc files. Check Examples folder to vie...

thanks a lot
Examples folder are for VB and Delphi while developer is using VC. how do I guide developers?

Hi Enigma
I want to use this technology in both of my dll that are x86 and x64 . Is it possible?

Instruction set in this technology is RISC .Does not this particular type of instruction set facilitate reverse engineering ?

thanks alot.
I am using v6.8 .Are x86 dlls compatible in the my version?

how to verify out put of protected dll ? by using tools such as IDA pro, Is it correct ?

Hi both of them but more x86.
your virtual machine technology is just for 64bit DLL , SO I can use just protected string for 32 bit dll, right?

Thank you. Is it applied to my C++ SDK, we send it as a DLL for customer app .

Yes .
I thought anti-debugging was a common way to prevent reverse engineering, so I have to think about other obfuscation techniques, such as string encryption. right?

thanks for reply

Shouldn't the dll debug be prevented instead of customer's app debug ? Now customer's app that call protected dll can not be debug!!we just want not to patched our DLL by attacker.

more info: my protected dll is in release mode and customer's app is in debug mode.

hello I have a DLL which has protected just anti debugger in two versions of Enigma protector . when my sample app with that DLL debugged in Visual studio , we have two different out put: 1- in 4.30 version, my sample app debugged without problem!!! ( Unlike my expectation) 2-in v6.80 and v7.0 demo ...