[hpsdr] Ozy/Magister will likely stop working on Win10 in about 60 days

[Dick Faust]

Does anyone have knowledge that this signing is directly tied to UEFI / 
Secure boot in the BIOS ?   When Win 10 first came out I "upgraded" on 
MBR [now called legacy] boot with both x32 and x64 systems with out a 
problem.  If converting to boot MBR/Legacy would solve the problem, this 
would not be a very difficult task as build 1607 ISO's are now available 
with direct download from Miserable$oft, just remember to get your 25 
digit key first.

I have used the Win 10 ver1607 release and there are many more issues 
there than just this.

Another possibility is to just dedicate a Win 7 or XP system to the 
Ozy/Magister system.  There are plenty of motherboards/older OEM systems 
that will run very well if dedicated.  Intel NUC's are very small and 
can VESA mount on a monitor.

A solution that I would really like to see is a move to a real operating 
system like Linux with ready to run packages for all of the openHPSDR 
software.  The biggest detraction to Linux, for new users, is the need 
to find, configure and compile all of the the various required 
libraries.  A package for a single distro like Mint/Ubuntu would get a 
lot of users up and running very quickly. This would also eliminate the 
inevitable future Micro$oft problems, which are certain to be as bad or 
worse than this one.

Dick K9IVB

On 8/20/2016 7:51 AM, George Byrkit wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
> Dear all,
>
> So Microsoft has a policy for double-signed drivers on Windows 10 that didn't exist
> before, and it will take place between 60 and 90 days after the release of Windows 10
> Anniversary (build 1607).
 >  Snip