Talk:NES 2.0: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(Created page with ':"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 ...') |
No edit summary |
||
| Line 1: | Line 1: | ||
:"Kevin Horton reports that Nintendulator supports NES 2.0." | :"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. --[[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) | |||
Revision as of 03:30, 5 January 2010
- "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)
