new big problem!

[caliber1942]

finally got the retail version today (DVD version). haven't been able to play it online yet (home connection is 56K), but the office has DSL at least. anyways, i got the DEMO hacks to work with TAGS and MINIMAP. thanks to xollox, sparten, helios, pn3r, and many others who helped me along with that. turns out it was stupidity on my part and i had been working with the right addresses all along, just needed to press ENTER and enlarge the map and turn PAUSE off to see if it worked and i hadn't been doing that. imagine the JOY of finally getting the hack to work after 3 days of this-

anyways, imagine the DISAPPOINTMENT when i go to try my hand at hacking the retail version and alas, you can't ATTACH a DEBUGGER (neither TSEARCH nor OLLY) to the retail .exe because i guess it has anti-debugging to it.

How do i get around this. is there a helpful program or some sort of method to be able to debug the .exe?

Thanks in advance for your help!

best,
cal

[HelioS]

MPC doesn't really support what i'm about to say so check your PM.

[Ch3at3r]

MPC doesn't really support what i'm about to say so check your PM.
I think you may want to tell the other hard core coders here as well (e.g. Spontaneous) unless they also know how it works...

I also tried my luck with Olly and BF2 retail, but I also can't attach it... maybe you can give me some "hints" as well? :)

[Kosire]

[edited] Lets all just wait for Faldo's tutorial :)

[Sparten]

the reason that the exe cant be attached to olly(or any other debugger) is cause its allready being debugged. there is a trick to patch it so you can attach a debugger. i asked faldo if he would write a tutorial on how to do it and i guess he will post it soon.

[CaptainCox]

Okay just because this had to be said sometime, if were gonna have any hacks peeps will need to know how to attach a debugger.

My hint: use a different BF2.exe that has been patched to remove the protection.

Mod can edit this if it in any way broke rules.


Its on the border here man...
I know that alot of peeps are getting anoyed with this EXE not attaching prob, but please keep "THAT" solution to your selfs as its against the rules to talk about you know what here...please.

[faldo]

Problem solved:
http://www.mpcforum.com/showthread.php?t=96339

[caliber1942]

thanks to all, esp. HelioS and Faldo. Looking into it now. The support here for bf2 has been great. i hope i have helped others in some way, too-

edit: i have had alot of crashes trying the Faldo method. probably something other than just the thing he described is necessary or perhaps i don't have the exact offset for my version of windows (windows xp professional 2002 with sp2). however, it will get you some success if the game stays stable. hopefully there will be more input here. there are other ways around this (like modifying the .exe for singleplayer offline mode hacking). i bought the game, btw (which is why this is a problem in the first place).

best,
cal

[caliber1942]

thanks for the help with the debugging thing... i got things working now for retail.

ss below


http://www.savefile.com/filehost/files3.php?fid=8366861

couple tips with faldo's method and trying to debug (at least on my machine this was helpful- your results or experience may be different):

1) make sure when you run cheatengine that you do the thing with the read/write memory EACH time you run cheat engine or you may get a little window popping up errors.

2) doing the method for ATHLON seemed to work better for my Pentium (less crashes and such)

3) when searching for variables with TSearch, don't attach and do autohack until you already found the variable for sure. cuts down on game crashes. i guess the same for olly, don't attach it until you need it.

btw, i did get both tsearch autohack and olly working together (just tried it once though) but you might get occasional INT13 breakpoints and errors doing things this way (two debuggers at once).

hope this helped,
cal

[Spontaneous]

One thing that should be checked into is disabling the debugger in the first place. Granted you will have to use faldos method to debug to the point of finding out how to disable the debugger but then someone could write a trainer or what not to disable the debugger so people dont have these problems. I just got the DVD today so I will be starting on all my BF2 hacking this weekend.

[caliber1942]

the only problem there is if they turn on scanning of the .exe, then changes of the areas that do the debugger code will be detected and then they will likely kick and possibly even ban for that-

i would, however, like to learn how to defeat the debugging thing in bf2.exe so that i can mess around with the .exe offline with debuggers without having to do the faldo method (not sure if we should call it the faldo method? did he discover this or report how to do it first here?) anyways, some things to look at-

best,
cal

[Spontaneous]

They can scan the exe all they want, you should not be developing your cheats on PB servers anyways. You should only TEST your already developed cheats on PB servers.

Anyways, if you can figure out how to disable the games debugger by injecting code into it, ether by forcing a registers value to something else, NOPing, whatever, then you could just make a trainer that you can use before doing your own debugging. Or if it is possible by by doing a detour, do an inject on process start(could do a loader type system that starts the bf2.exe and injects right away) and then be able to do your own debugging.

I mean really, how do you think a patched .exe works? Its nothing but a memory injected code that is hardcoded into the .exe. So it must be possible using some kind of memory injection. Its just finding the way.

[snoochy]

congrats caliber, I have been staying up on the posts...You can breath now....But I have to ask.... what cave have u been living in, 56k at home I didn't think that was possible!!! Sorry I just had to rib u a bit, congrats anyway good job on the hack. and thanks for sparking alot of info in the forum...

[h4x0rz4lyfe]

When can we expect a realese?

[Alias777-v2]

When it's done. Don't beg. I'm sure hes spending every minute of every hour of every day on this hack ;) , so just sit tight.

[Spontaneous]

Who said anything about a release? Just because someone gets a hack working dont mean they will release it. So quit your begging and learn like the rest of us.

[caliber1942]

congrats caliber, I have been staying up on the posts...You can breath now....But I have to ask.... what cave have u been living in, 56k at home I didn't think that was possible!!! Sorry I just had to rib u a bit, congrats anyway good job on the hack. and thanks for sparking alot of info in the forum...

i live in a very small town (~12,000 people). my subdivision is still <1 year old and so there isn't any cable or dsl there yet.... however at work i have a very fast DSL connection.... sucks, but at home i don't get to mess around much anyways (sounds backwards, i know!) for people who have fast cable, just be happy...

and there won't be a release. the only releases i made in the previous bf games were for non-pb and tutorials (gave info on tmk trainer maker, dma, code caves, et.c). this won't be any different. i still feel the only way to try and keep your hack from being discovered is to learn how pb works, learn how to hack yourself, and keep your private hack to yourself. you CAN do this-

start with the demo and read up all the posts here and get the tools and start learning. grab the small program and tutorial in the battlefield general forum area and hack it like the tutorial says to get a feel for how to do this and then move on to the bf2 demo to get your hands wet.

this forum gets kinda mad at people asking for private hacks-

best,
cal

[ATI9800Pro]

Well i'll be siting tight thats for sure, i cant wait to test out what i seen in those screens. These really good fighter pilots are really annoying. It seems like they have hacks themselfs, cuz you cant get em off your back. When this is released ill give them something to dodge. :devious: