Search found 12 matches
- Mon Nov 17, 2014 12:50 pm
- Forum: Basic
- Topic: Marker Errors
- Replies: 0
- Views: 15920
Marker Errors
Hello, I'd like to basically request a little feature as follows. When protecting an exectutable and enigmaprotector comes across a marker error, for example, "Marker XXX can't be placed inside XXX", it's quite hard to find out where the error occurs. That's why I'd like to have a more det...
- Tue Jun 24, 2014 3:56 pm
- Forum: Problems
- Topic: OpenProcess fails.
- Replies: 3
- Views: 12339
Re: OpenProcess fails.
Okay, I'll provide an sample application as soon as I can. The problem is the RISC VM. Without protecting the code area with the RISC VM it works fine. I'll try to figure out what exactly causes the problem to provide you more detailed information. I hope this can speed up the patch. Generally, I ha...
- Mon Jun 23, 2014 7:10 pm
- Forum: Problems
- Topic: OpenProcess fails.
- Replies: 3
- Views: 12339
OpenProcess fails.
Hello, I've just spotted a problem. I am using OpenProcess to gain access to a secondary process my application needs, but somehow, ONLY when the file is protected, this call ALWAYS fails. Process ID is correct, and so is everything else. Without protection it works fine. I've tried pretty much ever...
- Mon May 05, 2014 5:57 pm
- Forum: Problems
- Topic: VM RISC markers not used when selecting "Classic VM"
- Replies: 3
- Views: 12427
Re: VM RISC markers not used when selecting "Classic VM"
Thank you for the update Enigma! Seems to be working now 
- Tue Apr 29, 2014 7:42 pm
- Forum: Problems
- Topic: VM RISC markers not used when selecting "Classic VM"
- Replies: 3
- Views: 12427
VM RISC markers not used when selecting "Classic VM"
Well, i am not 100% sure about this. I have about 20 VM RISC markers in my code, and no functions selected in the VM function selection. When I set the VM to Classic, the output file size is about 1.9 MB. When I set it to RISC VM, the output file size is somewhat about 9.5 MB, which is quite a diffe...
- Tue Apr 22, 2014 8:18 pm
- Forum: Problems
- Topic: Control Sum Checkup always fails after a few seconds
- Replies: 3
- Views: 14585
Re: Control Sum Checkup always fails after a few seconds
There's a bug in ollydbg which prevents ollydbg from jumping to the module entry if the dosheader is corrupt.
- Tue Apr 22, 2014 12:29 pm
- Forum: Problems
- Topic: RISC VM Takes really long to protect and more
- Replies: 10
- Views: 33337
Re: RISC VM Takes really long to protect and more
Thanks for you help!
Worked perfectly
Worked perfectly
- Tue Apr 22, 2014 12:23 pm
- Forum: Problems
- Topic: Control Sum Checkup always fails after a few seconds
- Replies: 3
- Views: 14585
Control Sum Checkup always fails after a few seconds
Hello everyone, I just got another problem with Enigma Protector 4.10. It seems like the control sum checkup fails always after about 8 seconds. The only change i make during runtime is deleting the module from the LIST_ENTRY32's ( to hide the module ) and I delete the DOS header. It does not matter...
- Tue Apr 22, 2014 11:57 am
- Forum: Problems
- Topic: RISC VM Takes really long to protect and more
- Replies: 10
- Views: 33337
Re: RISC VM Takes really long to protect and more
These options apply AFTER the application is protected, right?
But i am talking about the input file. So that i can see the real function names in the "select functions" window.
But i am talking about the input file. So that i can see the real function names in the "select functions" window.
- Tue Apr 22, 2014 11:48 am
- Forum: Problems
- Topic: RISC VM Takes really long to protect and more
- Replies: 10
- Views: 33337
Re: RISC VM Takes really long to protect and more
Okay sure.
But one more question. Is there any way engima could use the debug database files generated if you use the /DEBUG flag in the linker for function selecting?
Function names like 0x103A3D are quite unclear. IDA is using the .pdb files and shows the "real" function names.
But one more question. Is there any way engima could use the debug database files generated if you use the /DEBUG flag in the linker for function selecting?
Function names like 0x103A3D are quite unclear. IDA is using the .pdb files and shows the "real" function names.
