<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div markdown-here-wrapper-content-modified="true" style=""
class="markdown-here-wrapper" data-md-url="Thunderbird">
<p style="margin: 1.2em 0px ! important;">On 06-Dec-14 09:15, Shon
Edwards wrote:</p>
<p style="margin: 1.2em 0px ! important;"></p>
<div class="markdown-here-exclude">
<p></p>
<blockquote
cite="mid:CAC3=1e_B54DkVh16jHdPTuMZ4Myn1yye8=QXwnM-U9wa10UR6w@mail.gmail.com"
type="cite">
<div dir="ltr">This is a very good explanation and should work
fine. I usually just use the "official" cables myself and
have no problem, so this is another option in case things
don't pan out.</div>
</blockquote>
<p></p>
</div>
<p style="margin: 1.2em 0px ! important;"></p>
<p style="margin: 1.2em 0px ! important;">I just went through this
process for the first time myself, just last night. Both my
radio and my programming cable came from Banggood (China).</p>
<p style="margin: 1.2em 0px ! important;">After a bit of
struggling I got my systems communication smoothly. My
configuration:</p>
<ul style="margin: 1.2em 0px;padding-left: 2em;">
<li style="margin: 0.5em 0px;">Laptop: Windows 8.1 </li>
<li style="margin: 0.5em 0px;">Radio Baofeng UV-82</li>
</ul>
<p style="margin: 1.2em 0px ! important;">I did try using the USB
cable driver that came with Windows and it did not work. I
downloaded the drivers from the Miklor site and they also did
not work. As a last resort I used the drivers from the mini-disc
supplied with my cable. Again: No luck at all.</p>
<p style="margin: 1.2em 0px ! important;">Then I realized that
Windows was automatically updating the USB cable driver the
instant I plugged in the cable. </p>
<p style="margin: 1.2em 0px ! important;">I discovered this by
drilling down deep within Device Manager and looking at the
Date/Version of the installed driver. As soon as the cable was
inserted (with or without radio connected), Windows upgraded the
driver instantly (Fail).</p>
<p style="margin: 1.2em 0px ! important;">The solution for me —
and YMMV, of course — was to re-enter Device Manager and to
click on the “Roll Back Driver” button, after assuring the O/S
that this was in fact my intention the driver reverted to the
one that <em>I</em> had installed. Immediately thereafter
everything was golden and CHIRP worked perfectly.</p>
<p style="margin: 1.2em 0px ! important;">I confess that it took
me close to an hour to realize, diagnose, and correct the
problem but I got mine working.</p>
<p style="margin: 1.2em 0px ! important;">Thereafter I went back
to the CHIRP Wiki page with the hope of being able to edit in my
Windows 8 approach (since Win8 isn’t specifically mentioned
there). Alas, although it is a Wiki page, I found no way to edit
it — despite having registered/authenticated.</p>
<p style="margin: 1.2em 0px ! important;">Instead, I post this
here, hoping it will help someone. I can provide more detailed
info, even a step-by-step procedure, if someone with Write
authority on the Wiki would publish it there.</p>
<p style="margin: 1.2em 0px ! important;">Tom Maynard WZ9U<br>
</p>
<p style="margin: 1.2em 0px ! important;">P.S. I am actually using
the driver that came with my cable on the mini-disc. I'm sure
the download from Miklor would also work, but once I had a
working solution I opted not to experiment further. (If it
ain't broke, right?)</p>
<p style="margin: 1.2em 0px ! important;"></p>
</div>
</body>
</html>