Romcenter

That means the size and/or the checksum of the roms do not match the data, i.e. the roms are not correct ones according to the data.
And it is not strange that they work `fine' in MAME.

Oh I get it. It's the completely unlabeled thing that was blank and not mentioned in the "getting started" file. Very intuitively written! </sarcasm>
Yes that's it. I said "using the long dropdown listbox shown in your picture". Maybe that is not an understandable description:)

The first step should be 'selecting a data set" (e.g., your MAME data file) using the long dropdown listbox shown in your picture. If there is nothing, your data file is not correct or not in the correct folder (romcenter_root_dir\datas).

Well in fact, CRC32 is not a strong checksum algorithm. It is not that hard to make a fake or watermarked rom with same CRC32 checksum. An example is that many ISO images released by Microsoft all have CRC32 0xFFFFFFFF. That is why the MD5 or SHA1 checksum should also be introduced into the ROM ...

Fix roms under the path node, not under the game list node.

You can sort your files under the pathnode of RomCenter by game name, and easily delete any one you want.

Hi Eric.

Well, i don't know if you decide to implement this but if you do, it would be nice if you also add an option to let the user decide which algorithm he wishes to use in each DB.
An option for a DB is a good thing. And I think a command item like "SHA-1 check" in right-click menu will be ...

Yes. CRC32-fake roms for MAME exist for a long time, and recently some GBA roms too.


News in nointro homepage:

27-mar-2007

Rising Scum altered #2720, but Sir VG redumped it.
Please note that CRC32 does not change. Only MD5 and SHA-1 do.
Freaks in that crew are reading math books, lol!

and ...

Good news, they are so boring...they made my rss reader full of garbage.

zip

I guess we'll have to blame the mame dev team for setting that name. If Eric has it in mind and remembers to put it in RC3, that would be fine. For now, we'll just have to stay with one red rom in mame v0.106. Hopefully, in the next mame version, the mame devel team will have a more proper name for ...

BTW, this dummy file is created as "317-----.key" by clrmame pro, like Wanderer said in his opinion 2-a.

^_^

data file wrong, or your rom sets wrong (sets working in emulator does not always mean they are correct)
for your instance, maybe data file has bug. neogeo system has a bios set, but some data files do not split it from game sets, such as the data file generated by winkawaks.

0.64? Those old roms are not easy to find I think...

That button is available when a path or some files are selected. N/A when selecting database.

Collect all roms you want, then:
File - Create data file from... - available roms

Thanks for you explanation and announcement of progress of 3.x

For a reference:


A few extracts from MAME0.103's listxml file:

<game name="dynduke" sourcefile="dynduke.c">
<rom name="dd9.jk5" size="16384" crc="f2bc9af4" sha1="9092ebe9dced243c3a7f63198a1180143dd42cea" region="gfx1" dispose="yes" offset="0"/>

<game name="dyndukj" sourcefile="dynduke.c ...

There are more troubles with RomCenter. Some new formats of codes cannot be recognized correctly by RomCenter. ClrMame may also have these new format troubles but it is updated more frequently than RomCenter.

For example, there may be some codes like this:
gamename A,
romname D;
gamename B, clone ...

There are more troubles with RomCenter. Some new formats of codes cannot be recognized correctly by RomCenter. ClrMame may also have these new format troubles but it is updated more frequently than RomCenter.

For example, there may be some codes like this:
gamename A,
romname D;
gamename B, clone ...

wow, Mr. Logiqx, are you better now?

Just use datutil. Logiqx also use it. And what's more, Logiqx is badly-wounded thus there may not be any updates in a few weeks...

Your software sucks. Perhaps you should make it clear that deleting a path from the left-hand list of monitored folders means deleting it from your hard drive? Jesus... It's a f-u-c-k-i-n-g good job that I made a new backup earlier today.

Sheesh....

:x :x :x :x :x :x :x :x :x :x :x
There isn't ...

Before you adding ROM paths you should select a ROM data.
Firstly put all of your data files in Romcenter's "datas" folder, then run Romcenter and select the one you want from the dropdown list which is to the right of toolbar.

nobody here?

When load a data with initial mode of "Merged", it seems that the "rom from" parameter does not work. If change the mode to "Split" or "Un-merged" now, I get the same result that in database part there is no "rom from main set" in any clone game. As a result I think, all zip files in split mode are ...

impossible

Yes, I know of all those errors but I have worked around them accordingly (e.g. ignore invalid parent names and rename ROMs that have CRC conflicts, etc). Kawaks also references non-existent parent but other than that is tidy. All good reasons to use my data files. ;)
An advertisement 8)
Anyway ...