Mysterious Mikie ROMs

Womble

Well-known member
Joined
Oct 12, 2009
Messages
1,078
Reaction score
84
Location
Vic, Australia
Hey folks, I have an original Konami Mikie board on the repair bench. It has one of the ROMs missing and shows no signs of life. Of the remaining ROMs on the CPU board all the TI eproms are bad, giving different data everytime they are read. I do have two working ROMs (NEC chips) on the board which let me identify the ROM set as being...

"Mikie (Konami, alt set)"

... but this data set is not available anywhere. There are a few versions online but none are a match. What is odd is that these ROM images are not even referenced by the mame driver, so if this version was once supported by MAME is isn't anymore. The only page on the web that lists these ROMs is here...

http://bewn.free.fr/dats/MAME - ...0.90_CM).dat

... and thats just a text file.

If anyone possessing greater Google powers than I can find these files..

game (
name "MAME (v0.33b6) - mikie"
description "mikie - MAME (v0.33b6)"
rom ( name mik_10d size 8192 crc a852bfb0 )
rom ( name mik_12a size 8192 crc 2894c75d )
rom ( name mik_12c size 8192 crc 2480b5db )
rom ( name mik_12d size 8192 crc 7a2631ea )
rom ( name mik_8i size 8192 crc 3bd2ed12 )
rom ( name mik_9i size 8192 crc a7007184 )
)

.. or if anyone has a Mikie that happens to have this rom set would you be able to dump the ROMs for me? If you have a Mikie board with ROMs at 8i, 9i, 10d, 12a, 12c and 12d then it is likely to be the right set.

Without these ROMs the board is sadly just more scrap which would be a shame.
 
Last edited:
Am at work at the moment but I am fairly sure they are bog standard TMS27c64s.

With so many bad ROMs I did wonder if the board had been powered up with the harness reversed but the two non-Ti chips are are fine, as are the ROMs on the gfx board and the socketted Z80.
 
you may have the data you need and just not realize it. Some of the mame romset are 16k files, and the ones your missing are half that size. I think it was just a difference in how the pcb was strapped - either for 2764s or 27128s. You can extrapolate the data you need from the mame romset.
 
Without these ROMs the board is sadly just more scrap which would be a shame.

I disagree - if it comes to it, PM me -- I'd probably buy it.

Also, are you reading the ROMs on the Mikie board itself? Are you sure the control logic to the ROMs is good? I just want to understand your setup. You can also put the ROMs into a known good board - Hypersports, Track & Field, Super Basketball, etc or some other board with same size ROMs with known good logic and read them with a Fluke 9010a.

I have a Mikie board that I haven't even looked at yet... I can try and find it to see what ROMs I have if the need is still there. But, again, since I haven't looked at it yet, I don't know if my ROMs are good at this point.

Either way, don't scrap that board!!!
 
maws shows a different set of roms?

n14.11c 8192 f698e6dd mikie
o13.12a 16384 826e7035 mikie
o17.12d 16384 161c25c8 mikie
n10.6e 8192 2cf9d670 mikie
o11.8i 16384 3c82aaf3 mikie
001.f1 16384 a2ba0df5 mikie
003.f3 16384 9775ab32 mikie
005.h1 16384 ba44aeef mikie
007.h3 16384 31afc153 mikie
d19.1i 256 8b83e7cf mikie
d21.3i 256 3556304a mikie
d20.2i 256 676a0669 mikie
d22.12h 256 872be05c mikie
d18.f9 256 7396b374 mikie

there is a pcb picture as well.

http://maws.mameworld.info/maws/romset/mikie
 
Yea. Like CDjump stated, that romset is probably from a board like this, with 27128K roms:

Mikiewith27128KROMs.jpg
 
looks like need to find an old copy of mame, i just did a crc search and nothing with the same crc exist for the set he posted.
 
I think that the problem is the 27128K ROMs. Mame only stores those ROMs from what I can gather. There is no need to store the 2764K versions, because they are the same as the 27128Ks.

For instance:
o17.12d 16384 161c25c8 mikie

This is the ROM at 12d on the board with 128K ROMs. What this contains is ROMs 12c and 12d from the 2764K ROM version (I assume...). If you were to pull out the first 64K of this ROM and compute a CRC on that data, you would end up with the proper 64K checksum for the ROM at 12c. Then, the reamining 64K of data would CRC to the ROM at 12d

Do you have the ability to test that? Just curious?
 
o13.12a , 0x0000 - 0x1fff CRC32B = A852bfb0 = mik_10d
o13.12a , 0x2000 - 0x3fff CRC32B = 2894c75d = mik_12a
 
Cool - so that works, and the ROMs contain the same info. So how will this affect your Romident tool? Can you handle this on your end, or do you really need the 64K ROMs in MAME? I wonder how many other times 64K ROMs have been dropped in favor of 128K or larger.
 
Yep - I must have stuffed up as I did compare the contents of the remaining functional 64kbit ROMs with the upper and lower halves of the mame 128kbit files and found they didnt match, since looking again they do match so not sure what I was smoking that day. The board supports both ROM sizes by means of a number of jumpers anyway.
 
All's well that ends well. I feel that I can sleep better now that I know that Mikie board won't end up in the scrap pile!
 
Cool - so that works, and the ROMs contain the same info. So how will this affect your Romident tool? Can you handle this on your end, or do you really need the 64K ROMs in MAME? I wonder how many other times 64K ROMs have been dropped in favor of 128K or larger.

well, kinda hard since mame dropped the 64K images from the mameset, i hope to have the ability to add items like this to the set (which would be a custom set), and when i update the mame database it would not overwrite it.
 
Back
Top Bottom