EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

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.

Messages - Devvy

Pages: [1]
1
clrmame Discussion / Re: clrmame 0.4 released
« on: 21 April 2025, 11:47 »
There isn't really a stats screen but the log output says a bit about the number of complete/empty/partly wrong machines
Would it be hard to add one like clrmamepro, I've been tracking my changes since 1998 for sets/roms/samples/CHDs.
please sir?

2
clrmame Discussion / Re: clrmame 0.4 released
« on: 21 April 2025, 07:48 »
https://mamedev.emulab.it/clrmamepro/binaries/clrmame_v04.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html

UI:

- scanner, fixed showing of empty and complete machines
- scanner, fixed showing of non rom/sample/disk related machine/file/folder issues

Core:

- added: read/write support for zstandard compressed zip files
- rebuilder, two zstd compression methods added, newly created/added files   will use it (existing destination files which don't get replaced won't be   updated). Source files which don't use the set compression method won't be taken into account when checking for a direct archive copy
- scanner, automatically detects if you prefer zstd or deflate compressed zips and uses the preferred setting the case that new files are added.
- with both, rebuilder/scanner you can theoretically end up with zip files which have files in it with different compression methods. Rebuilder: if you
  rebuild to existing files, scanner, if you already have a mixture of archives using different compression methods.

- added: scanner, reporting 'wrong' chd version. Current expected version is 5, warning is not shown for baddumps. Version and baddump warning can be altered in settings.xml

- misc:  changed the behaviour of devices which have romOf dependencies. When fully merging such devices they are now handled like parent/clone machines. On the one hand it makes sense since there are merge attributes indicating that such sets belong together but there are also cases where they are distinct. This is now aligned with clrmamepro, but still something which might need further discussion

- misc:  updated cli11 to 2.5.0
- misc:  updated spdlog to 1.15.2
- misc:  updated bit7z to 4.0.10

- misc:  scanner, using absolute pathnames for error reporting in path scan
- misc:  scanner, only trace-log machines with issues in fixing phase
- fixed: scanner, typo "uneeded"
- fixed: scanner: detection of empty but unneeded folders in archives
- fixed: scanner, backup of chds in software list collections can fail
- fixed: scanner, archives which match a valid rompath subfolder name (e.g. softwarelist name via pattern or automatically) are falsely iterated like a folder instead of listing them as unneeded (wrong placed)
- fixed: crash on rom definitions without a crc
- fixed: filter enrichment might miss sampleof dependencies
- fixed: doing archive backups from a folder and backup archive already exists creates a new archive instead of merging files in
Thanks for the great new version, took the giant step for mankind and moved from clrmamepro.
Scanned and fixed alot (Full mode), didn't break anything. cheers for that.
The old clrmamepro would give you a summary after scanning total sets/missing sets etc, is there a summary screen possible, or these results stored/shown somewhere else?
Thanks for years of keeping our ROMS in check ;)

3
Thank you for your help..
I will experiment with both apps, see what effects is has on my mame collection. I've nearly all .. but a few CHDs.. and laserdisc games..
Cheers

4
Would it be safe to run Clrmame with 'fixes'. looking at the Clrmamepro in scanner mode, I've got Merged Sets option.
I'm not sure whether to continue with clrmamepro or clrmame?
PS where is that "full merge mode -> hash collision name" option please?
PPS should I be running this scan in standalone to get the right results?
Thanks

5
Thanks for the new great version of Clrmame. But I think I'm doing something wrong. Clrmamepro doesn't report any of the errors that Clrmame is finding. Please help if possible.
So as an example, 88games reporting incorrect names.
P2 clrmame dump
P1 zip archive
P3 spludlow rom info
Thanks for the great Clrmamepro and now Clrmame

6
clrmame Discussion / Re: delta chds, cmpro test version
« on: 29 October 2023, 05:52 »
Something new from delta chds for a moment. Clrmame is quitting when it's trying to move freestanding *.chd files into a subdirectory structure.
I decided to convert from split to merged storage. I moved my CHDs out of their \roms\blah directories and put the raw *.chd files in the \roms directory.
In the past when I've done this and run a scan, clrmame will find them and move them to their created respective subdirectories.  Instead of doing that now it just quits out of clrmame.

