Erkdajerk wrote:The executable file on Yurbuh Tuggly's version is 9.6.5 whereas the "international" version is 9.6.2. This "international" version has a fairly lengthy sys.txt

Just for clarification, the "9.6.2xxx" EXE was sort of a 'bridge' version...the very first "2.0" Primo release with mixed code between 1.2 and newer stuff.
Nothing at all wrong with it...my first "Primo 2.0" release was based on it (and stolen\copied ..along with other bits developed by Chas521.. and then passed off as his own by persons who shall remain nameless).
But the "9.6.5xxx" EXE was really the final Primo 2.0 code.
If, for some reason, this solves your speaker issue, that's great...but I would suggest trying to use the "9.6.2xx" EXE only...with all my other stuff from the later release. I don't remember if data.zip is backwards compatible, so you may have to include that from the older release also, but try it without first. If you use the entire "International" Frankenstein jumble (including that hideous and unnecessary sys.txt)...and I'm trying to be polite here, believe it or not...., you will be likely to run into untold problems somewhere down the road that may be very difficult (or impossible) to solve.

Well, something in that "hideous and unnecessary" sys.txt seems to fix the muting problem. I tried that long sys.txt with your version of Primo and so far, so good.

I absolutely agree that most of the settings are bloated crap. It takes noticeably longer to boot and then to get a satellite fix.

I suspect one of the following settings is responsible for correcting the problem:

[tts]
tts_buffer=131072
announce_exit_directions=1
tts_logics=3
priority="HIGH"
always_say_road_names=3
announce_street_name=1
skip_exit_numbers=0

[dynamiccompressor]
compressor=1
ratio=9
gain=9

I added just those lines to Yurbuh Tuggly's lean and mean sys.txt and I will try it out tomorrow.

I'll tell you a little story about sys.txt under Primo...for either your benefit if you did not know, or others who may read this.
There are two basic Camps of Sys.txt-Users.
1) The Extremists.
They believe that just because a setting can be put in sys.txt, it should be put in sys.txt. Even to the point of repeating the defaults that are already part of data.zip. Doing so does nothing but slow the system down---loading the same thing twice. They also believe that instead of simply ticking a box/option within the Primo settings, sys.txt should automatically tick that box for you. Which means you can never change your mind...if you untick it, on the next startup it will be ticked again. They also may believe that all old settings from previous iGo versions also apply to newer iGo versions...which is wrong.
2) The Minimalists. They use sys.txt to only load the basics that may be absolutely necessary to accomplish a specific goal for specific hardware, and make all other settings within Primo or a Skin which may have additional choices. They realize that settings that may be appropriate for one device, are definitely not for another and could cause more issues than they solve.

And then there are the cases of particular distributions that have been so (badly) modified that they may need a scrollable sys.txt to function at all....because any proper defaults have been mangled.

Here is a fact: on some devices, Primo does not require a sys.txt at all. The scanning techniques used on the first start up are accurate enough to 'figure out' the hardware and apply the correct default settings without user intervention.

I think the settings you show above have little/nothing to do with how sound is routed to which speakers or whether speakers are muted or not. That is a device hardware/firmware decision.
BUT, whatever solves your issue is a good thing, regardless of what I think.