Actually I shoudl have titled this post “The Ugly Soft Underbelly of SDR Software Defined Radio that Uses a Separate Windows Computer to for anything other than User Interface!”
As described my contesting weekend was a bust – with a good share being basic computer woes.
The PowerSDR version of SDR I am using in the shack is absolutely dependent on having PowerSDR running successfully.
And PowerSDR is just yet another Windows program.
My particular Dell has having huge issues with wanting to call the mothership, update everything and demanding a series of reboots and software repairs.
There was absolutely no reason for this misbehavior, having ran 100% the weekend before and the weekend before that.
So what happened?
It was like every program on my machine wanted to get in on the update fun!
Then DDUtil either was updated or first recognized an update, and got into a locked processes battle with AVG Anti-Virus which was doing its own update,
PowerSDR crashed or part crashed every couple minutes or it if didn’t DDUtil took the lead and crashed.
AVG required a c complete removal and reinstall as it was convinced its installer had been hijacked.
Now I have Linux based computers that I shut down once a year to dust out and check. At work we even had a OS-2 Warp system that ran for years untouched.
But not Windows which just can’t seem to leave a working configuration alone.
Now this will all change with the next generation of SDR radios which return the Windows PC to what it is reasonably good at – as a user interface – and these new SDR have all real processing internal in their box with Linux running on a high powered processor.
I am sure there is amuch I can do to limit – to mitigate – the downside of Windows, but I ask “why should I have to?”