1
clrmame Discussion / Bug when scanning Mess+softlist
« on: 21 December 2014, 12:17 »
Seems that i had my account removed for some reason (auto pruning) ?
When i scan my MESS set i have the following errors :
Everything is at the right place, the NES softlist is correctly scanned when scanning only from the XML. But there seems to be some sort of conflict when i scan from the mess.exe
I would guess it come from the fact that CMP have to create false sets because of the way the NES samples are implemented at the moment.
I have this bug from before 0.156 till now. And scanning with the official exe didn't fix anything
When i scan my MESS set i have the following errors :
Quote
misplaced romset: E:\software\nes\moepro.7z (move to a rompath)
misplaced romset: E:\software\nes\moepro90.7z (move to a rompath)
Moe Pro! '90 - Kandou-hen (Jpn) [softwarelist: nes - folder: moepro90 - parent: basload3 - size: 640kb]
missing set: Moe Pro! '90 - Kandou-hen (Jpn)
missing rom: 0.chr [size: 131072] [CRC32: 7375d251] [SHA1: c240631e734fec873f546f20edaa81e0d31b4e27]
missing rom: 0.prg [size: 262144] [CRC32: c2222bb1] [SHA1: 4195ea3610d334bef352bf77fa005f24df1bfd6f]
Moe Pro! - Saikyou-hen (Jpn) [softwarelist: nes - folder: moepro - parent: basload4 - size: 640kb]
missing set: Moe Pro! - Saikyou-hen (Jpn)
missing rom: 0.chr [size: 131072] [CRC32: 221f85cf] [SHA1: 9379b8b4d440f039993a2f156e67667b38668094]
missing rom: 0.prg [size: 262144] [CRC32: 035cc54b] [SHA1: 24466952ee7178cde859a5953b12ab5b89b0c0ea]
moepro [folder: moepro - size: 0]
wrong SysDefPath: moepro [wrong: E:\software\nes\] [right: E:\bios\]
moepro90 [folder: moepro90 - size: 0]
wrong SysDefPath: moepro90 [wrong: E:\software\nes\] [right: E:\bios\]
Everything is at the right place, the NES softlist is correctly scanned when scanning only from the XML. But there seems to be some sort of conflict when i scan from the mess.exe
I would guess it come from the fact that CMP have to create false sets because of the way the NES samples are implemented at the moment.
I have this bug from before 0.156 till now. And scanning with the official exe didn't fix anything