DAX error: Here we go again

  • 3
  • Problem
  • Updated 1 week ago
Flex it is time that you solve this persistent and recurring problem. Windows does its regular updates and you chose to work with Windows .. give your users an adequate solution so that we do not have problems with YOUR product at just about every Microsoft update. This has been dragging on long enough.



Photo of Filip - ON7FD

Filip - ON7FD

  • 14 Posts
  • 1 Reply Like

Posted 2 weeks ago

  • 3
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3901 Posts
  • 949 Reply Likes
Not a Flex problem, Flex does not write for Microsoft. It is about time people put preasure were it belongs, on Microsoft as they have not been able to fix their updateing problems.

It is not only Flex that it breaks but, emergancy services, and so forth. About time Microsoft fixes a long standing issue.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3901 Posts
  • 949 Reply Likes
Filip, I really don't know what you want Flex to do when Windows has this big bug?
(Edited)
Photo of Thomas NE7X

Thomas NE7X

  • 57 Posts
  • 11 Reply Likes
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.
Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1557 Posts
  • 770 Reply Likes
@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
Photo of Joe N3HEE

Joe N3HEE

  • 432 Posts
  • 103 Reply Likes
I believe that a PowerShell script could be used to enumerate the DAX sound devices and then replace them with correct names and order. 
Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1557 Posts
  • 770 Reply Likes
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 
Photo of Ernest - W4EG

Ernest - W4EG

  • 621 Posts
  • 122 Reply Likes
Would you can you? 
Write a new program to substitute Microsoft's.
This was no issue when Flex started their software design; and now the new pea "nut" gallery is complaining.
They Do NOT need you to tell them what they need to do.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3879 Posts
  • 947 Reply Likes
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.
Photo of KC2QMA_John

KC2QMA_John

  • 779 Posts
  • 326 Reply Likes
All I can say this this DAX/Windows issue must be costing FlexRadio a lot of time and money.
Maybe a Batch file would help?
(Edited)
Photo of Tom N5MOA

Tom N5MOA

  • 95 Posts
  • 24 Reply Likes
I've had the Dax driver error message once on my Win10 machine.

That once was when I failed to close SSDR, close DAX/CAT, turn off the radio, turn off the ps and close any and every program using DAX.

I have my internet set to "METERED" and manually install each update after doing the above.

Knock on wood, so far so good.


Photo of Joe N3HEE

Joe N3HEE

  • 432 Posts
  • 103 Reply Likes
A script would work for checking and renaming DAX audio device labels.  The script will abort if it finds the proper device labels and order.  It will then open a web browser window to the Flex support page so you can open a ticket with Flex.  It will also output a list of other things to try while waiting on Flex support.  This will be a big time saver.  No more searching the Flex community for solutions that dont work.  

The script will be available around Q4 of 2020 as it is now contest season and I have no time to write it.  It will be a great tool and help countless Flex users with the dreaded Windows update dilemma !

The script should only be used by experienced computer professionals at their own risk of course.

I might be "nuts" for doing this ?
Photo of Dave

Dave

  • 98 Posts
  • 14 Reply Likes
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.