EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: 1 [2]   Go Down

Author Topic: MAME .267 and the new scanner  (Read 6406 times)

GDT

  • Member
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 33
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 127.0.0.0 Chrome 127.0.0.0
    • View Profile
Re: MAME .267 and the new scanner
« Reply #20 on: 25 July 2024, 16:53 »

Ok, I restarted from scratch with a new folder with the new scanner only for -listxml and this time it worked.
It finded some bounch (about 50) missing romsets, compared to clrmame scanner.
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 120
  • Offline Offline
  • Posts: 3414
  • Operating System:
  • Mac OS X Mac OS X
  • Browser:
  • Safari 17.5 Safari 17.5
    • View Profile
Re: MAME .267 and the new scanner
« Reply #21 on: 25 July 2024, 17:21 »

Actually both should output the same missing files….do you have an example? However I can only look at it early August. See also https://www.emulab.it/forum/index.php?topic=9767.0
I somehow think that in cmpro you got some options enabled which might hide some output…lets check that in August
« Last Edit: 25 July 2024, 17:22 by Roman »
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 120
  • Offline Offline
  • Posts: 3414
  • Operating System:
  • Windows NT 10.0 Windows NT 10.0
  • Browser:
  • Chrome 127.0.0.0 Chrome 127.0.0.0
    • View Profile
Re: MAME .267 and the new scanner
« Reply #22 on: 04 August 2024, 17:42 »

Ok, I've tried to repeat your ggiana sisters problem. Unfortunately, I can't repeat it. Everytime a removed set appears as fully missing in the next full scan. So I guess, I'd need your old profile *.cmp file (cmpro's settings folder) for your used profile where the problem appears and cmpro.ini.

By the way, on one screenshot you showed a chd naming issue with a sgi_mips chd. This is normal since the new scanner detects a problem when fully merging the sets (same chd file name, different hashes and for decompressed files (and chds are decompressed), you can't have subfolders). The new scanner then adds the sha1 in front of the filename. I can't remember if old cmpro handles this by removing parent/clone relationships of simply ignores it. So getting the wrong name here is normal if you compare old cmpro and new scanner.

Regarding your latest "It finded some bounch (about 50) missing romsets, compared to clrmame scanner." it would be interesting to see what it found.
Logged
Pages: 1 [2]   Go Up
 

Page created in 0.109 seconds with 20 queries.