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

-listsoftware does not include all software lists from mame's hashfolder and secondly, it's a real pain to set this mode up correctly. You'd need unique distinct rompaths for each software list and scanning takes long, more memory usage etc..etc...

Gotcha! 

When you import your data from a mame.exe you're asked after the import (unless the belonging option is unticked) if you want to import software lists. Then cmpro does load this -listsoftware data and you got all software lists in one profile. But....first of all, -listsoftware does not include all software lists from mame's hashfolder and secondly, it's a real pain to set this mode up correctly. You'd need unique distinct rompaths for each software list and scanning takes long, more memory usage etc..etc...This mode is not recommended.
Hopefully such problems will be history with a new scanner. You see that the new rebuilder already handles -listsoftware flawlessly and efficient.

- parallelization? You don't want to have multiple threads treating your hd/ssd like crazy...ever tried to copy various bunch of files from one hd to another in multiple copy operations...it will crawl

But a first small test was already pretty positive which gave a extra ~25% speed boost when sha1 input scanning was enabled....

That's the way!!

Thanks Roman 

Hey Roman, just tried importing -listsoft into cmp and found out it's loading by itself all (all? Maybe... ?) Software Lists in one shot.

Soooooo... I'm asking you: what's the point of loading all different SOFT xmls from the hash/ folder of MAME? 

Sure there's something I'm missing, but I do not understand what... ... 

As you (the audience) might have noticed, "fool-for-a-day, troll-for-a-life-time" Jessica Jones, rolled over the boards again and was removed by admins....nothing unusual...this happens once a year...

But the really funny part is:

The discussion gave me an idea where threading can give some extra speed up....It's not related to the troll comments at all (CUDA for SHA1 etc...)

But a first small test was already pretty positive which gave a extra ~25% speed boost when sha1 input scanning was enabled....
For non sha1 runs it's not that big since you simply have pure lookups without decompression/sha1 and the actual gain by multiple threads is eaten up by the overhead to create the threads...

I will check how this scales for larger data and for number of threads....

So..Thank you Jessica Jones...you made my day. See you next year.

I'm late this time but a huge THANK YOU for moving forward this! Will give it a spin ASAP

Rebuilder 0.05 released

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

0.05 has a major unicode update, so now all your utf8 chars (no matter if in the datfile, in archives, in folders, in log output etc) should be handled correctly.

As a small extra...(I had a little time and wanted to see how easy it is to reuse the core) I've added rebuilderUI ;-)
It's a tiny UI for the rebuilder....the options should be easy to understand since they match the commandline parameters. The log list has a context menu and the window is resizable (things you don't see on the screenshot below).

RebuilderUI (rebuilderUI.exe) saves its settings in settings_ui.xml while the commandline rebuilder (rebuilder.exe) uses settings.xml. Both need the 7z.dll.

Hope you enjoy it...

Hash values of an archive is of course obsolete.....order of added files and compression rate of course alters it....there is no guranteed add order, no sort, no nothing

Worth to mention that some zip archives have different crcs (for example 1941.zip) but size and files inside are exactly the same. Most of zips are exactly the same. I assume that clrmamepro adds some files into zips with different order.

Nice to hear...that old cmpro is slower ;-) I was a bit sceptical since you turned off all of the major speed advantages....but sounds good to me....

Rebuilded from the same source. Started at 7:15 ended about 12:35 so more than 5 hours was needed for entire process