the 0x30-0x3f <-> 0xb0-0xbf are not the problem, nor it is the 0x20-0x2f <-> 0xa0-0xaf... we match bsnes behavior, so I guess we are safe (and I'm pretty sure I had double checked two years ago)

it is the interaction between "SRAM repeats" and our current saving/loading procedure which is a PITA to handle correctly...

been busy tonight, I'll try to get a fix tomorrow