bootcore_timeout Not Working Anymore
Posted: Wed Oct 12, 2022 8:36 pm
I updated my Mister last night and the bootcore_timeout isn't working anymore.
In MiSTer.ini I have these two lines:
When turning on, it will load the lastcore, but it won't do the 10 second timeout as specified, it boots the core straight away.
Might be worth pointing out that prior to this update I was using a bootcore_timeout of 1, which wasn't a valid value in theory, but it did work. After the update I noticed an error message complaining about 1 not being an accepted value, so I changed to 10. The error is gone, but there is no timeout at all.
Thanks
In MiSTer.ini I have these two lines:
Code: Select all
bootcore=lastcore ; uncomment to autoboot a core, as the last loaded core.
bootcore_timeout=10Might be worth pointing out that prior to this update I was using a bootcore_timeout of 1, which wasn't a valid value in theory, but it did work. After the update I noticed an error message complaining about 1 not being an accepted value, so I changed to 10. The error is gone, but there is no timeout at all.
Thanks