DAX error: Here we go again

Filip - ON7FD

Bill -VA3WTB

Matt (K0KB)

DAX is the only thing that ever breaks for me.  I have about 40-50 PCs running myriad programs.

Filip - ON7FD

Bill - VA3WTB , do you really think Microsoft is awake about Flex, don't think so.

Bill -VA3WTB

It's not only Flex having issues with Microsoft updates. The blame is on Microsoft.

Matt (K0KB)

Probably best to not engage the cheer squad.  All they know how to do is cheer.

Bill -VA3WTB

what ever that means...lol

Steve K9ZW

The DAX issues are a shared responsibility.  I believe FRS has been continuously working towards solutions, though the process is certainly not helped by Microsoft's unresolved core problems with drivers during updates.

Outstandingly FRS has stepped up with the one solution that has been fully in their control - educating us, the ad hoc "repair team" guys, and the formal DAX repair support FRS has been doing.  This may not be the most convenient for those affected by DAX Driver Naming corruption but it is effective.

As always if you can fix the problem if it comes up, open a help ticket.  I had to do this on a PC that eluded my efforts. 

Someday one or both of the partners in this issue may fix the underlying issue or have a less hands-on repair procedure.  But for now we're either stuck with getting by with the Help Ticket fallback repair, locking down our systems so they never update on their own, or moving on to other options. 

Most of us find the upside of running our Flex-6000s greatly in favor of keeping them despite the DAX driver upsets. 

Thinking completely out loud with an idea - would many of us be willing to run a dedicated SmartSDR Client PC that is locked down along the lines of the Maestro? 

The general thoughts have been we value our platform's flexibility and multi-tasking capabilities more than the protection from DAX naming issues.  

The same capabilities-control/interaction issues have made a Linux and Android client difficult enough that neither FRS or third-party developers have ready to use options yet.  I think my first 6700 delivered in 2013, so we're over five years into things.

73

Steve
K9ZW

Blog:  http://k9zw.wordpress.com 

Filip - ON7FD

Bill -VA3WTB

Filip, I really don't know what you want Flex to do when Windows has this big bug?

Thomas NE7X

Agreeing Microsoft is the root cause of this issue, Flex is promoting and selling this feature. If the feature does not work correctly with Microsoft, Flex should not promote their product with this option.

Ernest - W4EG

Steve K9ZW

@ON7FD - Thank you Filip. @All - Please assume that FRS continues to work towards solutions. Sometimes we lose sight of how complicated things can be. There are iOS and MacOS clients if you truly want to avoid the Windows issues. For better or for worse most of us have Windows PCs in our shacks or a virtualized instance of Windows. With so many other ham programs expecting a Windows environment it is limiting if you do something else. If you take time to learn and understand the Windows update processes the flirting with disaster is not limited to just DAX and the issues are complex as to the why. Your hardware and software may not all work after the next upgrades yet you are not realistic if you try to keep your system static. Features are depreciated, broken or redefined. Ditto with workarounds and API hooks. Fairly dynamic. What it is is what it is. My hope is that this issue improves over time. 73 Steve K9ZW Blog: http://k9zw.wordpress.com

Joe N3HEE

I believe that a PowerShell script could be used to enumerate the DAX sound devices and then replace them with correct names and order. 

Bill -VA3WTB

And if it were so simple Flex would have done that a long time ago.
Dax works very very well, till an update scambles everything.

KC2QMA_John

Steve K9ZW

Perhaps if, and only if, the Microsoft induced problems were consistent by being limited just to a renaming/reordering process.  

There are plenty of other threads, FRS website resources and anecdotal stories of how, in particular individual instances  the problem was driven deeper into the Windows morass of dependencies.  

There seems to be differences in what update mischief happens if your system Windows history differs, if other installed software has touched audio drivers, and other variables.  

If a script was coded to abort with a "Open a Help Ticket" message for anything other than a standard plain name/order corruption instance automation could help.  

Given you can really mess up a system with the process and the variability of what the remote tech actually needs to do would this script really work? 

Or would it embolden folk into totally screwing up their systems?

As an aside FRS told me that sorting out user repairs that went off the rails takes more time than just doing the basic fixes they remotely offer.

73

Steve
K9ZW

Blog:  http://k9zw.wordpress.com 

Tom N5MOA

Joe N3HEE

DaveC

BTW Tim was able to resolve my issue. He also said an update for the DAX should be out soon to resolve this once and for all.