SDRPlay RSP1 & SDR#?
Posted: Sun Feb 11, 2018 5:55 pm
Hi;
I am trying to get the SDRPlay RSP1 to work with SDR# ver 1.0.0.1361 but not having any luck.
I was informed on another forum that this ver of SDR# would work with the RSP1.
I have downloaded and installed the following in the SDR#_1361 folder on my Win 7 box:
SDR# ver 1.0.0.1361 - not actually installed; just extracted the .zip to here
EXTIO SDRPlay ver 1.1 (Nov 2017) from the SDRPlay downloads site
API/HW Driver ver 2.11 (Nov 2017) (for developers only) - didn't notice that before, so I probably don't need this.
The API driver also installed the C++ 2012 redist package (which I probably didn't need)
The RSP1 is working properly with SDRUNO ver 1.21 and still is after the botched SDR# install.
When I run the program "SDRSharp.exe" from the folder which contains all of the other stuff I installed, I get the following errors:
"Failed to locate API registry entry: HKEY_LOCAL_MACHINE\Software\MiricsSDR\Tools... ERROR 0"
After clicking the OK button, another error pops up:
"Error loading 'ExtIO_SDRplay.dll' Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
After all the two error dialogs are dismissed, SDRSharp does open, but there is no SDRPlay RSP listed in the Source selections.
Searching the Windows registry I find that the MiricsSDR key does exist, but there is no \Tools subkey there. The only subkey is \Api which has the REG_SZ value set to the install folder for the api (which is the same folder that SDRSharp is in).
Perhaps I should have allowed ExtIO to install in the default folder but I wanted to keep all the new files out of the working SDRPlay folder in case I messed it all up. At least this way I still have SDRUNO (both ver 1.21 and 1.13) working.
Looking at the SDRPlay download site, I see that there is a Mirics DVB-T Demodulator. Do I need this as well?
In the end, I'm not sure why I want to have SDR# at all. I have been using SDRUNO since I purchased the RSP1 back in Nov 2016 and have liked it a lot. But I got an idea that SDR# has something that SDRUNO does not. I'm not sure what that is; it is something I read in another forum.
So, should I pursue this or just be happy to have SDRUNO?
I am trying to get the SDRPlay RSP1 to work with SDR# ver 1.0.0.1361 but not having any luck.
I was informed on another forum that this ver of SDR# would work with the RSP1.
I have downloaded and installed the following in the SDR#_1361 folder on my Win 7 box:
SDR# ver 1.0.0.1361 - not actually installed; just extracted the .zip to here
EXTIO SDRPlay ver 1.1 (Nov 2017) from the SDRPlay downloads site
API/HW Driver ver 2.11 (Nov 2017) (for developers only) - didn't notice that before, so I probably don't need this.
The API driver also installed the C++ 2012 redist package (which I probably didn't need)
The RSP1 is working properly with SDRUNO ver 1.21 and still is after the botched SDR# install.
When I run the program "SDRSharp.exe" from the folder which contains all of the other stuff I installed, I get the following errors:
"Failed to locate API registry entry: HKEY_LOCAL_MACHINE\Software\MiricsSDR\Tools... ERROR 0"
After clicking the OK button, another error pops up:
"Error loading 'ExtIO_SDRplay.dll' Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
After all the two error dialogs are dismissed, SDRSharp does open, but there is no SDRPlay RSP listed in the Source selections.
Searching the Windows registry I find that the MiricsSDR key does exist, but there is no \Tools subkey there. The only subkey is \Api which has the REG_SZ value set to the install folder for the api (which is the same folder that SDRSharp is in).
Perhaps I should have allowed ExtIO to install in the default folder but I wanted to keep all the new files out of the working SDRPlay folder in case I messed it all up. At least this way I still have SDRUNO (both ver 1.21 and 1.13) working.
Looking at the SDRPlay download site, I see that there is a Mirics DVB-T Demodulator. Do I need this as well?
In the end, I'm not sure why I want to have SDR# at all. I have been using SDRUNO since I purchased the RSP1 back in Nov 2016 and have liked it a lot. But I got an idea that SDR# has something that SDRUNO does not. I'm not sure what that is; it is something I read in another forum.
So, should I pursue this or just be happy to have SDRUNO?