Talk:NES 2.0: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
No edit summary |
m (Another random observation, probably too late to be useful) |
||
| Line 2: | Line 2: | ||
No it doesn't - it '''detects''' them (and the mapper interface has room for them), but it doesn't actually read any of the fields. --[[User:Quietust|Quietust]] 01:58, 5 January 2010 (UTC) | No it doesn't - it '''detects''' them (and the mapper interface has room for them), but it doesn't actually read any of the fields. --[[User:Quietust|Quietust]] 01:58, 5 January 2010 (UTC) | ||
*...though ''now'' it at least handles larger ROM images (including "Super 8-in-1 99 King Fighter (Unl).nes", which should actually be Mapper 45 with 1MB PRG and 2MB CHR, but with the 256KB CHR blocks 0/1/2/3/4/5/6/7 rearranged to be 0/2/3/1/4/5/6/7). --[[User:Quietust|Quietust]] 03:30, 5 January 2010 (UTC) | *...though ''now'' it at least handles larger ROM images (including "Super 8-in-1 99 King Fighter (Unl).nes", which should actually be Mapper 45 with 1MB PRG and 2MB CHR, but with the 256KB CHR blocks 0/1/2/3/4/5/6/7 rearranged to be 0/2/3/1/4/5/6/7). --[[User:Quietust|Quietust]] 03:30, 5 January 2010 (UTC) | ||
An observation: it would've made more sense for the TV system byte to use bit 0 to mean "Supports NTSC" and bit 1 to mean "Supports PAL", since it would've made it trivial to support Dendy timing by just adding another bit. --[[User:Quietust|Quietust]] 04:52, 14 January 2011 (UTC) | |||
Revision as of 04:52, 14 January 2011
- "Kevin Horton reports that Nintendulator supports NES 2.0."
No it doesn't - it detects them (and the mapper interface has room for them), but it doesn't actually read any of the fields. --Quietust 01:58, 5 January 2010 (UTC)
- ...though now it at least handles larger ROM images (including "Super 8-in-1 99 King Fighter (Unl).nes", which should actually be Mapper 45 with 1MB PRG and 2MB CHR, but with the 256KB CHR blocks 0/1/2/3/4/5/6/7 rearranged to be 0/2/3/1/4/5/6/7). --Quietust 03:30, 5 January 2010 (UTC)
An observation: it would've made more sense for the TV system byte to use bit 0 to mean "Supports NTSC" and bit 1 to mean "Supports PAL", since it would've made it trivial to support Dendy timing by just adding another bit. --Quietust 04:52, 14 January 2011 (UTC)
