oh, i forgot
4. You don't understand how to use the codes.

use tools > console > enable and load the rom again
get the ROM game code & etc. through to ROM crc
compare to specifications for cheats you found
copy results here and link to cheats you're using (and specify which cheat fails and where in the game you're trying to use it)
I'm sure we'll find a mismatch in there or else a foul in #4

I'll smoke a fat one in honor of your great achievement if you don't mind

Fantasy Life is a 3ds game. What are you doing on a NDS forum?

0 is not a valid setting

your controller and/or the drivers suck and don't support directinput. You'll need to find a 3rd party pad mapping program (does autohotkey work?) to convert it to keystrokes or a virtual directinput device

filed a bug here to track it

https://github.com/TASEmulators/desmume/issues/829

Sounds like one version of drastic has a bug in its save data handling and another version has code designed to recover from that error. Try updating your drastics. If that doesn't help, ask for a refund. Save files corrupted by drastic is not desmume's concern

The only setting that could help is config>display method. Ultimately this is discord's fault, not desmume's.

Randomizer corrupts the rom. Get a refund.

from what URL did you download desmume

You shouldn't turn off the interpolation since no workstation outputs at "32768hz" so resampling must occur.  Melonds isn't outputting at 32768hz, or if it is, it's relying on your OS to resample to 44100 or 48000 internally and you can't control that interpolation (therefore it's not a fair comparison between the emulators).

No situation should be prone to any audible errors when interpolation is used as intended.

If you could pick timer values that yielded exactly 44100 or 48000 then they could play 1:1 on an emulator, but it is impossible to pick such timer values. The timing is either based on dividing the ugly value of 33513982 (as desmume does) or the prettier value of 33554432 (0x2000000) (which is defensible but not what we do). Neither of those have 44100 or 48000 as divisors. You can only play, for instance, at 33513982 /759 ~= 44155.444hz. Consequently, interpolation must occur under all circumstances.

Personally, I'd just use the unmodified 44100 sounds from the PC version, for both emulators. Once your listening test is no longer conducted in a mistaken manner with the interpolation disabled, I doubt you will hear much difference. Of course melonds may sound different from system to system since it relies on the OS to do resampling work so that's an impossible goal to chase.

Now as for 1:1 results on the device itself.. now is the time to say I believe all the extant documentation is wrong. The audio is NOT actually 32768hz. It is simply CLOCK/1024: 32728.49.. or whatever. It depends on the oscillator. What you want to do is is set the timer so that everything is evenly divided. In other words, set it to be divided by 1024 (give or take a factor of 2 in the register configuration). This way, every input sample from the voice will be played for exactly one "output sample". In this case I would downsample the 44100 from the PC game to 32728hz using the best tool you have, and this is simply for the sake of making the pitch match expectations once played 1:1. In terms of fidelity, choosing that channel clock divider will make sure whatever waveform you have is played in a relatively comprehensible way. Although I have my doubts that anyone could hear any minor discrepancies on the NDS even with headphones after it's sent through the system's other strange audio circuitry to make it all harsh and cheap sounding.

Bug in wine. Report to wine.