<div dir="auto">I guess some update of win10 change some part of the driver without changing the driver version number. Redowngrading probably fix this. But this just a wild guess. The solution is important. The reason is less important</div><div class="gmail_extra"><br><div class="gmail_quote">בתאריך 20 במאי 2017 18:09, "Herb Gerhardt" <<a href="mailto:hgerhardt@wavecable.com">hgerhardt@wavecable.com</a>> כתב:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have been fighting similar problems on Win10 on my Baofeng UV-5R+. I too<br>
rolled back the driver to 3.2.0.0 to get my "genuine" cable that I purchase<br>
from HRO to work once I upgraded to Win10. It worked fine on Win7 and never<br>
had a problem with the latest driver but would not work on Win10 till I<br>
rolled the driver back. I then turned off the auto driver updates for this<br>
device. Everything worked fine after rolling the driver back.<br>
<br>
A few months later when I tried to read the radio again, it would not<br>
connect. I checked the driver and it was still the 3.2.0.0 driver in my<br>
listing. It took me several days till I updated the driver to the latest<br>
driver which of course did not work, but when I rolled it back again the<br>
3.2.0.0 driver from the pick list for this device, it began to work again.<br>
Don't ask me what is going on but then set it back for auto updates. I will<br>
now just roll the driver back every time I want to use this cable.<br>
<br>
I suggest you try to update your driver and then roll it back again to<br>
3.2.0.0 to see if that works for you. I know it sounds stupid but it is<br>
worth a try since it worked for me.<br>
<br>
<br>
Herb, KB7UVC<br>
NW APRS Group, West Sound Coordinator<br>
Our WEB Site: <a href="http://blog.nwaprs.info/" rel="noreferrer" target="_blank">http://blog.nwaprs.info/</a><br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:chirp_users-bounces@intrepid.danplanet.com">chirp_users-bounces@intrepid.<wbr>danplanet.com</a><br>
[mailto:<a href="mailto:chirp_users-bounces@intrepid.danplanet.com">chirp_users-bounces@<wbr>intrepid.danplanet.com</a>] On Behalf Of YT9TP -<br>
Pedja<br>
Sent: Friday, May 19, 2017 1:08 AM<br>
To: <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
Subject: [chirp_users] Cannot read Baofeng BF-888S<br>
<br>
I have strange issue with Windows 10, prolific serial adapter and BF-888S.<br>
It reports unable to download from radio.<br>
<br>
Driver is proper (version 3.2.0.0, update is disabled), and Chirp works fine<br>
with the same adapter and other radio (Baofeng UV-B5) reading and writing.<br>
<br>
I tried four different BF-888S and neither can be read.<br>
<br>
However, when I use the same USB adapter on my old Windows XP computer,<br>
Chirp easily reads and writes those BF-888S.<br>
<br>
Has anyone met with this problem?<br>
<br>
--<br>
<br>
YT9TP, Pedja<br>
<a href="http://www.yt9tp.iz.rs" rel="noreferrer" target="_blank">http://www.yt9tp.iz.rs</a><br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/<wbr>antivirus</a><br>
<br>
______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to amnon at <a href="mailto:amnon.zohar@gmail.com">amnon.zohar@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
</blockquote></div></div>