Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Matching ROM files between MAME and RomIdent ?  (Read 3205 times)

0 Members and 1 Guest are viewing this topic.

Kevin Mullins

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4504
  • Last login:February 01, 2021, 01:29:34 pm
    • Me on Myspace
Matching ROM files between MAME and RomIdent ?
« on: November 19, 2009, 11:21:00 am »
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.

Make any sense ?   :lol
Not a technician . . . . just a DIY'er.

Kevin Mullins

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4504
  • Last login:February 01, 2021, 01:29:34 pm
    • Me on Myspace
Re: Matching ROM files between MAME and RomIdent ?
« Reply #1 on: November 20, 2009, 01:51:59 pm »
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 in 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 ?  :angry:

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

Not a technician . . . . just a DIY'er.