I knew I was forgetting something all this time… EDIT: Now with No-Intro comparison

So, as I was going through testing ROMs to add to the Java emulator, I came across a couple redumps I never actually got around to showing on the blog!

For two years!


The game they’re for has been put on the Java emulator already. It’s Dr. Mario!

I don’t remember the details too hard on these redumps, but if my memory serves they have the ol’ “Deleted Headers”. The Java embed is of the first of the two – it appears to play identically to the commonly circulating ROM.

I deeper analysis might come around.. if I don’t forget for another 2 years.

Dr. Mario (BS)
ROM Download

EDIT Oct. 15, 2012: I’ve attempted to do a more in-depth comparison with the previous dump, HOWEVER…

It appears said previous dump, as it appears in the no-intro set, has a hacked header. I’m not entirely sure how this happened, but regardless…

Here’s 7FC0-7FDF on the previous ROM:

42 53 5F 44 72 20 4D 61 72 69 6F 00 FF 00 00 00
00 00 00 00 00 00 FF FF 20 10 33 02 CE B7 31 4B

On the same addresses, these two redumps have the following bytes in common:

82 63 82 92 81 44 B3 7D 83 8A 83 49 82 61 82 72
FF 00 00 00 00 00 ** ** 20 10 00 02 00 00 00 00

(The ** are differing bytes. Their location is in the “date” area of the ROM, anyhow.)

Notably, while the latter two’s headers are consistent with a “Deleted” game, the former has a header that just plain looks screwed up, especially with spelling “BS_Dr.Mario” the way it does.

Furthermore, none of the ROMs load in BSNES, but while this is expected of the deleted header ROMs, the “hacked” header ROM causes an odd behavior which causes the ROM loader to crash.

To boot up Dr. Mario closer to the way it was meant to be played, the header should look something more like this;

82 63 82 92 81 44 B3 7D 83 8A 83 49 82 61 82 72
FF 00 00 00 00 00 ** ** 20 10 33 02 C7 B7 31 4B

Note how the “hacked header” ROM does appear to have the checksum and maker values correct. Either the hacker attempted to restore these, or the header hack was based off a previously “pure” dump. This may need to be investigated.

… To think we don’t even have as simple a ROM as this in it’s purest state? Sheesh…


  1. JamesBond007 said,

    October 9, 2012 at 6:56 am

    Do you know that BS Dr. Mario actually contains full Tetris & Dr. Mario ROM? You can use PAR code 80802D01 to start at game selection screen.

  2. Kiddo said,

    October 9, 2012 at 11:02 am

    I recall reading that in TCRF, but have not gotten around to checking it out. It should make a good Youtube video.

    It’s unfortunate that this means the downloaders were basically locked out of a Tetris copy. I wonder why? Perhaps Nintendo had rights issues with The Tetris Company at the time… they didn’t seem to have anything Tetris-related on the Satellaview after “All Japan Super Bombliss Cup ’95″…

  3. ChronoMoogle said,

    October 10, 2012 at 4:10 am

    It is probably the same with that Nintendo Power Dr. Mario. I remember that I saw it in Akihabara… Strange decision to lock a whole half of a game for the japanese release.

  4. JamesBond007 said,

    October 12, 2012 at 8:27 am

    NP Dr. Mario is the same – Tetris is hidden and the PAR code to unlock it is the same.

    With some hacking, it should be possible to force the game to start at the Tetris & Dr. Mario Title Screen and allow the game to return from Dr. Mario title screen to Tetris/Dr. Mario/Mixed Match game selection screen with the B button. This command still works in Tetris and Mixed Match, but not in Dr. Mario.

    Technically, making a “BS Tetris & Dr. Mario” ROM (still runable via BS-X Bios) should be possible. Same with “NP Tetris & Dr. Mario”.

    BTW, I made a mistake in my first comment. The PAR code mentioned above loads the title screen, not the Tetris/Dr. Mario/Mixed Match selection screen.

  5. Kiddo said,

    October 15, 2012 at 3:18 pm

    Did an IMPORTANT article update. I will report it to No-Intro ASAP.

  6. redeemer665 said,

    October 17, 2012 at 6:43 am

    Well done. The old dump clearly has its internal name hacked.

    BSX headers have been a real pain in the neck since they were even designed to be modified by the system for some extent. I’ve come to a conclusion that the most important bytes that we need to have unmodified and original in the header are at $7/F:FD0 (Allocation bytes) and $7/F:FD9 (ROM type), among the internal checksum of course.

    Of those the checksum is the only one that could get overwritten by the BIOS but calculating a new one is easy if we have those two other bits of info correct.

    By the way, if you’re ever reading this, LuigiBlood, do you know if it could be possible to download a part of the streamed broadcast data into PSRAM for additional graphics (Inishie no Sekiban dungeon tile data) while running most of the game from the FLASH memory? By judging how those two memory chips can be mapped independently at different memory addresses it could theoretically work, but is this actually possible?

  7. LuigiBlood said,

    October 17, 2012 at 7:13 am

    Well, redeemer665, it is possible, in fact, when you run something from PSRAM, you can download more stuff from it into the FLASH, I think BS Zelda did that.
    But the BS-X BIOS can also do that, as downloading a game can work with several file downloads, so it can be PSRAM Files, and FLASH Files at once.

  8. redeemer665 said,

    October 17, 2012 at 2:35 pm

    LuigiBlood, do you mind if I help you to write up a proper help file for the SatellaWave utility? I’ve been trying to figure out for days and weeks how to use it effectively with no results.
    I’ve managed to create some files but I’m not sure if I even understand the naming scheme correctly. Also how is the Time Channel supposed to work? Every file I save from the “Time” tab ends up being 0 bytes…
    So, my idea is that I would do sort of an interview with you and ask about everything that’s missing a clear explanation, then write sort of a FAQ file based on your answers and you would proof-read it later. How does it sound? :)

RSS feed for comments on this post · TrackBack URL

Leave a Comment