> is the mentioned change already in 0.172? > > I have the same / similiar problem. Nearly every ROM I pick from Mame UI is answered > with "No CHD / ROM found" error, but if I start the same rom / zip from command-line, > it starts. > > Example: > > mame64.exe blazstar (runs) > clicking on "Blazing Star" in Mame UI results in above mentioned error. > > I did a clean unpack of 0.172 archive & copied roms to roms-folder. Then, all the > roms are found, but not startable. If I do a full audit (SHIFT F1) in Mame UI, the > entries for those roms all disappear... > > Where am I wrong? > > Thx, g
I did a test with official 0.172 and picked blazstar in the internal UI. After picking a BIOS the game loads and runs fine for me without any error messages.
I myself don't use the auditing feature in the MAME UI. There's software like ClrMAMEPro or just download complete sets and then there's no reason to audit at all.
Also, you don't need to copy or move roms folder. Instead just use the rompath option in mame.ini or you can specify -rompath location on command-line.
|