NEW! Arcade Memory Maps now on-line in BETA!

Arcadenut

Well-known member
Joined
Jun 12, 2003
Messages
9,355
Reaction score
4,888
Location
Glendale, Arizona
just found this and so worth a bump. Anyway to include fluke sigs for the roms. That would be even more awesome.

I love on your rom ident that you can paste in the CRC and get the rom file name.
 
Can you get them to me in electronic form? Text file would be fine.

Ok, I thought you were calculating the crc and sha but appears the CRC in rom map, anyway, is coming from mame driver?

I could probably generate a list of fluke sigs from all roms I have using Brian's or Ian's scripts not sure if that is the best way. Just thinking of work flow out loud. Look up rom map, grab crc, put crc in romident, get fluke sig.
 
Ok, I thought you were calculating the crc and sha but appears the CRC in rom map, anyway, is coming from mame driver?

I could probably generate a list of fluke sigs from all roms I have using Brian's or Ian's scripts not sure if that is the best way. Just thinking of work flow out loud. Look up rom map, grab crc, put crc in romident, get fluke sig.

The CRC and SHA1 values are from MAME.

Do you have a link to the scripts? I can take a look at them and see if it's something I can do on my side or if you would need to generate the list.
 

That code operates on the complete ROMs -- it can't be simply parsed out of the MAME source code like everything else on his site.

In any case that python code is incredibly inefficient since it operates bitwise....
There are far more efficient bytewise CRC algorithms out there. I coded up a nybble-wise one in assembly for 6502 and Z80 for ROM checks on my kits, as the tables for bytewise operations took up too much ROM space.
 
That code operates on the complete ROMs -- it can't be simply parsed out of the MAME source code like everything else on his site.
.

Yea, I haven't used Ian's python script yet but was just planning on running over all my roms (should be a somewhat complete set) and giving arcadenut the output. I am not a programmer but could probably brute force something that is a table of rom file name, crc, sha, fluke sig. I assume that is how http://romident.coinopflorida.com/ has done it.

Just would be nice to stick in the crc or sha hash of file from mame driver and get the file name and fluke sig. or the reverse, you read a rom on fluke and get the fluke sig, put that in and see if it matches anything.

then again, I just started using my fluke so maybe this is useless.
 
Yea, I haven't used Ian's python script yet but was just planning on running over all my roms (should be a somewhat complete set) and giving arcadenut the output. I am not a programmer but could probably brute force something that is a table of rom file name, crc, sha, fluke sig. I assume that is how http://romident.coinopflorida.com/ has done it.

Just would be nice to stick in the crc or sha hash of file from mame driver and get the file name and fluke sig. or the reverse, you read a rom on fluke and get the fluke sig, put that in and see if it matches anything.

then again, I just started using my fluke so maybe this is useless.

I would only need the fluke signature and one of those pieces of information (MAME driver name, CRC, SHA1) as they would used to find the existing records. I already have the CRC and SHA1 so no need for those to be recalculated.
 
I found the Quarter Arcade's CalcSignature app.

I'll run it against the ROMS's I have which should give us the majority of them.

Then we can figure out what to do with the missing ones.
 
Back
Top Bottom