I'm not sure if anyone has completed the tutorial successfully but I am holding off on writing any more guides until I get feedback on the first one so I can better pick a good example (more advanced, easier, more about reading assembly, etc)
So please post feedback, even if its negative so that I know how to improve the documentation, I have some really neat stuff to write up, that I'm not sure if anyone would be interested in.. =)
im a little lost with the telnet part, i go into command prompt type telnet (xbox ip) but if im in a game it doesnt connect, and if i do it in evox than go into a game it disconnects. what am i doing wrong?
Tutorial is fine although theres one thing I wanted to ask, I was messing around with T3 and found the ammo and continues (didn't spot Kinsfan had done it already :-) )
But the life bar was a little more elusive..
In your tutorial you selected 3 values as being more likely candidates, what was the reasoning behind this before you knew the locations contents.
Normally its spits out vast lists of locations which request a check of but rarely contain a match, sometimes it spits out single locations which are obviously better choices.
Still usnure as to why the value command offers locations that don't match the exact data, unless its just monitoring locations that match the equiv increase or decrease in value regardless of the actual value they hold??
Originally posted by GNEW do i need a debug bios or somthing, anything special? i cant get on xbxo right now but ill try those settings later tonight and see if it works.
You need to have at leat Evox 3921 installed, I use 3935 myself.
Just go into the settings menu from the dashboard and set TSR to debug and IGR's to yes then run Tenet from the run part of the start menu, type o and the IP address of your Xbox while a game is running..
You should see the debugger then..Don't expect anything fancy tho :-)
I picked those locations by guessing, for some reason 90+% of the time I guess which one(s) to pay attention to when there are hundreds.. The reason some values come up that don't appear to match your search is because those values are changing in between when they were checked and when you looked, on most of them you can do a db on the address a couple of times and you will see that its changing while you db em..
Originally posted by dootdoo I picked those locations by guessing, for some reason 90+% of the time I guess which one(s) to pay attention to when there are hundreds.. The reason some values come up that don't appear to match your search is because those values are changing in between when they were checked and when you looked, on most of them you can do a db on the address a couple of times and you will see that its changing while you db em..
I did wonder if you knew the memory map so some locations would match but be places that are not usable or just screen ram etc..
Very good chance that this question has allready been answered....
But, as far as the telnetting to the Xbox is concerned, I have that down to a fine art. Huge cash in SSX3, Extra lives, yadda yadda... Question is, you refer to IDA Pro, however in the how-to it's said to "open IDA and click on a tab".... with what? Is this IDA for windows, or is there an XBOX version? Whats loaded into IDA? is this the .xbe we're loading into it, or the converted .exe?
Thats the only part I'm stuck on, the rest of the tute was awesome, really made it click for me - I'm looking forward to knowing what to do with the Ida thing so I can start training for the pal people
yes IDA Pro is for windows,and you are loadin the converted exe.The tab you click is the one that says "IDA View" but you may not have to click it because it is selected by default (well at least for me it is)
I've found that by Poking Addresses 000b6fcc - 000b6fcd with NOOP (90) I have unlimited ammo in NightFire. Now, when I write an .etm file (tried both - poking it regardless and having it check for 2c,c2) It doesnt seem to be affecting it at all. I've tried it with the TSR on normal, and on debug just for the hell of it as well.
I "Believe" I have the correct Timestamp and Title ID.
Size of Certificate : 0x000001DC
TimeDate Stamp : 0x3DBFB19D (Wed Oct 30 20:17:01 2002)
Title ID : 0x45410026
Title : L"007™: NightFire™"
Alternate Titles IDs : 0x00000000
Does this TSR only work with reasonably new Bios's? I've got RemoteX Version 3935.