Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|08419||Interface||Feature||Always||13 days ago||13 days ago|
|Tester||star2root||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||Won't fix||OS|
|Version||0.247||Fixed in Version||Build|
|Fixed in Git Commit||Github Pull Request #|
|Summary||08419: All with a secondary optional BIOS: MAME should not prevent running a system if a BIOS that is not selected is not present.|
|Description||An error should be thrown a the time the BIOS is actually attempting to load. Missing additional BIOS ROMs should not prevent a system from running if they are not needed.|
|Steps To Reproduce||Use any system, delete a BIOS ROM that replaces another one when selected and try to run the system emulation from the builtin GUI.|
I think the way to fix this might be to mark the ROM as optional and the change the way optional ROMs are handled so that it distinguishes between an invalid check sum and file not found. If the check sum is invalid, it should throw a warning and continue because someone might be testing or debugging a ROM, but if the file is missing at the time of loading, it should throw an error and abort.
Saying this is too hard to fix or saying this is how it works is NOT a reason to mark this issue as invalid. Marking this as invalid without discussion is necessarily aggressive and counter productive. MAME should be throwing an error at the time MAME actually attempts to load the ROM, not when the emulation is launched. Saying "oh, just launch it from the command line" is NOT answer, as that simply makes the user interface pointless. If you are going to have a GUI, then support it and make it work PROPERLY. If here is a problem where this was reported incorrectly, we should discuss it first before marking it as invalid without discussion.
|Affected Sets / Systems||All with a secondary optional BIOS|
|There are no notes attached to this issue.|