NESDev and Strangulation Records messageboards
Forum Index | FAQ | New User | Login | Search

Previous ThreadView All ThreadsNext ThreadShow in Flat Mode*


SubjectRe: help understanding code  
Posted byAnonymous
Posted on8/1/04 1:38 PM
From IP213.150.147.93  



"...since I recall a convo on these boards about a game (using MMC1) which relied on this behavior. I wish I could remember the name of the game and/or find the thread though."
The game was "Bill & Ted's excellent video adventure" or something like that. And it didn't rely on this in-between-write-back, it got screwed up because of it. There are other games just like it, if I was at home right now I could give you a list... :)

FCEu had a "too fast write" hack that prevented the MMC1 from getting screwed up on these RMW reg writes, whereas some other guy used another hack where he resetted the bit counter every time a new MMC1 reg was written to (works for all games, since it would be good programming practice to write 5 consecutive bits to the same reg)

Anyway, this writing back of unmodified values bugs me too, but it seems like that's the way it works... But I still can't figure out how the MMC1 doesn't get screwed on a real NES.



-
Entire Thread
Subject  Posted byPosted On
*help understanding code  Anonymous7/30/04 6:02 PM
.*Re: help understanding code  Eshin7/30/04 7:00 PM
.*Re: help understanding code  Disch7/30/04 6:45 PM
..*Re: help understanding code  koitsu7/31/04 2:51 PM
...*Re: help understanding code  Disch7/31/04 5:49 PM
.....Re: help understanding code  Anonymous8/1/04 1:38 PM
...*Re: help understanding code  Anonymous7/31/04 5:43 PM
....*Re: help understanding code  koitsu8/1/04 09:44 AM
.....*6502 vs. 65C02  tepples8/1/04 3:27 PM
......*Re: 6502 vs. 65C02  koitsu8/1/04 4:47 PM
.....*Re: help understanding code  blargg8/1/04 1:17 PM
......*Re: help understanding code  koitsu8/1/04 4:45 PM
Jump to

Memblers' homepage             Contact Me

Forums powered by WWWThreads Demo