221
clrmame Discussion / Re: CHDMAN producing damaged delta CHDs on a few sets.
« on: 23 February 2024, 08:51 »
I haven't spent any time on convertig chds to deltas...so..nope..
- 26 March 2025, 10:39
- Welcome, Guest
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.
222
clrmame Discussion / Re: CHDMAN producing damaged delta CHDs on a few sets.
« on: 23 February 2024, 07:08 »
well....haven't looked into detail yet but in general cmpro only reads the chd header and compares the hashes....a decompression error can only be found if Scanner-Hash&CHD-CHD MD5/SHA1+Decompress CHD & check SHA1/MD5 is checked.
So that is most likely the reason why cmpro doesn't come up with a warning by default...the header of the bad file seems to be valid.
Seems to me another chdman issue regarding delta chds.....one where the creation doesn't exit with an error message but the produced data is bad.
So that is most likely the reason why cmpro doesn't come up with a warning by default...the header of the bad file seems to be valid.
Seems to me another chdman issue regarding delta chds.....one where the creation doesn't exit with an error message but the produced data is bad.
223
clrmame Discussion / Re: delta chds, cmpro test version
« on: 22 February 2024, 20:49 »
You need to use https://mamedev.emulab.it/clrmamepro/binaries/cmpro_deltaverify.7z
which is rock stable
Real life job currently takes all my time.....
which is rock stable
Real life job currently takes all my time.....
224
clrmame Discussion / Re: How can I achieve completely independent rom sets with clrmamepro?
« on: 10 February 2024, 18:31 »
Full merged, split merged and standalone will be the future. Nothing else, but of course you can achieve any possible combination by using modified datfiles.
225
clrmame Discussion / Re: How can I achieve completely independent rom sets with clrmamepro?
« on: 09 February 2024, 15:04 »
New rebuilder/scanner already got the "standalone" mode.
226
clrmame Discussion / Re: delta chds, cmpro test version
« on: 30 January 2024, 10:39 »
well....guess we all have to wait till MAME team fixes the chdman issue sooner or later
https://github.com/mamedev/mame/issues/11675
https://github.com/mamedev/mame/issues/11675
227
clrmame Discussion / Re: clrmamepro 4.048d released
« on: 23 January 2024, 17:06 »
I've contacted the author of ZipArchive and there is a good chance that zStandard will be included.
Don't know if I add a workaround (maybe via unrar.dll, have to check that) before that but I doubt that users need the support for zips (chds come for free...) so quickly...
Don't know if I add a workaround (maybe via unrar.dll, have to check that) before that but I doubt that users need the support for zips (chds come for free...) so quickly...
228
clrmame Discussion / Re: clrmamepro 4.048d released
« on: 13 January 2024, 10:09 »
Thanks, I will have a look
229
clrmame Discussion / Happy 2024
« on: 04 January 2024, 20:55 »
Wish you a peaceful and healthy 2024!
New Scanner coming along nicely....(Screenshots attached)
However, during the holiday season I only did some little work here and there....now fully concentrating on the core fixing part.
(And yes, you can have multiple rom and sample paths :-) )
New Scanner coming along nicely....(Screenshots attached)
However, during the holiday season I only did some little work here and there....now fully concentrating on the core fixing part.
(And yes, you can have multiple rom and sample paths :-) )
230
clrmame Discussion / Re: delta chds, cmpro test version
« on: 21 December 2023, 20:29 »
If you can't wait till next year and really need deep/full integrity check support for delta chds, you can download this build:
https://mamedev.emulab.it/clrmamepro/binaries/cmpro_deltaverify.7z
and unpack/replace you cmpro64.exe with it
https://mamedev.emulab.it/clrmamepro/binaries/cmpro_deltaverify.7z
and unpack/replace you cmpro64.exe with it
231
clrmame Discussion / Re: clrmamepro 4.048d released
« on: 21 December 2023, 10:42 »
would be nice however if someone prepares a zip file with some zStandard compressed files in it...would save me some time :-)
Again: we don't talk about .zstd files but zip with zStandard compression method.
Again: we don't talk about .zstd files but zip with zStandard compression method.
232
clrmame Discussion / Re: clrmamepro 4.048d released
« on: 21 December 2023, 07:49 »
well....for chds it won't play a role since decompression is only done when the belonging option is activated and then chdman is used.
For zips it would mean that the data inside the zip uses a different compression mechanism while the general zipstructure is the same, so reading shouldn't be a problem too.
When it comes to testing or unpacking it depends if ZipArchive (the used 3rd party library) is able to work with it which I haven't tested yet. When it comes to adding files to an archive, most likely a standard mode is used so that the newly added file inside the archive won't be Zstandard anymore (unless a direct copy of compressed data is used). The same applies to the new scanner/rebuilder where you might have the chance that bit7z (which reuses 7z) might already be able to decompress/compress Zstandard compressed files inside zips....have to check that. I can contact the authors of both to see if such a feature (if missing) can be added in a future release.
For zips it would mean that the data inside the zip uses a different compression mechanism while the general zipstructure is the same, so reading shouldn't be a problem too.
When it comes to testing or unpacking it depends if ZipArchive (the used 3rd party library) is able to work with it which I haven't tested yet. When it comes to adding files to an archive, most likely a standard mode is used so that the newly added file inside the archive won't be Zstandard anymore (unless a direct copy of compressed data is used). The same applies to the new scanner/rebuilder where you might have the chance that bit7z (which reuses 7z) might already be able to decompress/compress Zstandard compressed files inside zips....have to check that. I can contact the authors of both to see if such a feature (if missing) can be added in a future release.
233
clrmame Discussion / Re: delta chds, cmpro test version
« on: 20 December 2023, 21:17 »
Well yes, since cmpro does a "chdman verify -i %1" command which would fail on deltas....it would require "chdman verify -i %1 -ip %2" where %2 gets replaced with the parent chd filename...but that's currently not supported (but on the to do list).
So...for delta the deep check won't work....but as I said: currently nobody is using delta chds since there are some open issues with them on chdman side, see https://github.com/mamedev/mame/issues/11675
So...for delta the deep check won't work....but as I said: currently nobody is using delta chds since there are some open issues with them on chdman side, see https://github.com/mamedev/mame/issues/11675
234
clrmame Discussion / Re: delta chds, cmpro test version
« on: 20 December 2023, 18:36 »
Since nobody I know of uses delta chd, you most likely don't see any warnings about delta chds....
So I assume you don't have any delta chds....if you select "warn about non delta" you should see a warning for nearly all of your chds. The warnings appear in the warnings window below the scanner.
So I assume you don't have any delta chds....if you select "warn about non delta" you should see a warning for nearly all of your chds. The warnings appear in the warnings window below the scanner.
235
clrmame Discussion / Re: rebuilder 0.07 released
« on: 14 December 2023, 07:48 »
The UIs are very very preliminary but they do what they should do....
as soon as everything gets combined (Scanner, Rebuilder, Profiler), there will be a selectable backup path which can be reused by scanner and rebuilder.
as soon as everything gets combined (Scanner, Rebuilder, Profiler), there will be a selectable backup path which can be reused by scanner and rebuilder.
236
clrmame Discussion / Re: I've got a CLRMAME bug for you, Roman....
« on: 02 December 2023, 20:05 »
Maybe I simply don't understand what you mean but:
you can't have parent/clone relationships over different softwarelists.
in fmtowns_cd you have prostudgr which is a clone of prostudg within fmtowns_cd.
...and in pc98_cd you have prostudgr..they do both have the <disk name="pro student g (japan) (rerelease)" sha1="11bc5195ccaf557fe17a349eb8284c78e08e29ac" /> in common, but in general you need them twice. One time for pc98_cd and one time for fmtowns_cd. Since software lists need distinct rompaths, you shouldn't run into any issues. Of course it's recommended to use single profiles for each software lists and not that combined mode.
With the new scanner it will be a different story, but for cmpro you should use single profiles.
you can't have parent/clone relationships over different softwarelists.
in fmtowns_cd you have prostudgr which is a clone of prostudg within fmtowns_cd.
...and in pc98_cd you have prostudgr..they do both have the <disk name="pro student g (japan) (rerelease)" sha1="11bc5195ccaf557fe17a349eb8284c78e08e29ac" /> in common, but in general you need them twice. One time for pc98_cd and one time for fmtowns_cd. Since software lists need distinct rompaths, you shouldn't run into any issues. Of course it's recommended to use single profiles for each software lists and not that combined mode.
With the new scanner it will be a different story, but for cmpro you should use single profiles.
237
clrmame Discussion / Re: mac crossover problem
« on: 29 November 2023, 08:24 »
>No other things I can try?
Well you can try what I've told you, unfortunately you did not give too much details on your tests, so here again:
Try the 3 cases.
Start with an empty rompath, add one set with 1 wrongly named rom file.
1st test case: keep the set as folder/file
2nd test case: use a zipped set
3rd test case: use a 7z set
The scan should find the wrongly named rom (inside the folder / inside the archives) and if fix options are enabled, it tries to fix it. According to your post, modifying causes the exit. So try all 3 cases. Which one fails?
Instead of having one wrongly named file inside the archive/folder, you can also add a random file to it, which should appear as unneeded and fixing them would also cause a modification step. Let's see if that works.
You can post screenshots of the scanner windows where it lists (when fixing is off) your test case result, so I can have a look if that setup is ok already.
>Is there a way you can make a Mac version?
As the readme states, new scanner/rebuilder will get open source if they are done.
So you can try to get it compiled on a Mac.
Well you can try what I've told you, unfortunately you did not give too much details on your tests, so here again:
Try the 3 cases.
Start with an empty rompath, add one set with 1 wrongly named rom file.
1st test case: keep the set as folder/file
2nd test case: use a zipped set
3rd test case: use a 7z set
The scan should find the wrongly named rom (inside the folder / inside the archives) and if fix options are enabled, it tries to fix it. According to your post, modifying causes the exit. So try all 3 cases. Which one fails?
Instead of having one wrongly named file inside the archive/folder, you can also add a random file to it, which should appear as unneeded and fixing them would also cause a modification step. Let's see if that works.
You can post screenshots of the scanner windows where it lists (when fixing is off) your test case result, so I can have a look if that setup is ok already.
>Is there a way you can make a Mac version?
As the readme states, new scanner/rebuilder will get open source if they are done.
So you can try to get it compiled on a Mac.
238
clrmame Discussion / rebuilder 0.07 released
« on: 28 November 2023, 18:18 »
https://mamedev.emulab.it/clrmamepro/binaries/rebuilder_v007.zip
https://mamedev.emulab.it/clrmamepro/binaries/readme.html
- fix software list rom sizes determination (wasn't limited to loadflag value)
- fix software list merging (SL/SL collections don't use merge attributes, so lookup by hash in a parent/clone relationship)
- don't use # in default pattern (rompath) names since such names would be cut off when used in mame.ini due to comment handling
- pattern names can't end with '.' (Windows doesn't like this), replaced cases with "_"
- minor changes to the stats count output
- updated 3rd party libs (spdlog, bit7z, pugixml)
https://mamedev.emulab.it/clrmamepro/binaries/readme.html
- fix software list rom sizes determination (wasn't limited to loadflag value)
- fix software list merging (SL/SL collections don't use merge attributes, so lookup by hash in a parent/clone relationship)
- don't use # in default pattern (rompath) names since such names would be cut off when used in mame.ini due to comment handling
- pattern names can't end with '.' (Windows doesn't like this), replaced cases with "_"
- minor changes to the stats count output
- updated 3rd party libs (spdlog, bit7z, pugixml)
239
clrmame Discussion / clrmamepro 4.048d released
« on: 28 November 2023, 18:16 »
4.048d
fixed: softwarelists can lack some possible mergings
fixed: possible assertion during delta checks
fixed: softwarelists can lack some possible mergings
fixed: possible assertion during delta checks