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

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

clrmame Discussion / Re: clrmame 0.7.0 released

« on: 28 April 2026, 07:12 »

I try to repeat that scenario...0.7.0 had no changes regarding to "missing but fixable" though....but surely I will have a look
..or do you have a repeatable scenario which can be zipped up ;-)

Emailed you.

2

clrmame Discussion / Re: clrmame 0.7.0 released

« on: 28 April 2026, 05:54 »

Note the 'fixable via' files are no longer actually on the desktop as they were removed as part of the failed rebuild. Weird.

3

clrmame Discussion / Re: clrmame 0.7.0 released

« on: 28 April 2026, 05:52 »

Looks like 7 is not fixing for me after a scan w/ the files on my desktop.  It removed them but didn't add them to my roms and then told me they were fixable.  I ran the last 6.x version and it worked fine, removed them and added them to the roms.

4

clrmame Discussion / Re: clrmame 0.6.3

« on: 03 March 2026, 21:06 »

I guess it's better to just report on the issue in the log vs. trying to fix it, otherwise we wouldn't know to alert the devs to the duplication after the first clrmame run.

5

clrmame Discussion / Re: clrmame 0.6.3

« on: 03 March 2026, 20:32 »

Having this conversation at Bannisters in the shoutbox:

John IV: Looks like some clrmame complaints on identically named roms w/ diff. hashes today, exprraidbl and fstation7.

John IV: Osso and StonedDiscord.

hap: If a cloneset has a certain rom label exactly the same as the parent or sibling set, it's not a MAME problem. AFAIK clrmamepro doesn't have an issue with it either since it can rename the files when converting to a merged set

hap: If it's in the same romset, then yes it's a bug.

John IV: The current version of clrmame doesn't fix these two issues upon encountering them. When it's been hit previously it did require a source level alteration. This is w/ merged sets and the clones in subdirectories of the zips. I'll ask Roman.

6

clrmame Discussion / Re: Renamed, but where?

« on: 11 September 2025, 19:00 »

Nice, thanks Roman. Thankfully these are pretty rare occurrences, though I've spotted a couple in the last few months. ;-)

7

clrmame Discussion / Re: Renamed, but where?

« on: 10 September 2025, 07:24 »

Right.  But how would I have known it was in jhg3d.  That's the information I need surfaced so I can report it to MAMEdev.  I don't see the machine name, unless I'm overlooking it. Somewhere outside the UI? It's one of Ivan's, I sent him a DM on Bannister's.  He's on it.

8

clrmame Discussion / Renamed, but where?

« on: 10 September 2025, 02:31 »

Hi Roman, I'm seeing this rename error in the logs on every run.  It might be nice to include the containing zip or file that the renamed ROM is coming from so I can go double-check it or have a DEV rename it properly in the source.

9

clrmame Discussion / Re: clrmame just closing

« on: 16 April 2025, 04:41 »

Just to close this off, Robbie Fresco also fixed the missing crcs today so the current version of clrmame works again.

10

clrmame Discussion / Re: clrmame just closing

« on: 15 April 2025, 07:03 »

Sent you a link to the pertinent files via email.

11

clrmame Discussion / clrmame just closing

« on: 15 April 2025, 01:22 »

Hi Roman, seems within the last 24 hours or so when I run clrmame on my exported mame.xml it starts to build the full view and then closes without an error.  Very odd.  The softwarelist.xml scan is fine, but not the mame one.  My mame.exe is tip of master on github.  I'm able to import the .exe's xml into my front-end as normal so I don't think it's malformed?  No errors or logging.

[Update] Crashes with a fresh settings, also crashes reading from mame.exe vs. my exported mame.xml.
[Update] Old clrmamepro 4.049 works w/ this mame.exe.

mame -version
0.276 (mame0276-217-gf6d743b9378)

12

clrmame Discussion / Re: Scan deleted my softwarelist.xml

« on: 25 January 2025, 20:03 »

Cool, thanks for responding to wacky edge cases. ;-)

13

clrmame Discussion / Re: Scan deleted my softwarelist.xml

« on: 25 January 2025, 17:29 »

Thanks, will give it a go.  Did you find something?

14

clrmame Discussion / Re: Scan deleted my softwarelist.xml

« on: 24 January 2025, 18:31 »

Ok, I think I understand.  I can envision a scenario where this may be occuring with me:
1. build mame getting its \hash files as part of my chron job..
2. run scanner, no errors. leave clrmame open.
3. build mame and get its \hash files a second time.
4. run scanner again, hit this issue (do the \hash contents need to change or is a timestamp change sufficient to cause a re-loading?)

So if we're hitting the old export file is removed step, the reimportation in this case is ignoring my filter, and where does the reimportation file live? I have to re-generate the softwarelist.xml manually when this happens.

15

clrmame Discussion / Re: Scan deleted my softwarelist.xml

« on: 24 January 2025, 17:51 »

Nope, not touching those files.
I build mame, bring over all the git \hash contents to its directory then run the mame -listsoftware and run clrmame.  This isn't 100% repro.

Non standard settings, for my filter I'm using (see attached):

It just worked on my morning build, but as I've said I've watched it happen about 4 times throughout the day.  When the scan kills the softwarelist.xml file in the directory, it is not recreated there by the system (I put the softwarelist.xml in the same directory as clrmameui.exe) during the scan.

16

clrmame Discussion / Scan deleted my softwarelist.xml

« on: 23 January 2025, 22:49 »

Hi Roman, I've seen this a few times now where a scan is deleting the underlying software.xml file during its scan and failing.
1. Manually output mame.exe -listsoftware > softwarelist.xml
2. Point scanner to softwarelist.xml
3. Observe directory from step 2.
4. Run scanner on softwarelist.xml.
5. softwarelist.xml disappears from directory.
6. Log of scan shows a bunch of 'adding hashes'
7. End of log says, can't parse the softwarelist.xml as it's not there

Any code path that would actually delete the used stand-alone softwarelist.xml?  Attaching log file.

Nightly build from top of tree, x64 Win11.

17

clrmame Discussion / Re: a nightly cmpro...

« on: 11 December 2024, 20:27 »

Thanks Roman, I like the way the new tools handle it.  Just mentioned the different behaviour in the classic version in the event there might be people that use it to 'double check' the new tools' results.

18

clrmame Discussion / Re: a nightly cmpro...

« on: 08 December 2024, 05:28 »

Hmm, have some different results w/ the same .exe:
1. 'classic' cmpro is flagging these hitachis as not being in their parent.
2. new clrmameui does not complain of the initial problem; but it does complain *after* I let cmpro 'fix' its issues in step 1. (screenshot)

19

clrmame Discussion / Re: a nightly cmpro...

« on: 08 December 2024, 05:19 »

Thanks; keeping it around for delta chd detection/creation.

20

clrmame Discussion / Re: clrmame (scanner 0.08.1, rebuilder 0.15.1) released

« on: 04 December 2024, 18:10 »

Guess the warning confused me with its verbiage of 'sample-set only was added'. I took that to be some sort of fixing that would prevent the errors in the future, and when I re-ran the scan in memory and didn't see the errors it got my hopes up.

Oh, 1 second? I hadn't noticed that result, heh. The new caching speed is very nice for the usual multiple checks and runs.