EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: Shoegazer on 04 February 2020, 17:13
-
Trying to scan software by batch-importing MAME software list dats. I can't find where I need to specify the base scan path so that each software list item is scanned under its corresponding set name. I looked for documentation on scanning software under Linux/Wine but couldn't find any. Can someone help?
Note: this was working fine until the cmpro config became misconfigured somehow, and now I can't recall how it was originally set up.
-
erm...what do you mean with base scan paths?
Generally, if you batch scan existing profiles, it takes the information what to scan from the specific profile rompaths.
So the question is most likely more how to setup new profiles out of a bunch of datfiles, so that rompaths are created and assigned automatically based on the datfile filename or datfile header information.
This can be setup in the batcher settings (right click a datfile, load profile(s) in batchmode...) and switch to the "misc" tab. There you can find the "for rompath naming use:" settings and a root folder.
-
Thanks, Roman. You are right, that's what I meant - I was just using "base scan paths" for lack of a better term.
So I checked "create rompath for new dat" and browser for the root software folder (which contains software subfolders e.g. a2600). However, when I attempt a scan it immediately returns "not scanned" in the profiler window. What am I missing? I know it can find the root folder because I can browse for it.
-
You can try to
A) hit the profiler "refresh list"
B) load the "not scanned" profile as a normal datfile and check the setup rompaths if it's a) active/checked and b) matches what you expect
-
Thanks again. I refreshed the list, then loaded one of the not scanned profiles as normal and checked "ROM-Paths" under Settings but nothing was listed. Assuming the path should show up there, what am I missing?
-
yep, a rompath should be there. So something went wrong when it tried to create and assign a rompath based on the information from the datfile (e.g. root folder + datfile name tag).
Seems to be linux/wine specific then....Could be a rights-issue maybe? Maybe you can try a different root folder or check if that root folder actually contains newly created rompath and just the assignment failed for whatever reason.
-
Actually, the issue turned out to be related to the datfiles I had cached in the profiler. I deleted them and loaded them again with the "create rom path for new dat" setting and it seems to be working now. Thanks for your help though!