nesdev.org

I looked on the wiring section of nesdev, but it does not seem to be listed. I am trying to make myself a Dragon Scrolls, and it requires an AxRom board, but no idea how to wire that up. Is it the same as any of the other ones? Thanks

It depends on which AxROM you're dealing with. AMROM and ANROM use ordinary Nintendo 128K mask ROMs, for which the UNROM, SGROM, or SNROM conversion guide should work. AOROM needs special ROMs with a second positive chip enable (+CS2).

I don't know what kind of Dragon Scrolls you're talking about. I searched for dragon sc on NesCartDB and got this game using a Konami VRC2. Konami boards by and large use standard EPROM pinout.

tepples wrote:It depends on which AxROM you're dealing with. AMROM and ANROM use ordinary Nintendo 128K mask ROMs, for which the UNROM, SGROM, or SNROM conversion guide should work. AOROM needs special ROMs with a second positive chip enable (+CS2).

I don't know what kind of Dragon Scrolls you're talking about. I searched for dragon sc on NesCartDB and got this game using a Konami VRC2. Konami boards by and large use standard EPROM pinout.

Yeah Dragon Scrolls is a Konami game. So I could just use a Konami board, with no modifications to the chip or rewiring?

This is what is says in NES Mapper Reader:

NES MAPPER: 7 - 32kb ROM (PRG) Switch [A(x)ROM]
Mirroring: [Horizontal Mirroring]

PRG: 128kb (8 x 16kb pages )
CHR: 128kb (16 x 8kb pages)

Battery: YES

Tormenter wrote:This is what is says in NES Mapper Reader:

NES MAPPER: 7 - 32kb ROM (PRG) Switch [A(x)ROM]
Mirroring: [Horizontal Mirroring]

... whatever software this is, it is crap.

VRC2 is mapper 23 (among others), or 0x17 in hexadecimal, and "NES Mapper Reader" is evidently ignoring everything but the lowest 4 bits.

It's a VRC2 game. You'll need a VRC2 to make it, not an AxROM board.

Mappers greater than 15 were introduced in version 0.7 of the iNES emulator. This means that very, very old NES ROM tools from before about 2000 will reduce the mapper number mod 16. And because 23 / 16 = 1 remainder 7, such ancient tools will report 7.

Another example of there not being decent tools that have "evolved" with the supposed "format". The only people who suffer from all this are end users. In other words: I can't blame Tormentor.

I end up using Nestopia a lot of the time to review said header data (see View -> Image Info). And yes I'm aware it doesn't support NES 2.0 (irrelevant to what's being discussed right now).

I've written an NES 2.0 unpacker in Python. If it'd help, I can clean it up and release it now.

Tormenter wrote:NES Mapper Reader...

lidnariq wrote:...is crap.

I you want something much better, quietust made a tool called nes2edit.exe for editing iNES headers. (Even works for NES 2.0 extensions.)

... huh, how easy would it be to convert that into a Property Sheet shell extension ?

I dunno how easy writing a shell extension would be, but you can add nes2edit.txt to the right-click "open with" list very easily, which seems just as good as having it in the properties window, to me?

Okie I am confused now lol. What donor cart would it need?

Something with a VRC2 on it.

There are a bunch of pirates carts that use them (e.g. search for "23C3662"); all the licensed ones are Famicom-only. Either way, both pirate and licensed, the VRC2 appears to have only ever been on 60-pin cartridges, not NES 72-pin.