OK, I guess that's a feeble adjustment.

most likely you have a broken dsv (save) or dct (cheat) file, then. that would get fixed by nuking all your files (make backups first) and rebuilding your emulation environment from scratch

so what did you change? did you update desmume? did you change your GPU or drivers? did you change your security software? did you move your files around?

what is the actual problem with the ".desktop" file?

delete your ini file

your username has non-english characters in it, therefore the path the desktop (and the desmume directory and the battery subdirectory) has non-english characters in it, therefore despite 100s of bugs filed and fixed about things like this in desmume, there are still more problems. don't use a username with a non-english character in it (don't use spaces either) and you can avoid a lot of problems with this software and many others.

should be fixed in https://github.com/TASEmulators/desmume … bce32e63dc but only someone unwise enough to use a username with a non-english character in it can test it for sure

how long does it take to get to a fossil cleaning part? I gave up after I got to the town. can you post a .dsv file?

I have no idea why. Nothing changed the fundamental problem which was needing to rejit too much every time the program is written to by the cheat. I am suspicious and worried that something's gone wrong and the cheat processing has broken.

hope interest from developers will regularly arrive, like old times

because the nightly version is built with clang, probably.
I don't care if nobody likes it.

this is discord's problem, not ours, but you should change config > display method since it will probably be less likely to agitate discord's crusty code

I dunno man, make backups of your settings before you mess them up. This happens to lots of people but we have no idea how. They're all hacking or cheating or changing something around. It's also possible you didn't change anything but your save file is corrupted due to computer malfunction or closing desmume while it was in the middle of saving; you should be making backups of your .dsv if it's precious to you, like you should make a backup of any precious file. It's also possible you've been hacking the rom and trying to load the old save file and you've just struck out by creating a hacked rom that creates save files that no other hacked roms can read. We can't guarantee what will happen if you hack roms and try to load data other rom versions created, but white screens at bootup are a likely outcome.