Q's about iNES mapper assignments

This is an archive of a topic from NESdev BBS, taken in mid-October 2019 before a server upgrade.
View original topic
Q's about iNES mapper assignments
by on (#14853)
Was anything ever assigned to mapper 14?

What are the mapper numbers that don't have anything assigned to them?

What's mapper 84, and why does the Kevtendo mapper status page mark it as a "poison mapper"?

[Reality check]
*running out of steam, will think of more questions later*
Sorry to bore you with all these questions which I might be able to answer by looking at the iNES website. I'm not developing an emulator; I'm just curious. I *know* that the Kevtendo mapper status page isn't fully updated, so I shouldn't be picking on it too much. Oh well. Now for the really important question:
[/Reality check]


The PC10 version of Mike Tyson's Punch-Out!! seems to use a MMC2 variant that has battery-backed WRAM. Since regular MMC2 doesn't have that, perhaps it is necessary to assign a new mapper number or UNIF board to this game? (Nestopia runs the existing "Mike Tyson's Punch-Out!! (PC10)" dump just fine, but it ignores the battery RAM that is specified in the iNES header.)
Re: Q's about iNES mapper assignments
by on (#14857)
-_pentium5.1_- wrote:
What's mapper 84, and why does the Kevtendo mapper status page mark it as a "poison mapper"?

"Poison mapper" generally refers to mappers that have been used only for pirate mapper hacks, such as the mappers built into the Front Far East copiers.

Quote:
The PC10 version of Mike Tyson's Punch-Out!! seems to use a MMC2 variant that has battery-backed WRAM. Since regular MMC2 doesn't have that, perhaps it is necessary to assign a new mapper number or UNIF board to this game?

UNIF: Yes.
iNES: Probably not, given the overloading philosophy of the overall file format. Mapper 9 + no battery = PNROM, while mapper 9 + battery = the PC10 version's board.

by on (#14862)
iNES mappers are one big mess, shared conflicts and duplicates everywhere. It can't be said which ones are still free, because, not counting the numbers assigned by Marat himself, the list is not official.

UNIF on the other hand... hmm, but that's like changing the world from QWERTY to Dvorak, it would help if Cowering would convert from GoodNES to GoodUNIF.

by on (#14865)
hap wrote:
it would help if Cowering would convert from GoodNES to GoodUNIF.


Yes it would... when I started redumping tons of carts, I pleaded with him to work on some sort of transition, but he isn't interested with UNIF in the slightest. :?

Some day my DB might get to the size of cowering's, but for now it's pretty much all USA carts and it can only convert what it has info on.

by on (#14867)
BootGod wrote:
hap wrote:
it would help if Cowering would convert from GoodNES to GoodUNIF.


Yes it would... when I started redumping tons of carts, I pleaded with him to work on some sort of transition, but he isn't interested with UNIF in the slightest. :?

Some day my DB might get to the size of cowering's, but for now it's pretty much all USA carts and it can only convert what it has info on.

I'm with you, BootGod.
If I ever get that #¤%! CopyNES to work with my parport, I've got quite a few PAL carts to dump! ;)

Martin

by on (#14871)
Nessie wrote:
BootGod wrote:
hap wrote:
it would help if Cowering would convert from GoodNES to GoodUNIF.


Yes it would... when I started redumping tons of carts, I pleaded with him to work on some sort of transition, but he isn't interested with UNIF in the slightest. :?

Some day my DB might get to the size of cowering's, but for now it's pretty much all USA carts and it can only convert what it has info on.

I'm with you, BootGod.
If I ever get that #¤%! CopyNES to work with my parport, I've got quite a few PAL carts to dump! ;)

Martin


same goes here.. :)

by on (#14890)
Okay, here's my excuse for the not-so-intelligent questions: I was up late at night for no good reason, and I was trying to cram all my mapper-related questions into one post.

tepples wrote:
"Poison mapper" generally refers to mappers that have been used only for pirate mapper hacks, such as the mappers built into the Front Far East copiers (emphasis mine).
So where is FFE F6xxx now assigned? It used to be mapper 12 back in the early history of iNES, until that "Dragon Ball Z 5" game came along. Now it is apparently unassigned and unemulated. Hmmm... 8)

-_pentium5.1_- wrote:
...perhaps it is necessary to assign a new mapper number or UNIF board to this game?
tepples wrote:
UNIF: Yes.
So am I responsible for notifying Marty and Quietust to make the necessary changes to their emulators? Who is responsible for obtaining a good dump in UNIF format?

hap wrote:
it would help if Cowering would convert from GoodNES to GoodUNIF.
But then n00bs wouldn't know what system "UNIF" is... :D

While I'm busy talking about mapper stuff, I may as well give everyone a heads up about this discussion on the Nestopia boards about emulating mapper 185.

by on (#14982)
Now that the discussion about FFE has been split, I would like to add one more issue: I would like someone to investigate what this translation's documentation says about mapper 78.

Specifically, the documentation says this (emphasis mine):
Quote:
...Because all this compression was already in place, there was nothing left
for me to compress. I had to expand the ROM with a mapper chip to fit in the
English text. But, I only needed a really basic chip that simply doubles the
lower bank of program ROM as this is where all the 496 blocks of text are
stored. I would simply swap it based on which of the pieces of text need to
be displayed at any moment.

It turned out that Mapper 78, the Irem 74HC161/32 chip was perfect. With it
you could have any number of program banks replace the first program bank, but
not change the second program bank--exactly what I needed. You can switch
character banks with it too, but I didn't need that. Supposedly, "several
Japanese Irem titles use this mapper", but I could only find two.

* Uchuusen - Cosmo Carrier by Jaleco
* Holy Diver by irem

And they switch banks quite differently, so in reality they are actually two
completely different mapper chips. Holy Diver's mapper needed a special 256
byte table to work... yuck, I didn't have that kind of room to waste. But
Uchuusen's mapper, you simply load the bank number you want into register A
and then perform this 4 byte piece of code.
Easy and efficient.

tay ;A8
sta $d548,y ;99 48 D5
Should mapper 78 be split? Or do the two games mentioned really use the same bankswitching method and different data patterns to handle bus conflicts (Holy Diver a table of all possible byte values, and Uchuusen - Cosmo Carrier something a little more clever)?

by on (#14992)
It would only make things messier: http://nesdev.com/bbs/viewtopic.php?t=796 (Quietust's reply)