I have Sentinel (v1.07_05) installed in multiple places on multiple types of systems (W7, a couple W10, the latter two VMs). No problems on any of them EXCEPT one. On that one, I get
Yes, I've removed Sentinel, and yes, I ran CCleaner to kill all the registry cruft before re-installing. Yes, I've tried turning off the Windows 10 firewall. Yes, I've tried Reconstructing Full Database. Yes, W10 is up-to-date (both on the one that is working and the one that is not). Yes, Virtual Box (and the "additions") are up-to-date. Same answer in call cases.
Networking works - all my files are in a Dropbox share and that works fine. And despite being in a VM, I have no problems
No problems with the USB connection, either ... except ... I just tested the firmware update and get the same message. Sentinel can see the uSD card in the radio and can load freqs, etc, but when Sentinel tries to compare the version of the the firmware on the card with what's on the server, it barfs. (That the firmware is up to date on the card makes no difference - Sentinel can't get to the server to compare versions).
"Oh, it's the VM! You should never run it in a VM!" Um, no. Until recently, this has been working just fine (wasn't always so, but in the last year or more it's been fine). I run a W10 VM on another host and it's fine.
Code:
Updating full database failed.
Operation is canceled.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host
Yes, I've removed Sentinel, and yes, I ran CCleaner to kill all the registry cruft before re-installing. Yes, I've tried turning off the Windows 10 firewall. Yes, I've tried Reconstructing Full Database. Yes, W10 is up-to-date (both on the one that is working and the one that is not). Yes, Virtual Box (and the "additions") are up-to-date. Same answer in call cases.
Networking works - all my files are in a Dropbox share and that works fine. And despite being in a VM, I have no problems
No problems with the USB connection, either ... except ... I just tested the firmware update and get the same message. Sentinel can see the uSD card in the radio and can load freqs, etc, but when Sentinel tries to compare the version of the the firmware on the card with what's on the server, it barfs. (That the firmware is up to date on the card makes no difference - Sentinel can't get to the server to compare versions).
"Oh, it's the VM! You should never run it in a VM!" Um, no. Until recently, this has been working just fine (wasn't always so, but in the last year or more it's been fine). I run a W10 VM on another host and it's fine.