Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[funkmata]

Hello,

clrmamepro version: 4.044d
DAT file Source: ARMAX MAME Dats 0.244 | https://www.mameguide.info/MAME_(20220525).7z
DAT file: MAME - ROMs (v0.244_XML).dat
Missing Set: loveber3cn
Scan Options: <see scan_options.png attachment>
Scan Results: <see scan_results.png attachment>
segasp.zip Contents CRC: <see segasp.png>
loveber3.zip Contents CRC: <see loveber3.png>

This isn't really a big deal, but I've been trying to figure out over the past few years why the "loveber3cn" set is listed as missing in my scans.  I found a similar thread (https://www.emulab.it/forum/index.php?topic=4395) which alludes to this being fixed, but haven't seen it working in my case with the latest releases.

I understand the "loveber3cn" set requires the CHD, "segasp" BIOS, and the "loveber3" game as its parent.  However, I have CHDs unchecked, the "segasp" BIOS, and the "loveber3" ZIP available; so the set should be skipped instead of marked as missing.  From my understanding of the datfile, the "loveber3cn" set (without CHD) is just a merger of multiple files from both the parent game and BIOS, so there shouldn't be anything listed as missing since all the files (w/correct checksums) are in either segasp.zip or loveber3.zip (see segasp.zip and loveber3.zip attachments).

<game name="loveber3cn" cloneof="loveber3" romof="loveber3">
    <description>Love And Berry - 3rd-5th Collection (China, Ver 1.001) (MDA-C0071)</description>
    <year>2010</year>
    <manufacturer>Sega</manufacturer>
    <rom name="epr-24236a.ic50" merge="epr-24236a.ic50" size="2097152" crc="ca7df0de" sha1="504c74d5fc96c53ef9f7753e9e37fb8b39cb628c"/>
    <rom name="epr-24328.ic50" merge="epr-24328.ic50" size="2097152" crc="25f2ef00" sha1="e58dec9f171e52b3ded213b3fcd9a0de8a438076"/>
    <rom name="epr-24328a.ic50" merge="epr-24328a.ic50" size="2097152" crc="03ec3805" sha1="a8fbaea826ca257be0b2b86952f247254929e046"/>
    <rom name="mb_serial.ic57" merge="mb_serial.ic57" size="128" crc="e1e3c009" sha1="66bc636c527389c3338f631d78c788b4bd4e93be"/>
    <rom name="mb_eeprom_exp.ic54s" merge="mb_eeprom_exp.ic54s" size="128" crc="947ddfad" sha1="832a3db097af680d1d0eb9451b4650565f0cf8c7"/>
    <rom name="317-0446-com.ic15" merge="317-0446-com.ic15" size="2048" crc="9e519dc6" sha1="69a1efc81c9dc44fcb8fc9c17bd7f879d3259950"/>
</game>

An example of a similar set that isn't listed as missing is "dinokich" which also merges all of its files from its parent "dinoki25" and the "segasp" BIOS.

<game name="dinokich" cloneof="dinoki25" romof="dinoki25">
    <description>Konglongwang - D-Kids VS Alpha Yaosai (China, Ver 2.501) (MDA-C0081)</description>
    <year>2010</year>
    <manufacturer>Sega</manufacturer>
    <rom name="epr-24236a.ic50" merge="epr-24236a.ic50" size="2097152" crc="ca7df0de" sha1="504c74d5fc96c53ef9f7753e9e37fb8b39cb628c"/>
    <rom name="epr-24328.ic50" merge="epr-24328.ic50" size="2097152" crc="25f2ef00" sha1="e58dec9f171e52b3ded213b3fcd9a0de8a438076"/>
    <rom name="epr-24328a.ic50" merge="epr-24328a.ic50" size="2097152" crc="03ec3805" sha1="a8fbaea826ca257be0b2b86952f247254929e046"/>
    <rom name="mb_serial.ic57" merge="mb_serial.ic57" size="128" crc="e1e3c009" sha1="66bc636c527389c3338f631d78c788b4bd4e93be"/>
    <rom name="mb_eeprom_exp.ic54s" merge="mb_eeprom_exp.ic54s" size="128" crc="947ddfad" sha1="832a3db097af680d1d0eb9451b4650565f0cf8c7"/>
    <rom name="317-0408-com.ic15" merge="317-0408-com.ic15" size="2048" crc="f77c49dc" sha1="e10173bbbd5930ed159cec9a7dba308e2a3f3c43"/>
</game>

Is there anything I'm missing?

[Roman]

You need to differ between the meanings of the check options "sets" and  "chds", "samples","roms".

The set check checks if the set is available or not. The chd check would only moan about wrong named or missing chds inside the set. A set is a collection of roms and/or samples and/or chds. The rom check would tell you if a rom inside a set is wrong named, wrong checksum etc....

The mentioned set only cosist of shared parent roms but it uses an unique chd. So actually you'd need a rompath subfolder named after your set with the chd in it.
Since you're missing that chd, the set is missing and so the output is right.

[funkmata]

Sorry, I should have clarified that I don't have any CHDs for any sets.

So what you said makes sense, but I don't understand why loveber3cn is the only set with a missing CHD shown as missing.  I don't have any CHDs and no other set is marked as missing.  For example, the "dinokich" set also consists of just its parent game "dinoki25", the segasp BIOS, and its own unique CHD file that I do not have.  However, that set is not marked as missing when I perform a scan.

[Roman]

You're right, dinokich and others should also appear then. Why it doesn't do it for you...well....hard to say without knowning all your settings but most likely you have an empty dinokich folder in one of your rompaths which fools the set check. If the set check finds a folder or an archive with the name, the set check will be ok....an enabled chd check will of course tell you that the chd itself is missing though.

[funkmata]

Actually, I take back what I said earlier.  Since the dat file I'm using is ROMs-only and doesn't include any CHD information, how would clrmamepro know that the CHD (and hence the set) is missing in the first place?

edit: I'm positive there isn't a "dinokich" subfolder in my ROM-path.

[xyz@server all]$ find ./ -name "dinokich" -print0
[xyz@server all]$

[Bad A. Billy]

When CMP goes back to check the parents status might it bypass(internally) the chd rule and look for the chd in the parent to see if IT is complete?
Then, without its chd, CMP would mark the parent as missing/incomplete, and without a chd or any other unique files to fall back on, lovber3cn cannot be complete or even there?
Just a thought...

[funkmata]

Regarding your proposed scenario, the "dinokich" set is almost exactly the same.  It has a unique CHD that is distinct from its parent/clone "dinoki25".  There is no dinokich.zip file nor is there a dinokich folder, but clrmamepro does not list this set as missing.  I think this rules out what you've suggested, but thanks for thinking about it.

I'd tried something similar in the past: copying the contents of loverber3.zip and segasp.zip into loveber3cn.zip and letting clrmamepro sort it out to no avail.  Anyway, I tried it again just now and clrmamepro removed the contents of loveber3cn.zip which, ultimately, led to clrmamepro deleting loverber3cn.zip entirely.  On the subsequent scan clrmamepro showed the same result as before--the "loveber3cn" set is missing.

The only conclusion I can draw without additional logging is that there's a hard-coded exemption in clrmamepro for the loveber3cn set or something similar, but this seems unlikely.  I believe this issue originated around the release of MAME 0.216 (if you google "loveber3cn emulab" w/o quotes there's a forum result listing the release in the third result) which was released November 2019.

