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 / clrmame 0.6 released

« on: Yesterday at 07:37 »

clrmame 0.6 released

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

Core:
- added: dir2dat module
- added: compression level option to set compression level for 7z/zip(zstd). You can select "store", "fast", "normal", "best" (default)
- added: commandline version can use configurations from a toml or ini file
- misc: updated zipclass library with better compression level mapping for zstd (zstd/best is pretty slow by the way)
- misc: updated CLI11 to 2.6.1
- fixed: don't overwrite settings.xml when using cmdline and ui version
- fixed: fixing a special fixable-missing + existing-but-wrongly-named combination within a machine can lead to the same but inverted problem. Unfortunately no message was shown so that the user thinks the files are ok
- misc: greatly improved sha1 prefetcher for solid 7z files
- misc: disabled multi folder selection under WINE since it's causing issues there

UI:
- added: dir2dat module
- added: added compression level and compression method drop down in misc tab
- misc: moved threads/loglevel to new misc tab
- misc: rebuilder: removed zstd / rezip zstd compression options, instead use zip method drop down
- misc: scanner: removed auto detection of compression method, instead use zip method drop down

2

clrmame Discussion / Re: clrmamepro - remove unwanted rom sets

« on: 01 December 2025, 06:59 »

Scanner->SetInformation (lower left corner in the scan results window) opens a dialog where you can enable/disable sets. You already found that, great!
Disabling sets will skip them during a scan operation. If you want to mark them as unneeded (and so they get removed during fixing), there is an option in Scanner->Advanced->Mark disabled sets as unneeded.

For the new clrmame, you can define filters and set the filter mode to "HARD".

3

clrmame Discussion / Re: clrmamepro on Linux with WINE 7zip not removing file contents

« on: 11 November 2025, 18:56 »

if you only use MAME and all MAME software lists (>700) and a handful other dats, you can use it
If you need more profiles...well...then you may need to wait (or use the commandline version via scripts)

4

clrmame Discussion / Re: clrmamepro on Linux with WINE 7zip not removing file contents

« on: 11 November 2025, 18:30 »

...or you simply switch to use the new clrmame ;-)

5

clrmame Discussion / Re: clrmamepro on Linux with WINE 7zip not removing file contents

« on: 05 November 2025, 18:31 »

if more than one file within a 7z file needs to be removed, clrmamepro builds a temporary file in its temp folder called "_filelist.txt" which is a textfile holding the single file names.
It then calls 7z with "d -y -ms=off -mx9 E:\Temp\roms6\roadblst2.7z @E:\ClrMamePro\temp\_filelist.txt"

