Having issues upgrading to SmartSDR CAT v1.2.17?

  • 2
  • Question
  • Updated 4 years ago
  • Answered
With SmartSDR v1.2.17, you must uninstall the previous version of SmartSDR CAT before installing SmartSDR v1.2.17.  If you do not, there is a possibility that the virtual serial port drivers will not load correctly.

This is the step-by-step procedure to use.

1.) Open SmartSDR CAT and make note of how your virtual com ports are defined.
2.) Close SmartSDR CAT
3.) Follow the procedure, Uninstalling SmartSDR CAT prior to SmartSDR v1.2.11 on page 12 of the SmartSDR v1.2.17 Release Notes.
4.) Reboot your PC.
5.) Install SmartSDR v1.2.17
6.) Reboot the PC when prompted.

Now you should be good to go.  You may have to e-create your virtual com ports after installing SmartSDR v1.2.17, but you will not have to do it for any subsequent SmartSDR CAT upgrade unless there is a driver upgrade, which is not likely.

Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes

Posted 4 years ago

  • 2
Photo of Stan - VA7NF

Stan - VA7NF

  • 419 Posts
  • 96 Reply Likes

Please confirm that I must stop DAX and uninstall the previous version of SmartSDR to have the DAX drivers removed and replaced by the new install. 

It seems that if I don't do this I don't see the new drivers installed.

Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
DAX has not changed.  There is noting you have to do differently for it.
Photo of Ken - NM9P

Ken - NM9P, Elmer

  • 4025 Posts
  • 1248 Reply Likes
Wonderful!  it will be nice not to need to redefine all those CAT ports any more!  However, I have gotten so used to doing it that it only takes me about 2 minutes to define about 12 of them any more!  Thanks!
Photo of Brian Morgan VK7RR

Brian Morgan VK7RR

  • 57 Posts
  • 11 Reply Likes
Like Ken I find that redefining the CAT ports is a snap. Every once in awhile, I have to do it anyway as sometimes a dedicated port will open as a non dedicated port, so I have to delete it and then reinstall it as a dedicated port again. This has been the case since day 1. I have never found a convincing explanation, but as it only takes a moment to re-set it, it does not concern me.