Warning - ROM request inside

[Kevin Mullins]

 

Excitebike ROM files needed.......

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)

If I can match these two files then I know I have the right set in order to burn the ones I actually need. We have three bad ROMs.

[SavannahLion]

Maybe ask someone like this guy if he can dump the needed roms for you?

[Kevin Mullins]

Just sent him a message last night as a matter of fact.   
(waiting to hear back)

[death69inc]

not sure the crc's but i have liek ten excitebike sets Ill look at them

[Kevin Mullins]

That would greatly be appreciated as I've had no luck so far finding a set that includes the two crc's I mentioned.

[death69inc]

im checking now
i do have a question how do you know the crcs are right if you need to repair them they may be corrupted?
just asking

5 sets checked all had same crcs
1c = ofefba
1d = oc9ba9

none match yours
if i had my programmer hooked up to pc I woudl see what mames crc is prob same as the sets tested



did you check the jap set might have that crc

[Kevin Mullins]

i do have a question how do you know the crcs are right if you need to repair them they may be corrupted?

The two I listed are the ones that came up as GOOD against the older RomIdent program. So those are the two I want to match to see if I can find that particular set.

5 sets checked all had same crcs
1c = ofefba
1d = oc9ba9

Not sure how you got those CRC's either..... are you checking CRC32 ?
Yours don't match anything I've seen yet.

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

did you check the jap set might have that crc

I did check and they don't match anything I have either.

I started out by just dumping this whole set to see which ones were bad. Three came up good in the old RomIdent program, so I went with those and starting looking in MAME....that's when I found only one file matched between what I dumped and what MAME has.
When I run these files I have against the old RomIdent program they get recognized. When I run them against MAME's romident they are not recognized.
(except for the one 2b file that matches both)

So I've been digging to find a set that RomIdent apparently had in their database.
Now whether it was a good set..... I don't know. But I'm looking anyways.

[death69inc]

I gave you checksums my data i/o 29b gives me
I will need to get my promlink working to dump and check agian
or i think my emp20 will work on windows 7 i have to see and get back to you
if they end up matching the ones your looking for ill let you know
 

[Kevin Mullins]

I gave you checksums my data i/o 29b gives me

Ah..... maybe a different checksum type or something then, because they don't match anything I'm working with. (CRC16bit or CRC32bit)
I wish I could also get Sha1, but my programmer software doesn't show me that, it's a basic Willem.

32 bit CRC check -

Mine:
1c.bin CRC= 6AE01102
1d.bin CRC= F58A392E

MAME:
1c.bin CRC= 89BAAE91
1d.bin CRC= 7E54DF1D

MAME Japan:
1c.bin CRC= BDB317DB
1d.bin CRC= 6AA87037

Yours:
1c.bin CRC= OFEFBA     (?)
1d.bin CRC= OC9BA9    (?)

I will need to get my promlink working to dump and check agian
or i think my emp20 will work on windows 7 i have to see and get back to you
if they end up matching the ones your looking for ill let you know

That would be great if you could check.  

[Kevin Mullins]

I wish I could also get Sha1, but my programmer software doesn't show me that, it's a basic Willem.

Just found a great little program for doing just that...... called Pinpoint Hash.

Mine:

File Name: 1c or 6c.bin
File Size: 8192
CRC32 Digest: 6AE01102
MD5 Hash: B765FF1B31A4EAD7556B2C19387F313C
SHA-1 Hash: F3F49644F7E2887E14655E8934C7C75D4B92968E
SHA-256 Hash: 9FD5857AD63F88BD22288AE56C80DCAE3BD92A0A9B664D0507A148629DC99B29

MAME:

File Name: mds-eb4.1c
File Size: 8192
CRC32 Digest: 89BAAE91
MD5 Hash: F8A80B45E24E1A5601C9DD3AFFF8EBD9
SHA-1 Hash: 6AEBF13C415E3246EDF7DAA847533B7E3AE0425F
SHA-256 Hash: 0D96367C89F1D93BA1A58484A0BC2D21BFBE6F104B1B128B9EEF407E5FEE39CD

MAME Japan:

File Name: mds-eb4-4_6c_a.bin
File Size: 8192
CRC32 Digest: BDB317DB
MD5 Hash: EC72E280E69037F8631D37B89A7974A9
SHA-1 Hash: A8B3E8DEB1E625D764AAFFE86A513BC7EDE51A46
SHA-256 Hash: CE7D9B584FF729C3D5CCBCFD5EFF2D1A2A8CEDFBD16DB9F216C65C402CA4F2C0

[death69inc]

sorry cant get my emp20 to dump
and cant get my promlink to work with my 29b

both worked fine last time i used them think pc blocking comunications somehow
shrugs

[death69inc]

ok so far 3 sets match mame

1c.bin CRC= 89BAAE91
1d.bin CRC= 7E54DF1D

finally have my programmer well my 29b working thanks to hobbyroms

edit all my sets match mame even pulled roms off board lol

[Kevin Mullins]

Cool...... I appreciate you taking the time to look through those.
 

[death69inc]

maybe you set was programmed with a bad dump?

i can look into my old mame set from years ago and see if that set has the old crc's

who knows

[Kevin Mullins]

maybe you set was programmed with a bad dump?

Well, I would have just thought the same thing..... but .....
RomIdent recognized the ones I dumped, MAME doesn't recognize them.
And at the same token, Romident does not recognize MAME's.
(all with the exception of one file, 2b recognized by both)

I'd be happy to just burn a whole new set of MAME's version, but that still wouldn't answer why there's a different set recognized by Romident.

And Romident recognized the ones I dumped correctly as being a version of Excitebike. (three of the six anyways)
So you would figure a bad dump would just come up as plain unrecognized all around.

Hope my confusion makes some sense.

[death69inc]

what i ment is maybe the romident set was a bad dump
who knows

maybe there was a revision that is known but the mame set is the more known??

never used romident but i will on a unknown board i have tecmo not sure the game lol

i use clrmamepro verify my roms but will use romident to see if it can find out what board this is forgot about it that didnt work unknown lol )@)%@&%*

owell made a adaptor harness with fingers crossed nad now i knwo i have a simi working tecmo tee'd off but not one rom passes mame or romident lol
will probably dump the set and reflash with mame set to see if clears up the issue if not diagnostic mode i go