Print

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

[Guru]

I want to report some clrmame v071 issues and make a couple of suggestions.

When setting up the paths, if the backup path is a subfolder of the ROM folder the scan fails and says to check the log. No log is created as far as I can see. If one is created it isn't obvious where it is located.
It seems the 'log' is the status line at the bottom, but it only shows 2 lines. It should either be expanded to show more lines or be resizable with mouse so the user can show more lines.
I later realized the log was scrollable on the right side (hehe!) and found the info then made the backup folder a completely different path and it worked.

I'm using clrmame to build some new (work-in-progress and not completed yet) software list archives for MAME.
BUG: When doing a scan or rebuild on a new XML Software List, the scan fails to find any problems if the software list was edited and saved after the first scan was done. Even if the cached xml file copy in the clrmame directory is deleted it still fails. To force it to find issues with the current XML Software List clrmame has to be closed then re-opened.
I suggest to load the XML from the source path each time a NEWSCAN is done rather than use a cached copy.
SCAN should mean 'use the existing cached XML copy if a scan was already run once'. If no scans have been done SCAN should be greyed out. After NEWSCAN is done once then SCAN becomes available.
NEWSCAN should mean 'always load the XML and then scan'.

Thanks.

[Roman]

1a) "Log"
When running the commandline version, the log is the printed output with various warn levels (info/warn/error). You can redirect it into a file if you want. When running the UI version, the log area is at the bottom of each screen. It's resizeable, scrollable and you can even copy all entries to the clipboard. If it's "2 lines", then you should adjust it.

1b) "backup path"
Well, due to the fact that rompaths are reserved for your roms, it's pretty obvious that the backup path can't be a subpath of any rompath, otherwise the scanner would detect it as unneeded. That's why the log informs you.

2) Softwarelist: First of all the question would be are you talking about a -listsoftware import from a MAME binary or a single load of a software list (hash file folder).  I expect you do a -listsoftware import from a mame binary and then the following happens: clrmame rememebers a hash for the binary and a hash of its hash folder where the software list xmls are stored to see if it needs to reget the data and doesn't use the cache. So it does see if files do change inside the hashfolder or the mame binary itself changes. In this case, it reimports the data. Now you might do your changes in a different folder, then there is a settings in settings.xml "Settings/HashFolder" where you can specify your path and then this is monitored for changes.

3) Scan versus New Scan
This has nothing to do with cached XML data. A "New Scan" ignores possible existing previous results and rescans all machines while a "Scan" only rechecks the machines which had issues in a previous Scan or New Scan. The result is remembered and store. If there is no existing result, a "scan" will do a "new scan"


So....to sum it up: no bugs