Rom identification

silverfox0786

Beware the Hillman
Feedback
47 (100%)
Credits
2,699CR
Hi

Does any one know how to identify the different roms within a game pcb

for example

how would some one know which roms contained the Audio , and which roms contained the GFX and which roms contained the Main Program

its real confusing for me and im sure there must be a way of telling

thanks
 

silverfox0786

Beware the Hillman
Feedback
47 (100%)
Credits
2,699CR
im looking at it now

I cant make it out much

im trying to read and absorb it but its just way to confusing

some parts I understand and I can code a little in c and python so that helps my understanding but as a whole is a little confusing
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Ah, don't try to understand how to actually write any stuff with it. It's like someone swallowed a theory manual on C, spat out the most obfuscated macro based thing you could possibly imagine and didn't document it in any meaningful fashion along the way!

However, the ROM part is easy...

Take Galaxian for instance: http://mamedev.org/source/src/mame/drivers/galdrvr.c.html

(There's an absolute bucket load of different games in that driver)

You will see for example, the ROM definitions for Frogger (on galaxies hardware I presume):

Code:
[code] 5210  /*************************************
	 5211   *
	 5212   *  ROM definitions
	 5213   *  Konami games
	 5214   *
	 5215   *************************************/
	 5216
	 5217  ROM_START( frogger )
	 5218      ROM_REGION( 0x10000, "maincpu", 0 )
	 5219      ROM_LOAD( "frogger.26",   0x0000, 0x1000, CRC(597696d6) SHA1(e7e021776cad00f095a1ebbef407b7c0a8f5d835) )
	 5220      ROM_LOAD( "frogger.27",   0x1000, 0x1000, CRC(b6e6fcc3) SHA1(5e8692f2b0c7f4b3642b3ee6670e1c3b20029cdc) )
	 5221      ROM_LOAD( "frsm3.7",      0x2000, 0x1000, CRC(aca22ae0) SHA1(5a99060ea2506a3ac7d61ca5876ce5cb3e493565) )
	 5222
	 5223      ROM_REGION( 0x10000, "audiocpu", 0 )
	 5224      ROM_LOAD( "frogger.608",  0x0000, 0x0800, CRC(e8ab0256) SHA1(f090afcfacf5f13cdfa0dfda8e3feb868c6ce8bc) )
	 5225      ROM_LOAD( "frogger.609",  0x0800, 0x0800, CRC(7380a48f) SHA1(75582a94b696062cbdb66a4c5cf0bc0bb94f81ee) )
	 5226      ROM_LOAD( "frogger.610",  0x1000, 0x0800, CRC(31d7eb27) SHA1(2e1d34ae4da385fd7cac94707d25eeddf4604e1a) )
	 5227
	 5228      ROM_REGION( 0x1000, "gfx1", 0 )
	 5229      ROM_LOAD( "frogger.607",  0x0000, 0x0800, CRC(05f7d883) SHA1(78831fd287da18928651a8adb7e578d291493eff) )
	 5230      ROM_LOAD( "frogger.606",  0x0800, 0x0800, CRC(f524ee30) SHA1(dd768967add61467baa08d5929001f157d6cd911) )
	 5231
	 5232      ROM_REGION( 0x0020, "proms", 0 )
	 5233      ROM_LOAD( "pr-91.6l",     0x0000, 0x0020, CRC(413703bf) SHA1(66648b2b28d3dcbda5bdb2605d1977428939dd3c) )
	 5234  ROM_END
Code:
[font="Arial, Helvetica, sans-serif"]
[/font][/code]
Code:
[font="Arial, Helvetica, sans-serif"]We can see from that, which are the graphics ROMs, sound ROMs, cpu ROMs etc.[/font]
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
If you want to ident a ROM, read it in you eprom programmer, save the file to disk and them use "mame -romident <fname>" (from memory, things could have changed) and it should tell you if the CRC32 of the file matches any known games in mame and if so, which ones.

However, if it doesn't find a match, don't automatically assume your ROM is bad and erase it. It could simply be a ROM that is not in name (they're far from all in there). To properly know if an unknown one is bad then can do stuff like modify the checksum of the ROM list in name so it's accepted and then try and run it?

guddler2014-04-02 01:55:41
 

silverfox0786

Beware the Hillman
Feedback
47 (100%)
Credits
2,699CR
I wasn't trying to read a rom or anything

I just wanted to understand the board

like I know CPS-2
1-2 is Audio, 3-10 is main prog 11-12 is q etc etc

and MVS
v rroms are x m roms are x p roms are x

if I can understand them then it helps in diagnosing board faults and also good to know

will look at those links
 

favouredson

Super Star
vacBacker
Credits
1,260CR
With a lot of PCBs the ROMs are logically arranged.
The sound code near the amp/sound CPU, the program code near the main CPU and any remaining ROMs will generally be the gfx code.

Obviously, not all PCBs are designed the same but many are.
 
Top