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 - Roman

Pages: 1 [2] 3 4 5 6 7 ... 165
21
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.

22
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

23
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.

24
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.

25
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.

26
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.


27
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)

28
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


29
clrmame Discussion / Re: mac crossover problem
« on: 28 November 2023, 07:07 »
Use RomVault.

30
clrmame Discussion / Re: mac crossover problem
« on: 27 November 2023, 06:17 »
Sounds like an access rights problem.
But it's more interesting to know which files you're touching. zip? 7z? decompressed files/folders?
Since all 3 use different methods:

7z -> 7z.dll  (3rd party component)
zip -> ziparchive class (3rd party component)
decompressed files/folders -> std::filesystem / win api (depending if you're talking about the new rebuilder or cmpro)

So, simply test all cases, take a rompath with just 1 machine set, make it a 7z archive, a zip archive or use it decompressed.
...and check general access rights to that rompath. Are there differences between the new rebuilder and old cmpro?

31
clrmame Discussion / Re: Some new scanner wip
« on: 23 November 2023, 19:10 »
Since people asked for some "benchmarks"...(e.g. .260, no softwarelists, but roms/disks/samples)

generally, you need to differ between 2 things: no diskcache (that's a full scan after a just started PC)
and diskcache (that's a full scan after a scan already took place where your PC hopefully uses the cached data)

old scanner: 8 min 45 seconds (no diskcache)
old scanner: 1 min  5 seconds (diskcache)
new scanner: 5 min 49 seconds (no diskcache)
new scanner: 0 min  5 seconds (diskcache)

Scanning a not existing MAME 260 collection (so everything is missing)
old scanner: 1 min 31 seconds (no diskcache)
old scanner: 1 min 28 seconds (diskcache)
new scanner: 0 min  1 second  (no diskcache) however it takes 26 seconds to render the tree :-)
new scanner: 0 min  0 seconds (diskcache)    however it takes 26 seconds to render the tree :-)

Or some progretto snaps (Snapshots with software list datfile, unpacked pngs on the disk)
old scanner: 7 min 21 seconds (no diskcache)
old scanner: 1 min 59 seconds (diskcache)
new scanner: 4 min  7 seconds (no diskcache)
new scanner: 0 min  6 seconds (diskcache)


The tester's system: i7-8700K, 16GB RAM, Seagate IronWolf HD

32
clrmame Discussion / Re: Some new scanner wip
« on: 23 November 2023, 05:49 »
for now it only accepts a regular expression to filter machines by name....but yes, a filter is part of my menioned nice-2-have things which will most likely be able to filter with xpath expressions....and then you can filter on anything inside the xml....

33
clrmame Discussion / Some new scanner wip
« on: 22 November 2023, 19:02 »
While wasting a little bit of time with delta chd support in old cmpro, I recently found a little time to work on the new scanner again..

So what's the status?...well, it scans nicely:

- mame -listxml output, mame hash files, mame -listsoftware output
- full/split/standalone merged
- multi rom/sample paths suppport
- pattern scanning supported (if you keep your sets split by bios etc)
- roms, disks and samples, compressed (7z/zip) or uncompressed
- writing of fix dats
- writing of report output
- remembering old scan information for a faster scan
- commandline available (compareable to new rebuilder)
- preliminary gui available (compareable to new rebuilder)

What's on the to do list:

Well, the actual fixing part, but that be rather simple since it simple needs to run through a list of tasks like
'rename this to that', 'delete this file here', 'add file from there to there'...

Got a small wishlist already some some UI related features here and there...but they don't have any priority...

and of course.....after that, a profiler...

Ever wanted to scan a full software lists collection? Remember the pain in cmpro to set it up? Well, now it's just adding a rompath and hitting start...a little screenshot shown below should give you an idea. Generally it should be way easier to set it up...no need to define 'system default paths', no need to setup thousands of distinct rompaths just for softwarelists.....

34
clrmame Discussion / 4.4048c
« on: 04 November 2023, 17:20 »
4.048c
fixed: wrong "Error while..." message after delta operation succeeded but backup is disabled.
misc:  minor changes to the delta output messages



Keep in mind: https://github.com/mamedev/mame/issues/11675
....when this is fixed I will check if the V5 restriction can be taken back and some more chds can be converted....the github issue is about a V5 one though....

36
I've used your config and can't repeat your problem.
Do you have some kiwame folder in both of your rompaths? kiwame itself doesn't use any roms, so there shouldn't be anything kiwame related besides the folder with the chd.

Did you clean the cache or can you setup a new profile for fmtowns for a different rompath where you only have the kiwame folder with the chd?

I also wonder why only some chds are listed..especially only ones which were updated lately (260)....

Also go to Scanner->Hash & CHD Settings and check if all "Available Regions" are enabled in the middle section (especially the "cdrom" one without a number)

37
"4.047 will scan them and complain only about the samples.  The 4.048x wants to do all the renaming or removing of these systems"

this is interesting since the only change from 4.047b to 4.048b is actually
- the delta chd stuff....but that only checks the chd files for is/isn't delta and prints out warning, so the "missing"/"unneeded" part is not affected
- the "samples" unneeded issue...well..that only handles a weird scenario since "samples" is also a rom/sample/chd less device in MAME....

anyhow...thanks for the files, I will do further tests

38
well yes that looks ok, however some questions:
Do you use a single profile for fm towns or an all-in-one scan, which merge mode, how are the rompaths organized (more than one for fm towns?)

Maybe some other tasks are actively accessing the files during the scan and simply blocked cmpro's read...
since I heard that generally there is no problem when scanning such files

Maybe you can send me your cmpro.ini and the belonging .cmp file from cmpro's settings folder for your used profile.

39
clrmame Discussion / cmpro 4.048b
« on: 29 October 2023, 18:44 »
4.048b
fixed: wrong delta chd proposals in full merged mode (identical chds)


...and yes, it seems that converting the susume chd to a delta fails (also with manual chdman usage), JohnIV already filed a bug report to the MAME team....

40
can you do a "chdman info" on e.g. kiwame

Pages: 1 [2] 3 4 5 6 7 ... 165

Page created in 0.198 seconds with 19 queries.

anything