|
recursive ROM folders not working
#387799 - 09/09/20 04:41 AM
|
|
|
Hi. I've just updated an old installation with latest 0.224, and wanted to start clean. So I installed in new folder, and then configured ROM folder to point to my roms dir, which is d:\games\mame\roms. Just added that one. MameUI64 scanned that folder, very quick, and found 0 (zero) games! Problem is I have all sorted out in subfolders, like: d:\games\mame\roms\standard d:\games\mame\roms\neogeo d:\games\mame\roms\n64 and so no... You can figure out... d:\games\mame\roms\"swlist" is more or less my structure. So, question... what should I configure in mameui64 in order to get it to scan the folder AND subdirs? Is it possible, or should I need to add each swlist folder manually? Thanks!
Edited by Leo Lagos (09/09/20 04:42 AM)
|
|
|
|
Re: recursive ROM folders not working
[Re: Leo Lagos]
#387800 - 09/09/20 09:46 AM
|
|
|
|
|
Re: recursive ROM folders not working
[Re: Robbbert]
#387806 - 09/10/20 04:07 AM
|
|
|
Thanks for the clarification... is there any other GUI/frontend with such a capability? Maybe worth a try
|
|
|
|
Re: recursive ROM folders not working
[Re: Leo Lagos]
#387823 - 09/11/20 04:19 AM
|
|
|
|
|
Re: recursive ROM folders not working
[Re: Robbbert]
#387840 - 09/12/20 03:06 PM
|
|
|
Yes Robert. It helps. I just tried adding that root (games/mame/roms) and it works for sw but no for standard even though they are inside that root folder.
So, should I have 2 folders like: /games/mame/roms/software/"swlist" /games/mame/roms/standard
Could you please recommend what would work as a correct setup?
Thanks again!
|
|
|
|
Re: recursive ROM folders not working
[Re: Leo Lagos]
#387884 - 09/15/20 02:57 PM
|
|
|
When I updated to 0.224 my directories were no longer loading up correctly. A fast refresh. The clone filter via right-clicking in the left hand column was no longer working, chdlist missing, and auditing anything that did show (and did run) always brought up a rm check of 'none required'. MAME in comparison had no issues, just MAMEUI. A reinstall to a different folder fixed the issue though, pointing to the exact same directories. Possibly a bug or the result of incompatible old config files
|
|
|