If you forgot what values you are looking for, read this thread again.
I forgot those were there. My bad.
When setting the breakpoint you write 2001-2001 in the address range. I don't know how you got 2007 there.
I know what I did wrong here. I had 2001-unspecified instead of 2001-2001.
He doesn't need to write 2001 in both fields if it's not a range (but it will work anyway even if he uses range for a single address).
...Or maybe I don't know what I did wrong there. So 2001-unspecified probably wasn't the problem?
I just tested it, and 2001-2001 still gives PPU_Data breaks. Definitely not the problem.
You should read more about how bytes and bits work.
I did do a little research on bits/bytes, but didn't catch much of it due to lack of time. What you've said helps a lot though. Now I've got a much better idea of where to start researching, and where to go from there.
Now that's I've got a breakpoint with the address set to 2001-2001, with write and CPU memory selected, the game freezes.
Sometimes clicking 'run' will make at least change where it breaks and the A value (I assume it also makes the game run, but stops again before it's noticeable). Then it invariably gets caught on A=88.
This particular 88 and it's line are identical to that of the non-green ROM.
The values that happen before it aren't between #40-#7F or #C0-#FF.
Specifically they are 00, 1e, 18, and 88.
So I went back to the conditions that were discussed a while ago. I found that any inclusion of 'W' in a condition makes it invalid. When using the variant with A's it never breaks. When I initially tried the conditions I had the same results, but figured I'd just go without them.
However, when I have the A variant of the condition the game doesn't freeze.
I'd try to be more thorough before posting this, but I'm rather short on time again. Sorry if that's a problem.