379
« on: 05 March 2021, 16:21 »
1) I can't repeat the "An error occured while reading information from: G\Mameui64\MAMEUI64.exe" at all. This error only appears when cmpro can't access the redirected -listxml or -listsoftware output file or the file itself holds xml bugs. As I said...I cannot repeat this behaviour at all...sorry.
2) Using the same executable for 2 profiles (-listxml and -listxml + -listsoftware) is not intended and will create problems. cmpro reads the xml files and stores the data in a cache file (based on the exe checksum). So you will have one and the same file for both, or if you created one with software lists and load your profile without you get in trouble. Cmpro checks if the exe changed (hash), if yes it shows you a prompt and will reimport data, if not, it loads the cached information.
Either you need 2 not binary-identical exes or use a dat for one and exe import for the other. Or you need to clean the cache all the time before loading a profile...The better way for software lists is anyway to keep them in separate profiles (simply drag'n drop MAME's hash folder in the profiler).
3) auto assign sysdefpaths. Let me tell you how it works. First you need to add rompaths. Rompaths can't have subfolders with other files. You cannot add the root of all your software lists. You need to have them separated. You can simply drop all your folders in the settings folder of course. So settings -> rompaths should show a list of paths....and not one. Then you go to systems and hit auto assign. The auto assign works as follows: Runs through all rompaths (not subpaths!), tries to match the setname against the databasis...each match increases a counter (per bios/softwarelist) and after scanning all rompaths cmpro checks which rompath scored best for bios/softwarelists XY (highest count). So for Atari2600 your 6 rompaths score 0, 1, 1, 10, 200, 7, the rompath with the 200 is assigned ...and so on.
4) nothing of the above actually has changed in years. Regarding the fix for the autodetection, that feature broke a version before so it was just a quick fix to get it up working again.
Setting up softwarelists paths in a combined profile is really a pain...yes...that's why I advice people to not use it (I actually already though of removing it). Using separate profiles is in my opinion the better way to go through it (especially with the batcher)
Regarding 2, I can think of a way that cmpro is able to support 2 different cache files though....one with and one without software lists
(actually I'm working on modifying the hash so that a) the name of the datfile/mame exe, b) the binary content and c) combined or single mode is reflected by it...so you would be able to have differnt cache files for identical mame binaries in combined/not combined mode and/or different caching files for byte-identical files in different positions)....)
