2010-08-07, 04:15 AM
Crud, the files do make a difference, but I guess I don't really understand this. With the same files DD's player data still ends up at a different place than DoM's. That might indicate section 13 is a heap page (dynamically allocated memory) in which case some factors might cause things to move around and be different from system to system. Which means addressing memory outside of the data section with fixed numbers won't be a viable option. The only interesting thing I know of in the data section is the counters. Of course there are probably also addresses into the heap in there which can be used to pin down where things are in the heap.
Somdb seems to be reliable about memory anyway no matter how simple or complex the project. It may just be the absence of some factors like intro stuff that makes it reliable. If somdb.exe proves more reliable its address space could be mapped into the runtime's dynamic space. Which is more intuitive sense most people would fiddle with memory when setting up their projects.
Anyway the picture has become more complicated.
Somdb seems to be reliable about memory anyway no matter how simple or complex the project. It may just be the absence of some factors like intro stuff that makes it reliable. If somdb.exe proves more reliable its address space could be mapped into the runtime's dynamic space. Which is more intuitive sense most people would fiddle with memory when setting up their projects.
Anyway the picture has become more complicated.