Excitebike ROM files needed

KevinMullins

Active member
Joined
May 27, 2009
Messages
2,187
Reaction score
10
Location
Mcloud, Oklahoma
Does anyone have the ROM files for Nintendo's MDS-EB roms?
(.vs Excitebike)

NOT the MDS-EB4. (note the # 4 difference)
Already been down the MAME route....... they DO NOT match.

I am looking for a set that includes the CRC checksums that match
these.

1c.bin CRC= 6AE01102

1d.bin CRC= F58A392E

Should note that these ROMS are actually labeled "1C or 6C" and "1D or
6D".

(can be used on either side of the dual board)


And yes....... I am trying to repair an REAL set of ROMS.
(before I get slandered about requesting ROMs and such)
 
I'm curious too....... :)

All I can say is I have this particular "MDS-EB" ROM set, but can't find the files to fix the rest. There's three of the six that come up unidentified.
 
I assume the CRC's you listed then are of the ROMs you have that are good, but does EB have a test mode to test if they are good?
What program gave you those CRC's?

Is there writing in pink or red on the ROMs?
 
Yes, the CRC's I listed are from two of the three that came up good against RomIdent.
The third one (which I didn't list) is the only one that actually matches the set in MAME.
So that's why I was looking for a set that matched with those two.
The software for my programmer is what gave me all these CRC's after dumping the roms.
Not sure if EB has any kind of test mode for checking the roms. Right now these won't do much of anything to speak of in a known working boardset with Super Mario in it. And yes, I do have the proper PPU chip and all that as well for this EB set.
There is just an ever so slight hint of pink on a couple of the roms, but if you look closely at a few of them you can tell that these have been re-labeled at some time. But the labels are indeed original Nintendo labels. you can almost make out a letter here and there from the label underneath, but not enough to make anything of them.
In the pic I'm posting you'll see three roms without labels over the windows..... those are the three that came up unidentified. So I naturally got ready to burn new ones from the MAME files and went ahead and erased them and then that's when I realized something just wasn't right between what the good roms told me and what MAME had. (meaning there's a difference somewhere, CRC's, etc) You can also tell they were reburned at one time just because there are even different chip types amongst them. That's no biggie, but the difference in file data is.

Here's the speil I posted on BYOAC, both for assistance and for my own notes as I go along, which may help explain the scenario I've run into with these from the beginning -

First Post -

Is there an updated RomIdent .dat file ?
I'm checking a set of Excite Bike ROMs and three of the six come up bad in RomIdent.
Of the other three that check GOOD in RomIdent, only ONE of them has the same checksum as the ones found in MAME. (mds-eb4.2b)

How does someone put together a "matched" set of ROMs here in the real world using MAME files if old stuff (i.e. my RomIdent dat file) doesn't even match with new stuff (i.e. current MAME files) ?


ROM files I just dumped from real chips with CRC according to RomIdent -

============================
1a.bin:[E2902B4E] Not Found!
============================
1b.bin:[715A1A80] Not Found!
============================
1c.bin: (1/1) [6AE01102]
- 1C : VS. Exite Bike
============================
1d.bin: (1/1) [F58A392E]
- 1D : VS. Exite Bike
============================
2a.bin:[D8A79A84] Not Found!
============================
2b.bin: (1/1) [80BE1F50]
- 2B : VS. Exite Bike


ROM files available in MAME files (not including Japan version) -

mds-eb4.1a 8192 b9ab7110
mds-eb4.1b 8192 4c0c2098
mds-eb4.1c 8192 89baae91
mds-eb4.1d 8192 7e54df1d
mds-eb4.2a 8192 a9b49a05
mds-eb4.2b 8192 80be1f50

Note that 1c and 1d check good in RomIdent yet don't even match what's found in MAME.
So how am I suppose to burn new ROMs for the other three "bad" ones and guarantee they will work with the other three that already check good in RomIdent?
2b is the only one that matches in BOTH RomIdent and MAME files.

Second Post -

NOTE: I do realize RomIdent has not been updated in forever, I just like playing with it when I doink with ROM's. And sometimes mixing old and new brings out some surprises.

Ok, after some serious poking around basically what I've found out is that these ROMs that I have are being recognized in the old RomIdent ..... BUT..... the data RomIdent is using is NOT directly from MAME.
The MAME version of the ROM's are NOT even recognized by RomIdent.
I could also tell these were not from MAME by the way the "name" was written when these were recognized by RomIdent. Any names in RomIdent that show from MAME data show up as all capital letters, RomIdent's database (wherever it came form) does note. And RomIdent has the "excite" mis-spelled. These show up as Vs. Exite Bike. (versus Excitebike)

So the question remains.....where did RomIdents version of these ROMs come from that they have listed in their database ?
And how can I find a copy of them ?

BTW - Our ROMs have just MDS-EB on the labels.... not the MDS-EB4 you find everywhere.
 

Attachments

  • MDS-EB ROMS.jpg
    MDS-EB ROMS.jpg
    90.3 KB · Views: 12
  • EB ROMS.jpg
    EB ROMS.jpg
    83.8 KB · Views: 8
Last edited:
If you're just interested in getting the game running, try dumping the good ROMs, then replace the ROMs in the .zip of the ExciteBike set, with the good ones and see if it'll play in MAME. If it will, then just replace the bad ones with the good ones from the MAME .zip and call it a day. If you're reeeeeeeaaaaaally wanted to get the exact same ROMs that were originally on the chip, then it can take a bit of searching... but they're probably out there.
 
Getting the game running shouldn't be a problem, even if burning a whole new set using the MAME set is needed. I have no problem erasing and redoing all of them if need be.

Just really curious to find the files that match this original set I apparently have half of. (whatever version it may turn out to be)

I may try throwing these three in MAME and see what happens..... wouldn't be the first time I've done that sort of thing for kicks. Usually it'll pop up checksum errors, but if all is good it'll still continue past that and play. Will let ya know how that goes.

EDIT: Just tried the ones recognized by RomIdent in MAME..... it would NOT play. "missing ROM or CHD" error. Tried them just one at a time...... still would not play with either the 1c or 1d.
The only one it would actually play with is the one that was recognized by both RomIdent and MAME, the 2b ROM.
 
Last edited:
A friend of mine just showed me how to do the -romident directly through MAME.
So I did... same results.

These are the three files the older RomIdent program recognized, but and as you can see MAME does not recognize them except for the 2b file which I already expected it to recognize.
 

Attachments

  • MAME results.JPG
    MAME results.JPG
    62.3 KB · Views: 7
  • RomIdent results.JPG
    RomIdent results.JPG
    66.9 KB · Views: 9
Back
Top Bottom