Rather than calling up Dudley right away or opening a HelpDesk Ticket, I decided to use Tim's all-inclusive instructions (https://helpdesk.flexradio.com/hc/en-us/articles/204975589) to completely remove ALL old versions of SmartSDR and install SmartSDR (v)1.7.30 as a clean, brand-new installation. That resolved the DAX Driver error.
For most software vendors, when a new software version is released, the installation software FIRST removes the old version and then installs the new version such that only one version of the vendor's software is installed on the hard drive at a time. For the Flex Radio Systems SmartSDR, unless one does Tim's complete removal procedure (a manual step-by-step process I might add), your Add/Remove Programs Window will possibly show five or more versions of SmartSDR. And as a CAUTION NOTE, you cannot use the Add/Remove functionality to remove the older SmartSDR versions. You MUST use Tim's method to safely remove the old versions which includes removing the most recent version first.
(EDIT: According to this post by Tim, you CAN remove old versions with no harmful effects. If that is the case, why Tim, does one need to use your procedure to completely uninstall SmartSDR for Windows starting with the latest version first?)
Sooooooo... Why can't the SmartSDR Installation software be written such that it does NOT leave residual old versions of SmartSDR on the hard drive? Then, should a DAX Driver error screen occur in the future, all one would need to do is to remove the one-and-only current version completely and re-install it whereby resolving the error.
Makes sense to me...
73, Dave Hamm K4EET
Even for those of us that like to keep the previous version, it would be nice to have this option for those occasions when we have an issue and want to start clean.
Regards, Al / NN4ZZ
al (at) nn4zz (dot) com
6700 - HW.................... V 18.104.22.168
SSDR / DAX / CAT...... V 22.214.171.124
Not for this particular problem, but for other incidences, I have done that. Not a bad idea to have a recent restore point handy. Easy way out.
Come on gang! We are all at least General class operators and supposedly at least a little more technically savvy than the average Schmo. I don't expect Flex Radio to be in the diaper changing business. It's time for a few of you to Cowboy Up!
Inconvenient - My logging software can be configured to launch external programs but, since the path changes each time, it has to be modified for each new version release.
Messy - I have many directories of obsolete Flex software. I can imagine what the Registry entries look like.
We're making progress on DAX slobbering unused audio drivers everywhere (still a long way to go). CAT is being unbundled at last for those of us who don't interface to COM ports anymore.
Let us finally admit that many of us use the hamshack machine for things other than ham radio and clean up our act on install practices.
Multisystem ops who use multiple versions side by side have my deep sympathy, but surely there aren't many of them! As a rule, the burden of "big" installations should be borne by those folks -- who have the resources -- and not the vast majority (?) of us with simple setups.
73 Martin AA6E
Would a separate "Remove Everything" application work for those who would like to see things done differently.
On automatically deleting the prior versions, I would think it very wise to have a way to opt-out of a choice that could leave your system radio dead if something didn't work out well.
The statements that no other software leaves old versions intact puzzle me, as several major packages we professionally use do leave the prior setups intact or archived. We usually delete them after a couple backup-cycles if the latest software has proven stable in our instances.
- 5259 Conversations
- 1601 Followers
- 3094 Conversations
- 634 Followers
- 3629 Conversations
- 940 Followers
- 878 Conversations
- 150 Followers
- 2990 Conversations
- 855 Followers