Anyway, the problem I'm experiencing, is that using ClrMamePro to "scan" rom-files just doesn't work. It seems stuck on the "Finding unneeded files"-phase.
If I copy the exact folder to my local computer or smb/cifs-share, it scans just fine.
Also, here is the kicker. It's not consistent. It seems to work just fine for smaller sets, but it fails (and just loops) on larger ones.
(Yes, this is technically "copyrighted stuff", but it is absolutely ancient, so.. I hope this is not immediately removed)
Logfiles are placed here, due to their size (--logfile and --log-level DEBUG appended)
mega dot nz/folder/MCRQwZiD#XwmWpJEPj4kgNDw5t-vpbg
as per the debug log NOTICE: --allow-other flag does nothing on Windows
did not see the config file?
the reason i ask for it; based on your command, you are using the buggy, depreciated, never left beta, cache remote. if true, i suggest to remove that and test again. --cache-db-path, --cache-workers,--cache-chunk-size - these are for the cache remote
about the nonworking_rclone.log, did not see any ERROR in it?
post an example filename that is causing problems
Clrmame has no logfile really (well, of the operaton, which we need here atleast)
It scans the folders first, and then it's supposed to scan the files inside, checksumming them and looking inside archives if so is configured.
It's mainly used for keeping your MAME-set up to date, but there are (as shown) other uses for it aswell.
mamedev dot emulab dot it/clrmamepro/ would be the homepage for more info.