New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In case of multiple FDC's, it's not clear which drive is which #1544
Comments
Here's an idea on what could be done, but I'm not sure it's perfect (e.g. on a FS-A1GT the internal drive shows for controller "Memory Mapped FDC", which is not very clear.... for external drives the name is very distinctive though, so perhaps it's still good enough). |
Can you give some background on where this request comes from? And most of the time you don't actually want to know the name (or the slot) of the drive, but the drive letter that is assigned to it in MSX-DOS. This proposal doesn't help with that. For example this assignment can depend on software (e.g. started with CTRL or SHIFT). So there's not much openMSX can do for this (we try to avoid giving openMSX knowledge about the OS that is running: dos1, dos2, fuzix, ...). So I agree this proposal adds "some" extra info. But it's not always the right info (as in: the thing you actually want to know). And the extra info is also rarely needed (internal + external drives). So I'd give this low priority. I will of course help if you still want to work on it. |
Origin is here: https://msx.org/forum/msx-talk/hardware/issues-running-dsk-games-on-emufdc-on-turbo-r On a real system it is very clear in which physical drive you put a disk. But in openMSX it isn't at all, that's why I think we should improve that. |
Suppose you connect an external drive to the Panasonic FS-A1GT in slot 1. Then it's very unclear which physical drive is meant with "drive A" and which with "drive B". Perhaps the slot, or the name of the device should be shown somewhere (e.g. ImGUI and of course via some console query. Add a new field to the output of 'diska'?
The text was updated successfully, but these errors were encountered: