Print

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

[bob]

This is with the latest ClrMamepro and the latest Mame.

The scanner is really struggling with the MayGay Roms. Each one is taking 5-10 minutes. I cant for the life of me see why. Is this a known issue ?

[Roman]

Erm...nope

Full standard (splitmerged/zip/no softwarelists/nosha1 deep check) MAME 228 scan takes around 46 seconds on a low cost ssd/full cache.

You may need to check if other 3rd party tools (like virusscanners) interfear.

[bob]

Thanks for the info.

I will try and find out whats slowing it down. Its been over 13 hours now and only 35 % in. Its very strange as previously it was fast. Just this latest mame seems to have massively slowed down.

[Roman]

Must be something different...just some newly added sets can't be the cause.

Turn off all fix options and do a scan, maybe you miss something in such sets and got a weird scanner advanced fix option enabled which runs over and over again through all your files.

Scanner->Advanced->"Deeper check for fixable missing files" should be turned off for example

[bob]

Thanks Roman

That did the trick. Thanks also for producing such a tool, without it I would have given up trying to organise the roms years ago.

[ssergE]

Hi
I also suffered the same issue.  Disabled AV and "Deeper check for fixable missing files" with no success.  Only when I unticked the fix option for "Missing" was it able to get past the Maygay roms.

I access my ROMs over the network as they are on a NAS, so I think the added latency in opening the file is really highlighted for some reason.  Another thing I noticed is all the "meta-sets" (not sure the right terminology - things like the keyboard controllers and cartridge slots/etc) all add a pause to the scanning process, whereas normal rom sets fly by nice and quickly.

[ssergE]

Hi
To further expand on my last post - trying to fix the missing roms issue (there's two GALs that have been added to all the Maygay sets) by dragging a zip (funnily enough not containing the required files ...) to the results window with the fix missing check box ticked causes the really long running behaviour.

Looking at may NAS access logs I can see it is working its way through all ~1000 m1* Maygay sets, for each of the Maygay sets its trying to fix, so if I left it running it would do it 1000*1000 times, which seems to be a cause of slowness.

I'm wondering given the 'strangeness' of the Maygay machines (lots of variants, all sharing similar/same roms) it's uncovered some slowness?

Anything I can do to help diagnose what is going on?  It's a fantastic program!

[Roman]

Nah...there are several things here happening:

Dragging a set into the scanner tree window will run the rebuilder which touches the source(dragged) file exactly once and it creates any matching file in the destination. So when you miss 1000 times the same file and the file is in the dropped set it reads it once and writes it 1000 times...which would still be very fast.

When the rebuilder job is done, a scan is perfomed (when the belonging option is enabled). If you got the enhanced fix missing option enabled and still got a missing file somewhere, the scanner will look for it. Without that ticked option, it looks in your specified add folders, the backup folder and parent/clone sets of the current set. If you tick that option it will run through all files you got.....and that's the killer.

So a) it's not the drag'n drop operation and b) it's not "Maygay" (maybe only because the structure of the set leads to some missing files which are shared over the sets) and c) it's purely the advanced fix missing option...so keep it turned off....

Usually you add missing sets with the rebuilder.

[ssergE]

Thanks for the info; it certainly helps.
Finding the 2 missing files that were shared across the maygay sets and using the rebuilder did the trick.  Not sure where I picked up the drag-n-drop workflow from.

Thanks again!

[Fred92]

Hello,
i post here because i have the same issue (tried both with 4.039a and latest build.4.040 64bits)
my check is stuck on maygay too when i launch a new scann
and when i select "stop scanning"  clrmamepro freezes
i uncked all advanded scanner options.
my roms are stored on a Nas.
previously (for months/years) there was no problem... strange behaviour since 2/3 latest mame's roms builds.

any help welcome.
Thanks all

Fred.

[Roman]

Unless you have some network issues (https://www.emulab.it/forum/index.php?topic=4902.msg18940#msg18940) it's really based on an enabled advanced scanner option to do a deeper fix missing check. Or a virusscanner goes wild.
You may want to do some monitoring with Windows Taskmanager to see which task is taking cpu power or check the network traffic.

[Fred92]

thank you answering.
here are screenshots of my config
no deep scan at all...
NO VIRUSCANNER (i haven't any one on this PC)
i tryed another new scann and it's stuck on "m1albsq" for minutes...and then m1alley...
my NAS is on ethernet, no network issue at all.

[Roman]

Turn off the fix missing option and try again

...and you're sure you use not separated bios sets??? That should actually be enabled....and I see you're not using a direct MAME import but an external dat....shouldn't be a problem but...it's not official

if you now accidently turned off "separate bios sets", you're running into a lot of fix missing operations now...since you tell each and any set to have all bios files not separated (so you keep thousands of copies of the same files now).

[Fred92]

so...
here is how i have done :
before i wan doing a new scann with fix all options.
now this way doesn't work for me and is too long.
So i make a new scan without fixing anything and no deep.
then i make a rebuild
then a fix all.
and like that, it's more quickly done.
consider it's fixed for me (but i think there is something wrong since latest updates.. roms or softmware i don't know because i haven't done like this before for years and there was no issue at all).
Thanks helping.
Fred.

[Roman]

well, it is basically fix missing. depending on the advanced option it looks a) in your addpaths, in the backup folder and your rompaths for the missing file. If the advanced option is not ticked, it only looks in sets named after the set where the missing file is and in sets named after parent and clones of that set. if the advanced option is enabled it looks in any file which is of course overkill.

now if a big group of newly added sets miss a lot of files (or using not separarted bios sets), fix missing looks pretty long (and over and over again) for the files.. although the scenario is pretty rare it does happen. progetto snaps dats are a typical example where fix missing should be turned off. it use some placeholder files for pngs and so you may have hundreds instances of the same missing file and each would be looked up individually with fix missing (while the rebuilder would create them all at once). now if you additionally use solid packed 7z archives you can go for summer holiday while fix missing is working....


so....usually you should a) keep the advanced option disabled, b) do a rebuild first to add all new stuff and the finally scan with fix options on to get rid of the rest of te problems....