If you are even able to apply my fix, then you are using really old VBA code. That's all I'm saying. That means go get the newer code first.
The newer code doesn't even resemble the old code well enough to apply the same fixes.
EDIT:
Okay, it looks like there are still lots of problems even with the newer source code, so things still need fixing.
The difference between the 2004 and 2006 version of VBA's GBC emulation is like night and day... If you still have the 2004 version of VBA, throw out its GB emulation code.
Amazing that the old version had such bad timing...
Anyway, I'm looking over the GB emulation code again...
Double check the HDMA code to see if it can ever go out of bounds either at source or destination. Using normal boundaries, the source address can not exceed the end of RAM, and the destination can not be outside of VRAM. Should make sure that the code never violates those rules.
lots of other checks... I wonder if it's possible to just remap the two pages so that they will always act as echo ram? But I think that would screw up the rest of the FFxx area.
Last edited by Dwedit; November 1st, 2007 at 11:32..
Reason: Automerged Doublepost