ControlSum check not working for 64-bit DLL
Posted: Sat Feb 02, 2013 5:12 am
Hi,
I am attempting to protect a 64-bit DLL. The problem is that the ControlSum option does not work when applied to the list of protection options. When I run a test app, I get my custom message that the DLL was corrupted. When I remove the ControlSum option, the DLL loads correctly.
I am using Enigma x64 version 3.120. The DLL is not a .NET or special plug-in DLL, it is a "normal", vanilla DLL with 'C' exported functions. The language used to create the DLL is C++ (so no C# or some other frameworked language being an issue). There is no manifest in the DLL, so that isn't an issue.
The amount of protection I'm using is minimal. Just a BMP splash screen on startup, anti-debugger option, the resource protection, 2 vm markers, and the controlsum check (which doesn't work). No other options are set/checked.
I am using Windows 7 64-bit Ultimate, SP1 for testing. Any issues with 3.120 and the ControlSum option together with these other options?
Thanks.
I am attempting to protect a 64-bit DLL. The problem is that the ControlSum option does not work when applied to the list of protection options. When I run a test app, I get my custom message that the DLL was corrupted. When I remove the ControlSum option, the DLL loads correctly.
I am using Enigma x64 version 3.120. The DLL is not a .NET or special plug-in DLL, it is a "normal", vanilla DLL with 'C' exported functions. The language used to create the DLL is C++ (so no C# or some other frameworked language being an issue). There is no manifest in the DLL, so that isn't an issue.
The amount of protection I'm using is minimal. Just a BMP splash screen on startup, anti-debugger option, the resource protection, 2 vm markers, and the controlsum check (which doesn't work). No other options are set/checked.
I am using Windows 7 64-bit Ultimate, SP1 for testing. Any issues with 3.120 and the ControlSum option together with these other options?
Thanks.