dax driver issues

WA5YOM

AFter latest Windows 10 update and after numerous DAX driver uninstall and install attempts....still have a problem.....I am experienced in doing this before but the problem is very persistant this time......DAX IQ 1 and 4 display a driver error......


I have submitted a ticket.....but this should not be that difficult to resolve...I really do not want to uninstall and reinstall SMART SDR all over again.....

Mike Presnell

rgracer

The only way that worked for me was to completely uninstall SmartSDR. This is an involved process with several steps., not just uninstalling the program. Here’s the link. https://helpdesk.flexradio.com/hc/en-us/articles/204975589-How-to-do-a-Complete-uninstall-of-SmartSDR-for-Windows-from-your-PC

Jim KJ7S

Jim KJ7S

in the devices you only need to rename the ones that are wrong...highlight one you want to look at, click on settings,system,sound, find the Sound Control Panel (in upper right quadrant), hilight the device, select properties, rename the device, click ok, restart computer, restart SSDR. Hope this helps...Jim  KJ7S

WA5YOM

John - AI4FR

Jay Nation

Neil D Friedman N3DF

John - AI4FR

K0GGC

Hans Ficker

das Problemm müsste schon lange behoben sein. Bei Flexradio dauert das viel zu lange

ik3ghr Fortunato

ik3ghr Fortunato

https://drive.google.com/open?id=1tLlx4qTJaqAa6g59eF7qTqZ1p6UFzMuM Scrivi Procedures for audio inputs I used, but they are in Italian.una risposta

ik3ghr Fortunato

Pat

I have the same problem, and that after a full uninstall as noted above in this thread.  I went back and made sure that the Playback and Recording device lists were clean before restarting and beginning the 3.0.27 install, and they were.  What a mess.  I've spent hours of my valuable time on this.

Pat

Michael N3LI

Michael N3LI

Weird thing is that the Windows update does that renaming kind of randomly. The first time it happened to me, it renamed Everything DAX IQ RX 1, then 2, then 3, until every single driver was renamed. Second time it renamed everything, I fixed it by going Enterprise and blocking updates.

Michael N3LI

Poor Tim probably has dreams at night about repairing audio drivers. 8^)

Craig_KØCF

RFord

KM6CQ - Dan

After years of DAX issues on multiple machines my chosen solution is. I have a fresh image of my system all set up the way I like it without SSDR installed. When the Windows fall update comes out. I will **** away my system with the image, update windows and then install SSDR. This works every time and take less than 30 minutes.

ik3ghr Fortunato

Michael N3LI

I use a K3S as well at our contest station. It's a really good radio, but the Panadpter reminds me of a C-64, and the short push vs long push is annoying.

Anyhow, if switching to W7 or W10 Enterprise doesn't suit, nor iOS SSDR, or MacOS Dogpark - all stable OS' and Software, Perhaps a K3S is in your future. 

Pat

Michael, thank you for your comment!  This will give background to you and the other kind responses here.

I've had a KX3 for some time and from my experience the Elecraft gear just works.  I have the PX3 so I understand the P3's '80's architecture look, but it works.  I'm not so much a contester, but rather I have exposure to that Elecraft gear and it just works, and for my use case does so very well.  It doesn't consume my time...it is a pleasure.

So is the Flex 6600.  It too is a pleasure, as is SmartSDR (most of the time).

I'm a tech guy and was in IT all my life.  I saw the value in not upgrading software, as some propose.  Things do work...for a while.  However over my career I came to know that for me and the customer assets I managed, the best solution to yield the highest availability and security was to stay reasonably current, within the constraints of my customers (IT outsourcing business serving banking as well as other vertical businesses).  So for me personally I believe keeping W10 (Pro in my case) up-to-date provides the best overall solution.

I made the move back to Windows from a long-term Mac user point-of-view about 18 months ago (before my use of Flex).  I knew the legacy reputation Windows had for lack of reliability, unless manhandled by not upgrading or the like.  I am accountable for that decision...I accept that...I knew what was in store.  I can honestly say that other than the DAX issue, The Windows 10 experience has been overall a very good experience, given my history in IT Outsourcing and years of exposure to Windows based infrastructure.

I also know that architecture is critical to success in IT.  Flex has a great product...truly sincere about that point.  However they made a decision to put their SmartSDR architecture on Windows, and thus set up a very large exposure in the DAX area (many driver instances) to the known effect of Windows upgrades on clobbering 3rd party drivers.  In my book, they are accountable for that.  It costs their customer countless hours, if and when they chose to or need to upgrade.

The most important resource I have is my time, and I don't see anything changing that would cause me to believe I won't be fixing DAX drivers again and again with the current SmartSDR architecture, unless of course I chose to not perform maintenance which from experience will bring forward other issues over time.  I can't get the DAX fix hours back...that is a cost for me to the Flex experience, and a cost that will occur again and again.

That sums up where my head is at right now.  Sorry this is lengthy.  Everyone's input has been very useful and positive.

pat / nf8h

Ted VE3TRQ

I have a K3, KX3, and Flex6600M. For the reasons you set out above, Pat, I chose to run my 6600M on my Mac, with a Windows 10 laptop and a Windows 7 emulator (Parallels) as supporting players. The Mac is 100% solid, and for those times I use the Windows systems, a minimal amount of time keeps them functional. I love the K3/P3, but will never go back to them. The K3 gets used as my 2m radio because it has the transverter, but that will end as soon as I connect up the DEMI equipment I have for my 6600. No negative comment on your decision at all, just a different decision on my part.