The scan is also not finding the the CHDs in the add-folder.  Rebuild does not move the CHDs over from the add-folder either.  I purged my clrmame setup and re-downloaded and started from scratch just in case it was an errant setting, but same problem.
Was about to post the same thing!

7
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 12 August 2022, 06:22 »
Just to let you know, after I did an uninstall and did a fresh install, this problem has gone?
So thanks for the help but obviously was my setup.
Thanks for your great program

8
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 11 August 2022, 13:56 »
Will try fresh install from scratch, let's see what happens, thanks.

9
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 09 August 2022, 10:30 »
Yes, always import from the MAME binary (MameUI) each time new one released, clearing previous cache.
No don't use softwarelists.
Thanks again for your support.


10
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 09 August 2022, 08:23 »
I've checked all the folders I use, which is just one for ROMS and a couple for Add-paths, only 1 zip exists with correct info as you mentioned below. (arb pic)
Cleared my cache and did a reload of mame 0.246 and then a full scan with 2nd picture (scan pic)

11
clrmame Discussion / Re: Cmpro "misplaced a romset" !?
« on: 03 August 2022, 07:58 »
Move them elsewhere and let the rebuilder readd them with recompression enabled.
So I've had this issue since 4.045 and tried to fix.
same settings ;
My clrmamepro setup:
* Prefer merged sets
* Scan sets/ROMs/samples/CHDs
* Check and fix ALL types (Missing, Case, etc.)
* Separate BIOS sets is checked in (Rebuilder and Scanner)
Delete ARB.ZIP
Run 'New Scan'
'Set ARB V2 Sargon 4.0' 'do you want to add missing ROM'
Yes
Recreates ARB.ZIP in ROMS folder
Move
ARB.ZIP to add-paths folder
Run rebuilder, rebuilds ARB.ZIP to ROMs folder
Run scanner, 'misplaced ARB.ZIP' comes up again
'Set ARB V2 Sargon 4.0' 'do you want to add missing ROM'
and repeat .....
what's wrong. how did Paultup fix it. I tried every fix mentioned here.
Help



12
clrmame Discussion / Re: Merged Sets Scans
« on: 11 January 2022, 10:45 »
Thank you for your support ;)

13
clrmame Discussion / Re: Merged Sets Scans
« on: 10 January 2022, 11:01 »
Thanks again, I think I'm having a mental breakdown with the scanner and how it works.
I see your point in selecting anything other than "Merged" is not achieving anything different, except when I click "Miss" or "Have" list, then the list will differ but not "How" I thought it worked.
I've traditionally used these to 'find' missing sets, but I've now realised that I've been using it incorrectly ... for a long time.

I've attached some screenshots just to check I'm not going crazy.
1. settings
2. advance settings
3. systems, I always click "Auto-assign"
4. stats.
5. rebuilder

Cheers

14
clrmame Discussion / Re: Merged Sets Scans
« on: 09 January 2022, 07:33 »
1stly, Thank you for the best ROM manager... that I've used forever.
2ndly, thank you for your reply.
I've always had merged sets as the build/rebuild/scan option.
I thought that my merged sets were always complete until I used the 'non-merged' scan.
I've figured that I will just need to manage the clones/bootlegs via the 'non-merged' scan and track the missing with an excel spreadsheet (which I do now anyway), comparing the Mame32 audit window with the miss list.
PS I always use Miss / Have to keep upto date.
Thanks again
Live Long and Prosper

15
clrmame Discussion / Merged Sets Scans
« on: 08 January 2022, 06:50 »
So after nearly 20 years of mame use, and what I "thought" I was doing right was that I discovered that my so called "Merged" sets are actually missing ROMs.
Only by accident after trying to play Slapfight Bootleg Set1, which is actually part of m1albsq parent set.
So my question is that since I've got "Merged Sets" selected on scanner, did does not find any missed clones/bootlegs when I do a "Miss List".
I then tried selecting "Non-merged" to get a full miss list, and got a huge missing list. If I then run a "Fix all" scan, it starts breaking all the roms up into non-merged sets, and created a mess of a ROM folder.
So back to square 1 and the main reason for my question is ;
How to you scan using "Merged" Sets for ROMs that are actually missing clones/bootlegs? Because "Miss List" is not capturing any of these.
Help please

Pages: [1]

Page created in 0.072 seconds with 21 queries.