Huh, I thought the point of that SETUP setting was to force the calculator to be quiet, even when a recalcitrant program turns on flag 26 and starts making a racket. Guess I should read the release notes more carefully, or, even better, update my DM42 and see it in action.

I believe there is also a sound enable/disable setting somewhere in the SETUP menu. That has to be enabled, AND flag 26 set, in order for sound to be produced.

Good point. I was trying to clarify that F26 doesn't affect key noise, but you're right to point this out (I ignore it, since, well F26 does what I need). The global setting is accessed by: [Shift][SETUP][3][4] - If selected, all sound is disabled, otherwise sound is controlled by F26.

IMHO, we've got a drifting (or even hijacked) thread here. We're posting under "hardware issues" > "buttons that don't register well". Several of the most recent posts deal with software issues (in particular, which flags and SETUP settings control the output of sound), however. That looks like a totally different topic to me. If true, please post in the appropriate section. Else please explain why I'm wrong. Thanks in advance.

Good point. I was trying to clarify that F26 doesn't affect key noise, but you're right to point this out (I ignore it, since, well F26 does what I need). The global setting is accessed by: [Shift][SETUP][3][4] - If selected, all sound is disabled, otherwise sound is controlled by F26.

Try it. Check the checkbox on the settings page to mute the beeper. Then go back to the home screen and set flag 26. Finally, go back to the SETUP settings page and you'll see that the Beep Mute control has been unchecked.

Try it. Check the checkbox on the settings page to mute the beeper. Then go back to the home screen and set flag 26. Finally, go back to the SETUP settings page and you'll see that the Beep Mute control has been unchecked.

This has been the case since Beta version 2.10.13

Thanks for clarifying the clarification!

I should have left well-enough alone, but as has happened in the past, I didn't see the subsequent messages on the next page.

I don't recall the genesis of the mute setting, but presumably it was because a global setting called "mute" was thought to be easier to find and understand than recalling which flag number to use, though of course we now have an online help system.

The good news is neither of these methods will affect key-click noise.

I have found that particularly the 8 button, and less often 7 and 9 will miss. In fact, if I am gentle, I can get almost any button to "click" without registering the relevant keystroke. Those least susceptible to this are those with the loudest click. Is this also just a matter of opening and cleaning up? When working on a firm surface, there is no problem, but when it is in my hands it comes up more.