[Roman]

No set behaviour at all is hardcoded.
You said you're using a datfile without disks. Can you send me that one please.

[funkmata]

Sure.  You can download the datfile 7z from this URL: https://www.mameguide.info/MAME_(20220525).7z

I'm using "MAME - ROMs (v0.244_XML).dat" inside of that archive.

[Roman]

Thanks, due to weekend/holiday I will have a look at it later this coming week

[Roman]

Found your loveber3cn problem.
It normally doesn't pop up due to the unique chd for that clone. Since you're using a dat which does not use chds, a different issue is visible now.
It's gonna be fixed with the next release.

The reason...oh well....there's a flag which sees if a set does not need to exists (e.g. only devicerefs, only parent roms in a clone, only nodumps, etc) and that flag was set falsely in that case since loveber3cn references one bios file which its parent did not use at all...etc...blablab.... ;-)) Anyhow....it will be fixed.

[funkmata]

Awesome.  Thanks for looking into it and figuring it out, Roman.

[Senpai7878]

Found your loveber3cn problem.
It normally doesn't pop up due to the unique chd for that clone. Since you're using a dat which does not use chds, a different issue is visible now.
It's gonna be fixed with the next release.

The reason...oh well....there's a flag which sees if a set does not need to exists (e.g. only devicerefs, only parent roms in a clone, only nodumps, etc) and that flag was set falsely in that case since loveber3cn references one bios file which its parent did not use at all...etc...blablab.... ;-)) Anyhow....it will be fixed.

