If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below. Also, before requesting
codes, note that there is a main site, which may contain what you
are looking for already. Also, if you know what you want, feel free to
search for it directly.
Can you add an option to ignore all results that fall on a 0,1,2,4,5,6,8,9,A,C,D,E address so you just get the results that fall on 3,7,B,F address when doing 8-Bit searches.
had a quick play with vers. 1.05 and it keeps on erroring when trying to dump internally from the chosen emulator (in the search tab) i alway's get this msg saying 'error dumping the process in memory'
is it possible to create an .ini file with this program that allows use to get renegade to working with other emulators ( like atari, cbm etc)
had a quick play with vers. 1.05 and it keeps on erroring when trying to dump internally from the chosen emulator (in the search tab) i alway's get this msg saying 'error dumping the process in memory'
is it possible to create an .ini file with this program that allows use to get renegade to working with other emulators ( like atari, cbm etc)
Huh. Whatever emulator you tried to dump probably isn't as static as I expected. For whatever reason, the game system RAM within an emulator can be loaded to different places on different machines/OSes. It can work all day long with any game loaded for me but will absolutely refuse to work for some people. You could try figuring out the starting point manually and update the preset. The readme has more info on doing that.
You can also set everything on the hook tab for a new emulator and hit Add Preset, as opposed to having to edit an INI. I haven't had a lot of luck finding the right part of the memory to dump with some of the older systems I've tried though. It's weird. Like I can find the start point on PCSX but not ePSXe. Makes no sense. I think I was also looking to do SNES9x or Gens something at one time too and failed.
Ok. LMZ and I got into this last night, and I think we finally figured out the issue with dumping No$GBA (0 results). The method I was using to autodetect the RAM was randomly picking up the ROM for some people, since the 12 bytes being checked appear at the start of both. I tweaked this a bit and had LMZ test it last night with success. Let me know how it works out.
I found a problem with v1.05.
I was searching for the 64-bit value 000002A000000048 but it was only found it in two places, I checked it in ps2dis using the pattern A002000048000000 and rex has missed the first two possibilities.
00409cc4 - Not found in rex
00409ebc - Not found in rex
005d4700 - found in rex
01fdfc38 - found in rex
I've attached the dump file for you to look at.
Also rex v1.06 only allows you to enter 13 digits instead of 16.
Dammit! These 64-bit integers are no fun. They don't work as well as 32-bit. I wonder if I ever tested reading in those I64s with scanf. The number of digits in the text box is more likely due to the size of the box than the actual maxlength setting, which should be an easy fix.
In any case, I may or may not have a quick fix. I found and fixed a problem with the In Range searches too, but I've started to rebuild Renegade for a 2.0 release. Maybe I'll go ahead and release 1.07 though.
Edit: Man. You had me worried for a minute. I know why it missed 2 addresses. Those other 2 addresses aren't 64-bit ALIGNED (they start on 4/C instead of 0/8).
Edit 2: I (hopefully) fixed the input issue and the In Range searches issue I had previously found. Dev-C++ project files are on longer in the rex source, but still in the Mupen one since I was too lazy to delete them. I use the regular makefile for MinGW now.
Another quick fix. The No$GBA hooking was working so long as the rom are in process memory was over 10 meg. I left it a little laxed before because the regular and debug versions had different size pages for ram in memory, and I wasn't sure if anything else effected that. It should work for both without the rom size side effect now. Kind of a rush release, since I'm in the middle of working on PS2CC. No need for the mupen build on this one anyway.
So your saying in order find 64-Bit addresses that fall on 4/C i'll have to do 32-Bit searches instead and just look for the other 32 bit address next to it with the correct value? there's no way to do unaligned 64-bit searches to narrow the results?
I did some tinkering with breakpoints in Mupen. Here's a source package with the EXE built. Breakpoints and watchpoints on read/write work. Registers view works, but do NOT try to view registers before a game is running or it'll shit the bed. http://viper.shadowflareindustries.c...2010-2125].rar
I was trying to think of something other than Turok to test it on, so....
For emulator called DEmul 0.5.6 Start of RAM is 2C000000 - tested in practice. Works on:
Sega Naomi 1/2
Sammy Atomiswave
Sega Dreamcast
Memory map: http://git.redump.net/cgit.cgi/mess/...rivers/naomi.c
3 0x0C000000 - 0x0CFFFFFF System Memory
3 0x0D000000 - 0x0DFFFFFF (Mirror on DC, Extra RAM on Naomi)
For Dreamcast RAM size is 16MB, Atomiswave & Naomi 1/2 RAM size 32Mb
Try this
Comment