<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><ol style="margin:0px 0px 1em 30px;padding:0px;border:0px;vertical-align:baseline;list-style-position:initial;color:rgb(51,51,51);line-height:19.5px;background-color:rgb(255,254,249)"><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Open Device Manager</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Remove Old Com ports and USB devices: Proceed to step 2 of <a href="http://www.digi.com/support/kbase/kbaseresultdetl?id=3308" target="_blank">this tutorial</a>.</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">When that is done, still in Device manager, navigate to your problem USB cable (it should have a yellow exclamation mark on it)</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Remove it, and then reinstall the driver</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">If that driver will still not work then:</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Right click on it, and choose <em style="margin:0px;padding:0px;border:0px;vertical-align:baseline">update driver</em>.</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Click <em style="margin:0px;padding:0px;border:0px;vertical-align:baseline">Browse my Computer...</em></font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Click <em style="margin:0px;padding:0px;border:0px;vertical-align:baseline">Let me pick from a list...</em></font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">A list of all of the drivers should show. Choose the oldest Prolific driver on the list. I chose version 3.2.0 from 2007</font></li><li style="margin:0px 0px 7px;padding:0px;border:0px;vertical-align:baseline;line-height:1.3em;word-wrap:break-word"><font face="tahoma, sans-serif">Install it, and you're done!</font></li></ol><p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;clear:both;word-wrap:break-word;color:rgb(51,51,51);line-height:19.5px;background-color:rgb(255,254,249)"><font face="tahoma, sans-serif">If you are using PuTTy, note that when you connect, the COM port may not work as expected. What you should do, if you need to, is go into the Serial options in the main PuTTy window, and turn off flow control.</font></p><p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;clear:both;word-wrap:break-word;color:rgb(51,51,51);line-height:19.5px;background-color:rgb(255,254,249)"><font face="tahoma, sans-serif">Everything should work right now<img src="cid:360@goomoji.gmail" goomoji="360" style="margin: 0px 0.2ex; vertical-align: middle;">.</font></p></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><br></div><div><font face="comic sans ms, sans-serif">Regards,</font></div><font face="comic sans ms, sans-serif">John Kellas<br>403-762-2333</font></div></div></div>
<br><div class="gmail_quote">On Sat, Dec 6, 2014 at 12:55 PM, Jim Unroe <span dir="ltr"><<a href="mailto:rock.unroe@gmail.com" target="_blank">rock.unroe@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tom,<br>
<br>
I don't have Windows 8.1 here so I can test it out myself. Are you not<br>
able to choose the older compatible driver in the 8.1 Device Manager<br>
like is shows in step 11?<br>
<br>
Jim KC9HI<br>
<div class="HOEnZb"><div class="h5"><br>
On Sat, Dec 6, 2014 at 1:36 PM, Tom Maynard <<a href="mailto:tom.wz9u@gmail.com">tom.wz9u@gmail.com</a>> wrote:<br>
> On 06-Dec-14 09:15, Shon Edwards wrote:<br>
><br>
> This is a very good explanation and should work fine. I usually just use<br>
> the "official" cables myself and have no problem, so this is another option<br>
> in case things don't pan out.<br>
><br>
> I just went through this process for the first time myself, just last night.<br>
> Both my radio and my programming cable came from Banggood (China).<br>
><br>
> After a bit of struggling I got my systems communication smoothly. My<br>
> configuration:<br>
><br>
> Laptop: Windows 8.1<br>
> Radio Baofeng UV-82<br>
><br>
> I did try using the USB cable driver that came with Windows and it did not<br>
> work. I downloaded the drivers from the Miklor site and they also did not<br>
> work. As a last resort I used the drivers from the mini-disc supplied with<br>
> my cable. Again: No luck at all.<br>
><br>
> Then I realized that Windows was automatically updating the USB cable driver<br>
> the instant I plugged in the cable.<br>
><br>
> I discovered this by drilling down deep within Device Manager and looking at<br>
> the Date/Version of the installed driver. As soon as the cable was inserted<br>
> (with or without radio connected), Windows upgraded the driver instantly<br>
> (Fail).<br>
><br>
> The solution for me — and YMMV, of course — was to re-enter Device Manager<br>
> and to click on the “Roll Back Driver” button, after assuring the O/S that<br>
> this was in fact my intention the driver reverted to the one that I had<br>
> installed. Immediately thereafter everything was golden and CHIRP worked<br>
> perfectly.<br>
><br>
> I confess that it took me close to an hour to realize, diagnose, and correct<br>
> the problem but I got mine working.<br>
><br>
> Thereafter I went back to the CHIRP Wiki page with the hope of being able to<br>
> edit in my Windows 8 approach (since Win8 isn’t specifically mentioned<br>
> there). Alas, although it is a Wiki page, I found no way to edit it —<br>
> despite having registered/authenticated.<br>
><br>
> Instead, I post this here, hoping it will help someone. I can provide more<br>
> detailed info, even a step-by-step procedure, if someone with Write<br>
> authority on the Wiki would publish it there.<br>
><br>
> Tom Maynard WZ9U<br>
><br>
> P.S. I am actually using the driver that came with my cable on the<br>
> mini-disc. I'm sure the download from Miklor would also work, but once I<br>
> had a working solution I opted not to experiment further. (If it ain't<br>
> broke, right?)<br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> chirp_users mailing list<br>
> <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
><br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
</div></div></blockquote></div><br></div>