Hi Roman I tried to send you a DM but it isn't letting me and it also doesn't seem to let me start new threads? Not sure if it's because I have just registered.

I hope it is okay for me to message you regarding some help - I have tried for about 10 hours now across multiple days and I can't get something on MAME to work - I noticed you replied to a thread regarding loveber3cn and I hope you may be able to help me with it. I am coming to you as the last resort.

If it is okay, I will give you the TLDR:

I'd like to play loveber3cn, specifically the Chinese version as I grew up playing it.
I have the latest version of MAME installed.
I have followed the Arcadeitalia's list of REQUIRED FILES for this game.
(segasp.zip, loveber3cn.zip, loveber3cn_mda-c0071.chd).
I have placed the two ZIP folders along with the .chd file inside my roms folder for MAME
In my roms folder, I also have loveber3.zip along with a folder called loveber3 with the mda-c0042.chd
I also have loveber3cn.zip along with a folder called loveber3cn with the mda-c0071.chd

I have ensured that MAME's ROMS directory is correct.

When clicking on the game in MAME, I get the message:

Required ROMS/disk images for the selected system are missing or incorrect etc etc

I am completely new to this so I've really struggled to get to grips with sorting this out but I eventually found out how to use CMD, navigate to the folder, and use the command "mame.exe loveber3cn" - I am told that 317-0446-com.ic15 has WRONG CHECKSUMS in the CMD but the game launches but gives me a red text box error:

EXPECTED: CRC(9e519dc6) SHA1(69a1efc81c9dc44fcb8fc9c17bd7f879d3259950)
       FOUND: CRC(60f56bf2) SHA1(35e697aca7213e3fb1ebe75bb8991b1b992af6d9)

The red text box error states:
THIS SYSTEM DOES NOT WORK. The emulation for the system is not yet complete.

Can I ask if there's anything at all I can do? Or does the game straight up not work in MAME? and I just need to wait until it is compatible?

I'm not sure if I've messed up any steps, or if it isn't user error.

Really appreciate any insight you can give and sorry for taking up your time - it really is a last resort, I promise.

[john iv]

You don't have the right ROMs, and the game is flagged as not working.

[Senpai7878]

I receive the same red-text box error message as you which I assume means I have the correct ROMs.
I've tried demul but they don't seem to have a selectable option to play the chinese version of the game, only the USA ones (which work).

I know it's possible to play this game as there exists footage online.
Really stuck for solutions, I thought out of anything it would work on MAME - Open to any suggestions if you have any please?

Is it possible to "trick" demul into running the loveber3cn instead of lovebery/lovebero/loveber3?
I have attached a screenshot to show that loveber3cn does not exist on demul but the others do.

thank you for your time

EDIT:

I have tried Flycast and the game seems to launch but gets stuck on a black screen that says "ERROR 100 RFID READER NOT READY"

This is the closest I've gotten so far with the game actually launching.
I have spoken with the Flycast dev and they said that the Chinese editions use a completely different RFID system and it currently isn't emulated at this moment - I assume they are referring to not being emulated on Flycast

So close yet so far

[Roman]

EXPECTED: CRC(9e519dc6) SHA1(69a1efc81c9dc44fcb8fc9c17bd7f879d3259950)
       FOUND: CRC(60f56bf2) SHA1(35e697aca7213e3fb1ebe75bb8991b1b992af6d9)

Clearly says you don't have the right rom for the mentioned one.

But it doesn't matter since the game is not emulated in a way in MAME that you can use it.
So even if you have the right rom, it won't won't.

Besides of this, MAME emulation issues or Flycast or DEMUL topics do not belong to this forum.