However, I have a question, and I might look like a dummy, but I really don't know what else to do:
One of my favorite games since I was a kid was Super Mario Bros. 2 (the Japanese version). I was able to play it due to some odd job of Famicom cart I had, but now my Famicom is busted thus I can't play it (and no, it doesn't seem to work on the cheap Famiclone I got).
The game was originally created for the Famicom Disk System. I have the FDS file on me, but whenever I try to run it the emulator just stops on its tracks. I've searched this topic in search of clues so that I can pull this up, but nothing was helpful, except something I read about mappers (more on that later in this post).
I even thought that if I updated nesDS to 1.02b (the most recent version as of today) I could make it work. But it didn't. I already copied the disksys.rom (BIOS) file to the ROMs folder, just in case.
I load the FDS file with the browser, and the emulator stays blank. If I open any other normal NES file, it works perfectly, but if I try to run the FDS, the emulator stops (and even the graphics that were shown before I load the file get garbled). In case this helps, the debug window shows this:
Code:
ERR0 00000000 ERR1 00000000
READ 00000000 WRITE 00000000
BRK (increasing numbers like there's no tomorrow) BAD OP 00000000
VBLS (numbers go up from 00 to 3F and reset very fast) FPS 0000003C
BGMISS 00000001 cartflg000000E5
... (3 lines of values all in zeroes)
mapper#00000004 PRGCRC 000098E3
diskno 00000000 makeid 00000000
gameid 00000000 emuflag00000040
Regarding those old posts I found about FDS support, I read that the ROM mapper had to be number 20, but I really don't know how to change it. Another thing that has left me thinking is why does it show diskno 00000000? Am I using a bad ROM file?
