Joined: 6/21/2006
Posts: 401
Location: Japan, Nagoya
Randil wrote:
I have no trouble watching addresses for any other games, though this is the only game I have with two blanks in the game title. Does anyone know how to fix this problem?
Yes, I have. Try the latest version (rev2.1), it will work well :P
Joined: 4/20/2005
Posts: 2160
Location: Norrköping, Sweden
I was scanning my computer for viruses with my anti-virus program AVG today, when it suddenly told me that there were trojans in both vbawatch.exe and vbxwatch.exe! The name of the trojan was "Trojan horse Proxy.SQU". I took a printscreen of what AVG says about the trojan, here it is.
And I didn't find any more of these trojans on my computer so i don't think it's anything that has spread fom another file. In any way, it's probably important to look up.
To find those addresses, you need to decompress and disassemble the executable. We can download the source code of the emulator, so finding them is not very difficult.
GBA: searching a string like "vbaIRAM", or MapViewOfFile call will help.
GBx: searching 0xfe00, "shr e?x, 12", or "and e?x, 0x0fff" may help.
I can't get this memory watch to work, I tried both Metroid Fusion and Zero mission (both of which where already in the config file) but it won't display any of the addresses. I have version 19.3 of VBA.
EDIT: It runs fine with 20.0, but I don't want to use that emulator due to desynch issues.
Joined: 11/18/2006
Posts: 2426
Location: Back where I belong
I'm working on a GBx game, and during a memory search I come across two types of addresses in VBAs built in search function:
One type looks like this:
00:c20e
00:c250
And the other type looks like this:
01:c154
01:ca28
01:cf2e
In VBA watch, inputting an address from the first type of sequence (ie c20e and c250), works exactly as they should, displaying the desired memory address. However, the sequences with a prefix of "01" do not display the same address as seen in VBA cheat search. Is there some special notation to use in VBA Watch to enable these different types of addresses?
Uhm, I still can't get the memory watcher to work on v19.3. Since it does work on v20.0 I assume that the errors lies in what is written in the target field in the vbawcnf0 file. So it'd be great if someone could just copypaste whatever it should say there from their own file and post it here.
To find those addresses, you need to decompress and disassemble the executable. We can download the source code of the emulator, so finding them is not very difficult.
GBA: searching a string like "vbaIRAM", or MapViewOfFile call will help.
GBx: searching 0xfe00, "shr e?x, 12", or "and e?x, 0x0fff" may help.
Bumping this to hopefully get the addresses for the current version of VBA, 1.7.2, v21. I don't know how to go about finding them since I don't know about how to disassemble the .exe or where to find this information in the source code. :(
To find those addresses, you need to decompress and disassemble the executable. We can download the source code of the emulator, so finding them is not very difficult.
GBA: searching a string like "vbaIRAM", or MapViewOfFile call will help.
GBx: searching 0xfe00, "shr e?x, 12", or "and e?x, 0x0fff" may help.
Bumping this to hopefully get the addresses for the current version of VBA, 1.7.2, v21. I don't know how to go about finding them since I don't know about how to disassemble the .exe or where to find this information in the source code. :(
I think there're something like ""Copy memory addresses for VBAWatch" under the "Tools" menu in v21. However, you should use at least the svn r85 then. It fixed some bugs related to the very VBAWatch/VBxWatch strings that missed CR (0xD) before the newline characters, which caused VBAWatch/VBxWatch to fail.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
