Cannot Get MiSTer Logo off of Menu Core

For topics which do not fit in other specific forums.
Snappy
Posts: 2
Joined: Wed Jan 18, 2023 2:19 am

Cannot Get MiSTer Logo off of Menu Core

Unread post by Snappy »

I want the mister logo removed from the top left of the menu, so I've made this change to the config file:

; 0 - disable MiSTer logo in Menu core
logo=0

_

However, the logo remains. What am I missing? Thanks in advance!

Milspex
Posts: 165
Joined: Wed Jun 10, 2020 6:46 pm
Has thanked: 38 times
Been thanked: 35 times

Re: Cannot Get MiSTer Logo off of Menu Core

Unread post by Milspex »

perhaps its on your wallpaper? ;)

Snappy
Posts: 2
Joined: Wed Jan 18, 2023 2:19 am

Re: Cannot Get MiSTer Logo off of Menu Core

Unread post by Snappy »

Milspex wrote: Sun Jan 29, 2023 5:14 pm

perhaps its on your wallpaper? ;)

Thanks, but it's not on the wallpaper.

Malor
Top Contributor
Posts: 860
Joined: Wed Feb 09, 2022 11:50 pm
Has thanked: 64 times
Been thanked: 194 times

Re: Cannot Get MiSTer Logo off of Menu Core

Unread post by Malor »

Just in case: you did try rebooting? And then verifying that logo=0 is still in the INI file?

If it works after a warm boot, but not a cold one, that usually means that your config directory is on a different filesystem than the main Mister binary. If it's not up yet when the menu launches, it will use default settings. When you warm boot, the ini file is available, and the menu will work correctly. If you always put the config dir on the filesystem that contains the MiSTer file, this won't happen.

Lightwave
Posts: 232
Joined: Sun May 24, 2020 10:06 pm
Has thanked: 110 times
Been thanked: 68 times

Re: Cannot Get MiSTer Logo off of Menu Core

Unread post by Lightwave »

Also, if you use alt MiSTer.ini configs make sure you are editing the right one.

hitm4n
Posts: 104
Joined: Sat Jan 30, 2021 9:20 am
Has thanked: 2 times
Been thanked: 16 times

Re: Cannot Get MiSTer Logo off of Menu Core

Unread post by hitm4n »

I have had this issue, you have to re-enable it, then reboot, then disable it again. It was related to an older 3rd party "update all" script, at least thats what Sorgelig told me.

Post Reply