[hpsdr] Problem with VAC and com ports following Win 10 update to 1803

[Richard Grubb]

Thanks Scott. You are right. Turning on Microphone access to Apps fixes 
the problem. I would not have thought of that privacy setting myself as 
the cause for a long time. I was not referencing the microphone as an 
input, but MS must be interpreting that setting more broadly in v.1803. 
I should remember to search the ANAN community for problem fixes.

While I am posting to the HPSDR list I should mention the other major 
problem caused by the 1803 "upgrade" to my Ham Radio setup that I have 
not seen mentioned here. All my serial "com" ports used for "CAT" 
control ceased operation. This was apparently due to a bug in the 
interface to the kernel mode driver, serial.sys. that prevented 
communication from the top level device drivers. The device manager 
claimed the com ports were working, but examining the event log for the 
1803 upgrade showed the errors. MS fixed serial.sys in the update this 
week. Everything did not immediately start working again however 
because, somehow in the process. the com port numbering had been 
scrambled and this had to be corrected manually in the Device Manager. 
Thank you MS for an interesting bug chase that should have been 
unnecessary.

73, Dick
W0QM, G3FNL

------ Original Message ------
From: "Scott Traurig" <scott.traurig at gmail.com>
To: "Richard Grubb" <richard.n.grubb at comcast.net>
Cc: "hpsdr at lists.openhpsdr.org" <hpsdr at lists.openhpsdr.org>
Sent: 6/13/2018 6:27:08 PM
Subject: Re: [hpsdr] Problem with VAC following Win 10 update to 1803

>***** High Performance Software Defined Radio Discussion List *****
>See:Â
>
>https://apache-labs.com/community/viewtopic.php?f=13&t=2819&p=5562
>
>73,
>
>Scott/w-u-2-o
>
>
>On Wed, Jun 13, 2018 at 8:08 PM, Richard Grubb 
><richard.n.grubb at comcast.net> wrote:
>>***** High Performance Software Defined Radio Discussion List *****
>>
>>
>>I am using PowerSRD mRX PS 3.4.9 with Hermes (Firmware 3.3). I had 
>>happily been using VAC to interface to Fldigi on the same PC using the 
>>MME drivers to couple to the MS sound mapper interfaces to the 
>>Creative Audigy sound card. After the MS Win 10 1803 update VAC no 
>>longer works and gives me invalid steam pointer errors when I enable 
>>VAC. All the other driver choices except ASIO give the same error. 
>>ASIO works to transfer audio to the PC's speakers but Fldigi does not 
>>know how to pick it up. This problem was not fixed by the June MS 
>>patches.
>>Â
>>Has anyone else run into this problem, or knows the solution ?
>>Â
>>Thanks, 73, Dick, W0QM, G3FNL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20180614/d2f6d581/attachment.html>