Talk:INES Mapper 030

From NESdev Wiki
Jump to navigationJump to search

Board allocation

Study Hall definitely needs its own mapper, but why does BK:MoT need to be here? It's handled by the standard m2 emulator oversize logic... —Lidnariq (talk) 11:54, 8 April 2014 (MDT)

While it is true that BK:MoT can function with just the Mapper 2 oversize, the game was made on the board that Mapper 30 is defined for. Given that it exists on the UNROM 512 board, I do have some plans to make a convenience hack, where the games continue points write something to the flash, so that the game can be saved, resumed later, without needing to write down passwords. Modding that to real cart will just be a matter of desoldering the 4 flash locked jumnpers, soldering the flash enabled jumper, mounting the 74*139, and flashing the modified rom to the cart. Such a hack would definitely need the mapper 30 definition. Caitsith2 (talk) 12:15, 8 April 2014 (MDT)
So... you want to allocate mapper 30 for a BK2 hack you plan to make in the future? I don't think it's good practice to allocate mappers before there is something to be emulated that needs one. - Rainwarrior (talk)
Oh wait, I missed the comment about Study Hall. What are Study Hall's special requirements? Bankable CHR-RAM? - Rainwarrior (talk) 15:09, 8 April 2014 (MDT)
Ah, OK, I see from the UNROM 512 Talk Page this mapper would support several RetroUSB games? I misunderstood the discussion. Are there other such games that don't already fall into existing mappers, or is it just Study Hall? - Rainwarrior (talk)
Study Hall explicitly requires self-flashing support. —Lidnariq (talk) 15:41, 8 April 2014 (MDT)