Experiencing an issue with MAME 0.184, which was not present with 0.183. Looking for confirmation if anyone else experiences similar...
Selecting a new ROM file through the internal UI for a console with a ROM already loaded, after running the same console from Command Line referencing an external ROM path, results in MAME not loading the new ROM file; rather, MAME retains the ROM that was loaded previously for that console. Systems tested: a7800, nes, coleco, a2600, genesis, snes.
Launch MAME from command line specifying a console system and a ROM file from an external path...
mame.exe a7800 -cart "C:\Console ROMS\Atari 7800\Color Selector Demo (2003) (PD).a78"
mame.exe nes -cart "C:\Console ROMS\NES\Loopy Color Demo.nes"
mame.exe coleco -cart "C:\Console ROMS\ColecoVision\Carnival (1982)(Coleco).col"
mame.exe a2600 -cart "C:\Console ROMS\Atari 2600\Color Test (26-09-2002) (Eckhard Stolberg).bin"
Bring up the internal UI by pressing the 'Tab' key.
Select "File Manager", select "cartridge (cart) XXXXXXXxxxx", then from that same external path of the folder containing the console's ROM file that was loaded from Command Line, select a ROM different from the one currently loaded and running.
MAME restarts the console; however, it loads and runs the ROM previously/originally loaded from Command Line and not the new one selected through the Internal UI.
Tested with Windows 10 x64 / MAME 0.184 x64.
*EDIT: Bug report opened: http://mametesters.org/view.php?id=6531
Tested under three different systems, all with a clean install with the same exact results.
Edited by Trebor (03/31/17 12:34 AM)