2009-10-07, 09:16 AM
(2009-05-06, 10:33 PM)Holy Diver link Wrote: The dumped file will be over 150MBs, so only try this if you're machine is pretty hearty. Now open it in your text editor, and go to the SoM data segment (Just look for Holy in the text, and page up a little ways until you see something like 0000 0000 f037 4000. That is where the initialized data segment officially starts for the record (theoretically it's possible these values might've been changed in your dump -- whatever they're used for, but not likely)
For the record I noticed that the f037 bytes change (apparently depending on the game/project)
Sorry if that actually confused anyone
Good news is I have access to the memory now. Only took probably a long 8hrs, but I learned some stuff along the way, so.
I think before jumping whole hog into mapping values to memory, I'm going to see if I can't figure out enough about DX to add a text overlay to SOM, so we can draw the contents of the memory on the screen, so you can see it as it changes/page thru it. Probably most of the interesting parameters will be grouped together, so if you can see the memory changing on screen, it might only take minutes to work out what is what
If not a text overlay, at least I can make a separate window to write or draw to somehow
