Print

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

[Roman]

https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v031.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html

UI:

added: optionally hide/show roms/disks/samples output via context menu
fixed: remove datasource XML file when hash folder changed (should only happen when XML file was internally created from an exe export)

Core:

added: "available:" filter which limits the machine selection to files you have. You might notice a count difference in total vs filtered even when you got all files. This is based on the fact that a) empty sets are excluded and b) there are clones which are totally included in their parent, so -in split mode- you don't have a standalone file/folder for it. So don't worry about the count.
misc: "file:" filter, in case you work with softwarelist collections, you'd need to prefix single entries with sl-name#pacman (e.g. a2600#pacman) to specify which set you're refering to. Not needed for single sl files or standard dats though.
misc: some earlier cancel returns in fix wrong named disk/sample/rom/machine
misc: dupe output now shows all found paths belonging to a machine
misc: updated spdlog to 1.15.1
misc: limited AUTO thread switch to 25 threads as max (or less depending on your hardware). You can still manually select more or less if you like
fixed: dupes can be listed multiple times
fixed: backups for unneeded folders can create wrong and very long folders due to wrong encapsuling
fixed: backup can miss empty unneeded folders at first scan
fixed: fill-in file from addpath/backup path was removed (when requested) even when fill-in copy failed and you might had a 0 byte new archive
fixed: log pattern in commandline mode

[batigol]

hi roman, there is a mode for make a batch mode in clrmame.exe
like a .bat for all set
or u know if is possible to have unique .xml for all softwarelist and chdlist?

thanks for your great work

[Roman]

Hmm..don't know if I understand your questions correctly...

A batcher is planned for the (far away) future but surely you can write and run a shell script for the commandline version which runs over multiple xml files.
Unique xml files for softwarelist? Either you use a -listsoftware MAME export for all sl data in one file or you simply use the single XML files in MAME's hash folder.
chdlist? What should that be? A standalone datfile for chd files? For what? But most likely such things are floating around in the internet.

[batigol]

Hmm..don't know if I understand your questions correctly...

A batcher is planned for the (far away) future but surely you can write and run a shell script for the commandline version which runs over multiple xml files.
Unique xml files for softwarelist? Either you use a -listsoftware MAME export for all sl data in one file or you simply use the single XML files in MAME's hash folder.
chdlist? What should that be? A standalone datfile for chd files? For what? But most likely such things are floating around in the internet.

Hi roman, sorry for my English.
I think you got it right.
I will try to make a batcher for all the XML software, which would speed up the work a lot since there are almost 700 files.
For CHDs it was the same request so I think it is feasible with them too.

thanks again

[Roman]

Again: For software lists, you don't need 700+ profiles/xml files.

You can simply run a mame -listsoftware based scan. Specify just one folder as rompath. This folder is the parent of the sl folders (a2600,....)

[Roman]

Looks like I broke the showing of empty and complete items in clrmameUI 0.3 ...get a fixed one here: https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v031.zip

[GDT]

Hi Roman,
I switched from clrmameUI 0.2 to 0.31 and scanned my MAME 275 romset.
No problems with roms, but I get problems with software lists scanning: the program exits itselfs with no error message, it completes the scanning phase and exits just a few second after starting the FIX phase (0%).
I had no issues with 0.2.
The particularity is that for software lists I have roms located on my local SSD and CHDs located on a network share on a NAS (SMB). I always had this configuration, also with previous versions of clrmame and mame itself.

What can I do?

[Roman]

Hmm..sounds indeed like a crash. However there weren't that many changes from .2 to 3(1) which fall into that time window of starting fixing...

Could be a corrupt archive or something. Do a scan (without fix option enabled) and check the output which machines require fixing. So you may get an idea which files are affected. Maybe only a few are listed so testing would be not so time intensive...

When fixing is enabled, you can also try to enable log level "trace"...but if it simply shuts down it will be hard to see the log...so maybe you can use Windows' Snipping Tool to record a short movie ;-) So you might get an idea where it crashes.

By the way: there is no difference in roms or software lists internally.

Would be really interesting to find out which file is causing the problem. So would be great if you can somehow minimize the problem and contact me / send me the file in question.

[GDT]

With Fix Issues disabled I was able to end the scan.
It founded varios folder and file to delete, I manually deleted two software lists folders (amiga_a1000 and amiga_a3000) and then I was able to end the scan with "fix" enabled.
In the backup folder I previously had a copy of the amiga_a1000 folder with only 1 file inside "wbenc10" and an empy amiga_a3000 folder.

[Roman]

If I remember correctly there were some amiga sl lists which were renamed/merged to a new list in last MAME release....so the original folders became unneeded and should be moved to the backup folder....before they should form the new folder though....I will have a look if I see something obvious when replaying that scenario.
There is a change in .3 which affects building the backups (which was wrong before ;-)) ...maybe that hit something weird....

Thanks for the feedback.

[Roman]

Hmm...ran some tests with the amiga 274-275 changes but currently I wasn't able to reproduce the problem (or even hit a crash once).

I will double check the backup fixes which came in from .2 to .3 if they can have a sideeffect. The problem back then was that when backuping it created endless subfolders, e.g. if a software list A was unneeded and contained A1 to A100 archives, it created a backup folder A\A1 then A\A1\A2 then A\A1\A2\A3 and so on.....instead of having the files simply stored in A....the fix is like 2 lines of code....and should end in a crash....but again...I will do further checks.

If you are able (or even have time) to reproduce the problem with a small setup, let me know....

[GDT]

I'll try to make some tests this weekend.
Thank you.

[Roman]

That would be great. Actually, when fixing is still at 0% it's still in the "fix missing rom" phase so when files are added to a rompath from either backup, addpaths or from a different set....
The fix order is like:

- per machine
  - fix missing roms, fix missing disks
  - fix wrong named roms/samples/disks
- fix wrong named machines
- fix unneeded

so if fixing was at 0% for you I'd assume it was still in the fix missing part...(e.g. that also happens when a sl like the amiga 1000/3000 is renamed, the folders themselves are unneeded but the files are used for fixing/adding them at the correct place.

[Robee]

Hiya! I'm having this exact same issue, but unchecking fix issues fixes it for me as well.

I'm pretty sure it's failing on fixing missing, at 0%. I can do a full scan without that, but the moment I either try a full scan or a continued scan, it closes itself. I don't think this is folders in the add list not existing, as I removed those and it didn't help.

[Roman]

I tried it several times but never ran into a crash.
If you can somehow repeat this issue with a minimal setup (e.g. just the 2  amiga folders with e.g. 1 file in it), let me know. Most likely I also need details about the backupfolder and the used settings (e.g. sending settings.xml) in general

[Roman]

Would be great to know how your config looks like, so maybe you can send me your settings.xml file. Additionally maybe some information about the sl files themselves...zip/7z/decompressed...