Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05169 Interface Major Always Mar 6, 2013, 15:49 Apr 23, 2019, 11:30
Tester Robert Gault View Status Public Platform
Assigned To Resolution Invalid report OS
Status [?] Closed Driver coco3.cpp
Version 0.148u1 Fixed in Version Build
Summary MESS-specific 05169: coco12.cpp: The user selected slot device is ignored in recent svn sets. starting about svn 21000 latest test 21596
Description When any .rom image is mounted in CoCo Cartridge Slot, the data in the .ini file or the selection made via scrolllock/tab Slot Devices is ignored. What is used is the value in src/mess/machine/cococart.c as shown below.
//  get_default_card_software

const char * cococart_slot_device::get_default_card_software(const machine_config &devlist, emu_options &options)
	return software_get_default_slot(devlist, options, this, "pak");

As a result, if an alternate disk ROM image is mounted, emulation drops back to Extended Basic and all disk commands are invalid. It also means all other alternative settings are ignored; fdc, fdcv11, cp400_fdc, rs232, orc90, banked_16K, and multi.
Steps To Reproduce Start any coco emulation that accepts disk commands and mount anything in the cartridge slot, even the disk rom used in the ROM directory.
Additional Information If you change the cococart.c line above to make fdcv11 the default, then disk roms mounted in the cart slot work. This is not the solution but indicates that the default value seems to always be used and the .ini value or internal UI selection is ignored.
Regression Version
Affected Sets / Systems coco12.cpp
Attached Files
There are no relationship linked to this issue.
User avatar
Mar 24, 2019, 00:46
This is expected behaviour. If you load a loose .rom image it will always assume it is a standard pak cartridge. Any ROM that requires additional hardware to be selected in the slot device must be loaded from the softlist, which will specify which slot option is required to run the ROM. Using the File Manager to load a ROM will always override whatever was selected in the Slot Device, defaulting it back to pak.
User avatar
Apr 23, 2019, 11:30
Closing due to expected behaviour.