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

Well I asked for your binary because I wanted to check how the -listxml output differs from the official one :-)
I know from other forums that mameUI sometimes is some commits ahead of the official mame release...
I don't expect something really obvious in that output for the "chds from backup -> sample path" move but who knows....

Update: Well, the -listxml output does differ from the official one but nothing really which gives a reason why chds from backup gets copied to your samples folder....this really does not make any sense. Files from backup are only copied back to a rompath (!!) when it matches a missing file (crc32+size, optionally sha1 match).
What you can double check is, open settings.xml in a texteditor and search for your samplepath if it's somewhere listed where it shouldn't be listed...

Roman,
   Here's a link to that mameui... https:  //limewire.com/d/3kKrE#6bc3TaqDtT   <- This was my own compile and not inline with the 276 source.

That got me thinking & wondering... I completly forgot that since MAME updated to the new CPU with x86-64-v2 processor instructions set requierment, on this older PC I've had to use my compiles to be able to pull the xml with CM. With the V2 requirement and official MAME.exe CM gives all kinds of errors trying, and sometimes it did complete the pull but def didn't scan correctly.
I can't remember if 274 and the new requirement was the 1st issues I had with this but I'm willing to bet it was/is. Next release I will use the baseline 277 source to compile and see what happens. Or I can just pull the xml off of 1 of my newer PCs and use it on this old one to scan. (Right? The xml file should be the same for scanning.)

      Big Thanks! - Again!

-Had to add a couple of spaces to the link, Spambot didn't like it!

Since you're using a mameui.exe, can you send me that?

Would be great to know how your config looks like, so maybe you can send me your settings.xml file. Additionally maybe some information about the sl files themselves...zip/7z/decompressed...

Well...it's been a while so maybe you're interested what's happening behind the scenes...

well, first of all, I started with the profiler. Nothing to show/work at the moment since a) real life keeps me extemely busy and b) there are some other core tasks to do.

So here what's already in the next version:
UI:
- scanner, fixed showing of empty and complete machines
- scanner, fixed showing of non rom/sample/disk related machine issues (e.g. wrong named machine)

Core:
- added: scanner reports 'wrong' chd version. Current expected version is 5, warning is not shown for baddumps. Version and baddump warning can be altered in settings.xml
- misc:  updated cli11 to 2.5.0
- misc:  updated spdlog to 1.15.2
- misc:  using absolute pathnames for error reporting during path scan
- misc:  only list machines with issues as trace output in fixing phase
- fixed: typo "uneeded"
- fixed: filter enrichment might miss sampleof dependencies
- fixed: doing archive backups from a folder and backup archive already exists creates a new archive instead of merging files in
- fixed: archives which match a valid rompath subfolder name (e.g. softwarelist name via pattern or automatically) are falsely iterated like a folder instead of listing them as unneeded (wrong placed)


Still in the queue:

- trying to repeat the crash which 2 users reported  when fixing the Amiga SL 1000/3000 change (MAME 274-275). Unfortunately I can't repeat it at all at the moment...so if anyone is able to repeat it, please contact me (see https://www.emulab.it/forum/index.php?topic=9882.msg27364#msg27364)
- trying to find out how chds were placed in a samples folder (see https://www.emulab.it/forum/index.php?topic=9893.0)
- checking some WINE SHA1 checking warnings
- trying to align clrmamepro and clrmame/UI for devices which have a romof dependency and use or don't use merge attributes on files. Currently I think that clrmameUI does it right...but I need to compare and check...

I tried it several times but never ran into a crash.
If you can somehow repeat this issue with a minimal setup (e.g. just the 2  amiga folders with e.g. 1 file in it), let me know. Most likely I also need details about the backupfolder and the used settings (e.g. sending settings.xml) in general

Hiya! I'm having this exact same issue, but unchecking fix issues fixes it for me as well.

I'm pretty sure it's failing on fixing missing, at 0%. I can do a full scan without that, but the moment I either try a full scan or a continued scan, it closes itself. I don't think this is folders in the add list not existing, as I removed those and it didn't help.

1) actually I've added it yesterday, so it will be in the next release
2) ;-) Overwriting won't help if file A+B was replaced with C which includes A and B......you ended up with A,B and C...and so you have the files mulitplied...
3) very very strange one indeed....there are 3 very very unlikely possibilites:

- You did a rebuild and had your samples folder as destination folder
- You had your samplefolder specified as backup folder (but that would mean that the chd files were somehow marked as unneeded)
- The algorithm which decides where to put a wrong placed files somehow picked the samples folder, however chds/roms and samples are strictly separated...but I will have a look at it....But that would also mean that the chds were somehow wrongly placed in the first scan....

1 - That's what I figured.
2 - Dead on. I did overwrite the old hash files with the new ones so I'll guarentee those old ones are still in there.
3 - It only does that on my 1 computer on the 1st scan with a new version of MAME. If I get time I'll see if I can repro it before the next release or I'll just wait until then and I will be certain to pay more attention to see what goes on. Then I'll get back to you if need be. I'll bet that it's something on my end in that old set-up.

Thanks for the quick answers and definetly for all your time spent doing this!
Have a good one!

1) chd version mismatch check will come soon in clrmame. SHA1 check won't solve the problem

2) Hmm..no, actually it detects the old ones as unneeded and sees them as fill ins for the "new" megacd. They get 'moved' to the new place. However, maybe you did not do a clean install of your MAME hash folder and still got the old hash files in their. clrmameui first takes all from -listsoftware and then scans the hash folder for additional ones which are not listed in the xml output (there are a couple which aren't included for whatever reason). So if you don't clean MAME's hash folder before unpacking the new version over it, you still get the old ones in there and clrmame will read them in as additional sl.

3) ? weird one. Unless the samples folder isn't listed as backup folder somewhere. You could check the settings.xml file for this....but the screenshot doesn't correspond to that. Is there a repeatable small scenario for it? I can try to build one based on that screenshot....