codezilla:
Number 1: I'm not your "buddy," I'm a Moderator here.
Number 2: You obviously do NOT have any idea what you are actually doing, otherwise you would understand that there has to be some routine
inside your target program which searches for the presence of a "debugger" (or at least the presence of Olly) and
after it makes that detection, it refuses to keep running.
Number 3: If you understood Number 2,
and if you knew how to actually USE a debugger (whether Sice or Olly) or had actually done some research on the issue of "debugger detection" and/or "anti-debugger routines" THEN you
might understand that your debugger can be used to actually FIND where your target is searching for the debugger and (gasp) bypass that effort!
Number 4: Instead of looking for THAT information
YOURSELF, YOU want someone to "tell you what tool or debugger" to use to solve "your" problem, when the answer is that you need to learn how a program detects "your" debugger and then actually "use
your debugger" to "catch the target attempting to do that and stop it from refusing to keep running.
Number 5: So, again, the answer to
YOUR question is
YOU need to spend some quality time learning "how debuggers are detected" and then "how to intercept the start of your target program" so YOU can attempt to actually WATCH it run through the routine which "detects" your debugger and "branches" to the point where it "refuses" to continue running.
Number 6: Somewhere "inside" your target, the program does a "test" for a "debugger" and if one is "detected" it "branches" to the "no go" routine or "debugger detected" message. YOUR job is to find that location and figure out "how" to "make" it take the "path" it would have followed IF "no debugger had been detected."
Number 7: There is already information on this Forum which discusses these issues and much information on the Net addressing these concepts.
Number 8:
OUR RULES oblige
YOU to
SEARCH for such information
YOURSELF,
BEFORE you "ask your question HERE."
Number 9: You, obviously, have
NOT done that.
Number 10: YOU need to do that
BEFORE you ask
any more questions and "THEN" come back and tell US what YOU have learned and what further help you might still need.
Hope I made it clear what
you "SHOULD" be looking for!!!
For example "debugger detection + olly" in goggle produced 744 entries; "anti-debugger + olly" produced 114 entries. There is already discussion of "debugger detection" in other Threads here. That's
WHY we have a SEARCH button.
Regards,