I talked with you about it before (a long time ago) on MRC but I restart my request to avoid key conflict with other interfaces, firmwares, etc. Please, see the thread at link below for the explanation with an example.
The advantage is only one key would be used during the boot and even this one could not conflict because it would be usable only for a small period of time.
Other request: If possible, it would be nice to be able to "disable" slots that we specify (to prevent ROMs from being executed at startup).
Hi Konamiman,
I talked with you about it before (a long time ago) on MRC but I restart my request to avoid key conflict with other interfaces, firmwares, etc. Please, see the thread at link below for the explanation with an example.
https://www.msx.org/forum/msx-talk/development/routine-to-bypass-a-firmware
The advantage is only one key would be used during the boot and even this one could not conflict because it would be usable only for a small period of time.
Other request: If possible, it would be nice to be able to "disable" slots that we specify (to prevent ROMs from being executed at startup).