Home Page Forums MAME MAME UI quirks with slots and possible solutions

This is "impossible" unfortunately[1]: at loading stage MESS converts disks (and tapes) to be a flux fo raw data, so that all info added in the dsk/td0/etc formats before creation are discarded (they were not part of the original disk)

During loading, they can be logged either to .log file or to the log window of the debugger, if whoever wrote the support for the disk format added the corresponding code, but after loading stage they are gone and there is no easy way to recover it


[1] quotes are mandatory, of course, because with some re-design everything is vaguely possible, but the modern floppies seem to move in the opposite direction discarding anything that is not low-level raw data

Well for people who don't know there's a thing called a 'manual' ;-)

Seriously though, for the uninitiated there's Cloanto's Amiga Forever which is basically WINUAE with plug and play and lots of stuff auto-included under the hood.
Give it a try if you haven't already.

I have implemented a first stub of device menu.

you start e.g. "mess ibm5150 -isa5 hdc" and you enter Slot Devices menu

if you select one of the mounted devices, like the serial mouse or one of the HDC cards, and you press Enter, you are now prompted with a simple description of what device the option corresponds to, and what suboptions rely on it

OTOH, if you change one of the slots to a value that is not currently mounted, e.g. to a soundblaster 1.5, you can have a preview of the options that get enabled when you mount the option, even if they are not currently available


opinions?

wow.

Awesome! This is clearly much much better than before.

However, I think that the text "Player input" should be renamed for MESS, I mean who says that you only play games with your mouse? ;-)

Great progress, I was wondering if it could be added to change the Ram size within the slots?

at the moment, we have a unique RAM device for each system and its configuration via the UI is not possible.
we will hopefully have RAM converted to be a slot device, eventually, and that will allow for both easy config in UI and for configurable RAM in other slot devices...

in the past few days, I had a lot of headaches fighting with the interaction among UI and slots, but I think that the result was worth the time I have spent on in.
with previous code, there were a lot of cases where the internal UI was not handling properly devices that creates further image or slot devices, because when the menu were first created there were not many devices triggering subdevices as we have now.

to make a few examples, in 0.157 if you launch sms and then try to mount the multitap option in Slot Options, after Reset the multitap is stuck using 4 joypads and the corresponding options cannot be configured from UI

again, in 0.157 if you launch fds and then you mount the Game Genie from the UI, the passthru slot does not acknowledge any image you attempt to mount from the File Manager (you can mount it, but the system reboots and the second cart is gone)

finally, in 0.157 if you mount c64 with no carts inserted and then add the cbmieee cart from the File Manager, you can get both previous bugs combined: at reboot, neither the -cart2 device nor the slot sub-options would work as they should

with current git tree all the above behaviors have been rectified, and the sub-options can be finally configured as one would expect