05986: All sets in msx.c: Cartridge mapper not detected using Full Path

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
05986	Core	Minor	Always	Jul 12, 2015, 16:08	Jul 14, 2015, 19:22

Tester	Testweazle	View Status	Public	Platform	MESS (Official Binary)
Assigned To	wilbert	Resolution	Fixed	OS	Windows XP
Status [?]	Resolved			Driver	msx/msx.cpp
Version	0.163	Fixed in Version	0.164	Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	05986: All sets in msx.c: Cartridge mapper not detected using Full Path
Description	When using full path method MAME is not properly detecting the cartridge mapper type, resulting in constant rebooting of the system. When using shortname method the cartridges run as normal. The mapper info is in the XML file.
Steps To Reproduce	EXAMPLE: Full path method broken: mame hb101p -cart1 "c:\mame\roms\msx1_cart\nemesis3.zip" Shortname method works fine: mame hb101p -cart1 nemesis3
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets in msx.c

Attached Files

No.11870 B2K24 Senior Tester Jul 14, 2015, 00:16	Isn't this intended behavior and the same things happen with NES? Without softlist loading, how can the machine possibly know which mapper is correct?
No.11871 wilbert Developer Jul 14, 2015, 18:41 edited on: Jul 14, 2015, 19:18	I checked the code a bit more, there is some mapper auto detection code but apparently it is too limited at the moment to detect the mapper used in that game. B2K24: Some other systems also have some mapper detection code which attempts to detect the mapper from the rom image. It is not always perfect though. Hah, what a silly bug. It actually helps if we read the rom file we want to run the detection on ;) Fixed in git already.

No.11870

B2K24

Senior Tester

Jul 14, 2015, 00:16

Isn't this intended behavior and the same things happen with NES?

Without softlist loading, how can the machine possibly know which mapper is correct?

No.11871

wilbert

Developer

Jul 14, 2015, 18:41

edited on: Jul 14, 2015, 19:18

I checked the code a bit more, there is some mapper auto detection code but apparently it is too limited at the moment to detect the mapper used in that game.

B2K24: Some other systems also have some mapper detection code which attempts to detect the mapper from the rom image. It is not always perfect though.

Hah, what a silly bug. It actually helps if we read the rom file we want to run the detection on ;)
Fixed in git already.