I have seen a lot of xtrap remover apps here. What I would like to know is the following:
1.. What is it exactly that you search for in the game exe?
2.. Once found, how is it disabled?
That should be enough to scramble my brains for a qhile:laugh:
Printable View
I have seen a lot of xtrap remover apps here. What I would like to know is the following:
1.. What is it exactly that you search for in the game exe?
2.. Once found, how is it disabled?
That should be enough to scramble my brains for a qhile:laugh:
I had thought I was about the last to know. Been thinking about making this thread into a guide for newcomers though.
That is how I learned it... It's not actually hard, but the "remover" apps, only really work as well as the patches I released a while ago for the official clients at that time. That is, they are pretty specific to a small group of clients.
Thanks for that link..I dont know why it didnt show up in my searches
looks like I have some trial and error testing ahead...I hust got clinet version 2.40.8 from KPT and want to eliminate xtrap from it.
Note that the method normally used, discussed there, and implemented in the XTrap removers, does not actually "remove" XTrap code from the client... rather, it removes XTrap dependency.
What's the difference? Well, for one thing, it leaves a load of XTrap code in the client doing nothing. That would make nice little holes for new routines. For another thing, it will still use XTrap files if they are available, it just doesn't complain if they're not there any more.
well I found the offset for the extrap and put in the C3 90 ( nop retn)
it stll wont execute must be another problem I dont know about..back to the drawing boards
I've had similar results with the Chinese and Vietnamese versions... They use XTrap + one other exe protection. I think (IMS) it was one of the usual GameGuard / NProtect type ones... but I didn't start RCEing PT till after ePT dropped GameGuard and NProtect in favour of XTrap.
Having said that... there may be more too it that even that, I wasn't that desperate to find out.
Hmmm never gave that a thoght, but very possible indeed.
I only wish my MASM skills were better..like Peterr Norton...i wish. Well I guess this goes on the back burner.
I don't get it.:blink:Quote:
Assembly language programming is an extravagant waste of human talent and should be avoided whenever possible
(Peter Norton 1983)
Hi!Can you tell me how to be GM with PTV offline?
Easy... follow me :ott1:Quote:
Originally Posted by tangodown
I use the updated game from EPT
http://img199.imageshack.us/img199/7376/olly.th.png
If you don't found the offset, try searching the sequence
NOP
Push 0
Very easy, isn't it?
Then, fill up with some nops, till the RETN, like this:
http://img377.imageshack.us/img377/8514/olly2.th.png
So in RETN line, change to ADD BL,AL.
Look, you should have something like that:
http://img444.imageshack.us/img444/4425/olly3.th.png
Unfortunately, this game has a quite difficult bug, that you can't log as GM. The Hotuk is there, all is there, nothing too different... But you can't log :$:
And I don't know why you need to do like this to disable the xtrap, but I know that work... :blush:
Sorry if I missed something, my english isn't too good...
PS.: Sorry if in the bobs' link has the same answer, but I can't see it, I don't know why the posts aren't appearing... :closedeyes:
Nope... My initial method was just to replace the first line with a RETN, then from there I go around cleaning out all the rest of XTrap.
And yes, the no Admin mode is a pain, but I'm confident I will get it back, one way or another.
I think I missed something...Upon finding the push 0 followed by the call to getcurrentprocess, I did notice about 5 other address references to that call, my assumption is that they also need to be disabled,,,right or wrong?
Depends. The method used to close the program if XTrap is not available is very much like the basic routine you would write to "exit cleanly" in the event of an exception. A "handled exception" as opposed to the ones that cause the OS to take over and shut the process down it's self with an "Unhandled / Fatal Exception Error" message to the users.
This routine could be called from a number of error routines. Though there are a number of standard MSVC++ SEHs (Structured Exception Handlers) in the code, it's still common to catch errors and exit cleanly in your C++ project on top of the basic Stack, Heap, Divide by 0 and Integer out of bounds checks performed by the compiler.