If it's just 1 file it calls 7z with
"d -y -ms=off -mx9 E:\Temp\archive.7z filexy.bin"  (where archive.7z is your 7z archive and filexy.bin is the file which needs to get removed

maybe Linux/Wine doesn't like the filelist usage....

...use the new clrmame it does not need an external 7z binary...

6

clrmame Discussion / Re: clrmamepro on Linux with WINE 7zip not removing file contents

« on: 05 November 2025, 07:32 »

Actually I wonder that 7z compression does work. In old clrmamepro, an external 7z executable is required for doing write operations on 7z files, i.e. adding or removing files. Since you're in a mixed Linux/WINE world, I thought that calling the (Linux) 7z already fails when compressing files. Since this is working, you may want to double check if the remove operation is correct. Settings->Compressor->7z shows how the 7z executable is called for adding and for removing files. Surely there also might be accessrights involved on your system....

You better switch to the new clrmame which does not require an external 7z binary.

7

clrmame Discussion / Re: Questions...

« on: 30 October 2025, 07:13 »

Well, thank you for reporting 'simple silly glitches' 9th of Oct...2 days after mine.....

8

clrmame Discussion / clrmamepro 4.050

« on: 29 October 2025, 08:15 »

Believe it or not....there is a small clrmamepro update (https://mamedev.emulab.it/clrmamepro/#downloads)

4.050
fixed: xml parser issue with CDATA or comment ending in the same line
fixed: some device clones parent roms might not get marked as wrong placed
fixed: unneeded files in sample parents aren't detected

9

clrmame Discussion / clrmame 0.5.2 released

« on: 16 October 2025, 16:38 »

clrmame 0.5.2 released

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

Core:
- fixed: temporary path getter can fail leading to unpacked files in rom, sample or last used path
- misc:  updated spdlog to 1.16.0
- misc:  scanner, removed fileAccessible test for unneeded files in rompath, it's pretty slow and normally all files within rompaths should be accessible anyhow. If you now get warnings, please let me know

10

clrmame Discussion / Re: clrmame 0.5.1 released

« on: 11 October 2025, 07:48 »

Thanks for reporting it

11

clrmame Discussion / Re: Unwanted file being created

« on: 09 October 2025, 18:18 »

finally found the cause of it...

https://www.emulab.it/forum/index.php?topic=9893.msg27568#msg27568

12

clrmame Discussion / Re: Questions...

« on: 09 October 2025, 18:16 »

ok....knowing the problem it was also easy to produce a chd file appearing in your sample path and s7.z7 from sauro (see https://www.emulab.it/forum/index.php?topic=9934.0) appearing your rompath.

Ok...what's happening? Well, if you have an archive in an archive in your addpaths or the backup folder (and if that one is ticked as "incl. as addpath), clrmame decompresses it to a tempfolder. In the sauro case your have s7.7z (a file not an archive) inside a zipfile, but until you check it you don't know if it is a valid archive. So, if you got a look-a-like archive inside an archive, clrmame unpacks it to a temporary folder which is a folder inside %TEMP% (or you specified an own one). By default it takes a subfolder path which is named like the file, so e.g. "sauro". If that folder already exists, it adds a random number and tests again....and again....and again...up to 10 times. You would think that randomly added values should be fine...well...yes...if the seed is initialized correctly....and in that case it wasn't, so during one clrmame session you get the same numbers again and again, which lets the tempfolder determination fail after a while (it works for sauro 10 times....so yeah...took a time to repeat it). If the 10th tempfolder directory failed, it wasn't able to to get a good folder to unpack and unfortunately it didn't produce an error there but continued and took an empty string as prefered unpack folder....which is the current path. So depending on what the current path at that point in time was (either rom, sample or clrmame application path), it unpacked files there.

So you see....to trigger this, you needed archives in archives in your add or backupaths, plus you needed to scan > 10 times to get the temp dirs created....

wow...finally solved this mystery. Guess I will do a 0.5.3 version for that one, even if 99,9% of user never ever experienced something like that....

13

clrmame Discussion / Re: Questions...

« on: 09 October 2025, 07:41 »

Wow....pretty old topic....but shorty after releasing 0.5.1 I actually found a repeatable case for 3) "magic appearance of files in the samples folder".

I finally found out what the reason is....so stay tuned for a 0.5.2 I guess.

Actually, the "sample" folder is just used because it was the last used "current" directory. There is a problem when temporary unpack folders already exists and creation of a new random one fails....and it unfortunately returned an empty string where it should return a full temporary path name and so, files get unpacked into the current folder....which in your case is the samples one.....

Actually, https://www.emulab.it/forum/index.php?topic=9934.0 can be related to that one, too...however I wasn't able to reproduce it (yet)

14

clrmame Discussion / clrmame 0.5.1 released

« on: 08 October 2025, 17:38 »

clrmame 0.5.1 released

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

UI:

- added: context menu options to take over compatible settings from current Scanner to Rebuilder 'profile' and vice versa. Option is only available if no scan (or rebuild) job is currently running. Not all options can be taken over, mapping is described in the documentation
- added: context menu options to link Scanner and Rebuilder, so that if you switch the XML/EXE in one, it will select the same in the other module (XML/EXE needs to be setup in both first, e.g. with upper mentioned take over option). This only works if the other module is currently not running.
- misc:  combobox, hold CTRL while clicking X additionally removes current entry from list when clearing input, no more empty entries in the drop down list, use X
instead if you want to have an empty selection

Core:

- fixed: 7z, addFiles(from, to) was limited to unique from files, i.e. multiple additions from the same source (a->b, a->c) skipped creating files
- fixed: rebuilder, deletion of rebuilt unpacked files doesn't work when creating archives
- fixed: rebuilder, creation of some destination files is skipped when a matched file is used multiple times and is listed more than one time in the source machine xml
- misc:  additionally give machine name when renaming roms/disks/samples due to errors in dat

15

clrmame Discussion / Re: clrmame 0.5 released

« on: 29 September 2025, 07:00 »

Ah thanks...I see the problem....actually the removal of unpacked files only works if you rebuild them to unpacked


...Fixed in next version...

16

clrmame Discussion / Re: 1G1R mode for MAME DATs?

« on: 29 September 2025, 06:32 »

Well, since you said you're working on building up a 1g1r datfile, I assume you can
If you need an idea I think you can take a peek at any existing datfile with languages/regions/releases elements out there.....

17

clrmame Discussion / Re: 1G1R mode for MAME DATs?

« on: 28 September 2025, 13:52 »

The datfile needs "release" elements for supporting 1g1r mode.

18

clrmame Discussion / tiny wip

« on: 24 September 2025, 18:25 »

If you're interested in some wip....

UI:
- added: context menu options to take over compatible settings from current Scanner to Rebuilder 'profile' and vice versa. Option is only available if no scan (or rebuild) job is currently running. Not all options can be taken over, for mapping see readme.md
- added: context menu options to link Scanner and Rebuilder, so that if you switch the XML/EXE in one, it will select the same in the other module (XML/EXE needs to be setup in both first, e.g. with upper mentioned take over option). This only works if the other module is currently not running.
- misc:  combobox, hold CTRL while clicking X additionally removes current entry from list when clearing input, no more empty entries in the drop down list, use X instead if you want to have an empty selection


Core:
- fixed: rebuilder forgets to add some destination files when a matched file is used multiple times and is listed more than one time in the source machine xml
- misc:  additionally give machine name when renaming roms/disks/samples due to errors in dat


To sum it up, one important rebuilder fix and some nice to have UI options.....still waiting for some feedback for 2 posts here on the board, unfortunately not repeatable things and not enough information was given....so maybe I do a 0.5.1 release soon...

19

clrmame Discussion / Re: clrmame 0.5 released

« on: 17 September 2025, 05:58 »

What exaclty are you doing? I mean, which datfile are you using? Which files are you talking about in detail, how they are stored? Are you talking about the rebuilder (since you say "input folder")...I need a little bit more information to work with. Is it repeatable? What settings do you use, etc..etc..etc..

20

clrmame Discussion / Re: Unwanted file being created

« on: 15 September 2025, 06:34 »

Do you have any update on this?
I did various test but unfortunately I'm not able to reproduce this. So if you can repeat it, please let me know the following:

- are you using an official MAME as data source or a custom datfile?
- are you using 7z or zip files
- any other settings changed (addpaths, patterns, filters, etc)
- what is your used merge mode
- how does your original saurop and/or sauro archive looks like (what files / checksums are in it)
- step by step instructions to repeat it (but I guess it's just a scan with the fix option enabled)