![]() |
|
|
|
#1
|
||||
|
||||
|
Quote:
Quote:
http://forum.exetools.com/showthread.php?t=8457 I couldn't solve the problem on my WinXP SP1 ! ![]() Can you attach your packed notepad.exe? Did you test script on detached child process or on father process? But thanks, I chaned patching routine to your method (previous method is working too !) ![]() Script is updated. Download it from first post Last edited by Newbie_Cracker; 01-27-2006 at 02:40. |
|
#2
|
||||
|
||||
|
Quote:
__________________
UpK һ�����ꡭ����ƽ��! http://www.unpack.cn |
|
#3
|
||||
|
||||
|
Finally I fixed it. But I was compelled to remove logging of import addresses. Doing manual steps, as in first script, is only solution to log the addresses. Logging is necessary in case of CopyMem-II & Import Elimination.
![]() Now it's compatible with all versions of Armadillo (as I tested). As I see, logging and stopping at oep is not possible in Arma 4.4 by using current version of script plugins. Only one of them is applicable ! Maybe there is a little bug in OllyScript and ODBGScript. Stepping the script using ODBGScript window, gives a fully working script, but running it, causes troubles ! I've a question : Logging import addresses is more important, or stopping at OEP? If first, I can change script to stop after fixing and logging imports, then user should put bp on CreateThread and find CALL OEP, manually, or use a 2nd script. Which one is better? PS: I devided first script in two scripts : 1- Import Redirection Fixer 2- OEP Finder They work perfect ! Last edited by Newbie_Cracker; 01-28-2006 at 05:56. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|