<div dir="ltr">We are locked on W10 1903, having blocked automatic updates in the Registry. Do you suspect that drivers will be updated nevertheless?<div><br></div><div>By Jove, you are correct Sir. I just checked. Although my OS was last updated in 2/20, drivers were updated recently this month, including Prolific Ports and FTDI Ports.</div><div><br></div><div>Do you have information as to how I can roll back the affected drivers? My Bezos cables may indeed have copied chips. I tried 5 different cables, including the ones forum denizens said always worked. Only 2 worked, and both are el cheapo cables.</div><div><br></div><div>To the other chap, the chronology was (works > fails > update CHIRP > still fails). So as you see the failure came under the previously working version of CHIRP.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 24, 2021 at 12:15 PM Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, May 24, 2021 at 11:25 AM Ceferino Lamb <<a href="mailto:ceferino.lamb@gmail.com" target="_blank">ceferino.lamb@gmail.com</a>> wrote:<br>
><br>
> For months, I've been successfully cloning GT-3TPs for our own use and UV5Rs for friends.<br>
> Suddenly, last week, I can't connect to any radios via CHIRP. I've installed the most recent CHIRP versions. Today it's chirp-daily-20210520-installer.exe<br>
<br>
This is not unusual with Windows and some programming cables with<br>
Prolific type USB-to-Serial chips. If you previously had to install<br>
and select the older Prolific v3.2.0.0 driver to get your programming<br>
cable(s) to work, Windows can and will, without notice, update to the<br>
latest driver version and sometimes even remove the working driver.<br>
When this happens your programming cable will not function until you<br>
install and select the older driver again.<br>
<br>
><br>
> I have two known good cloning cables that worked previously. Same results. I'm using BF-F8HP type as always. I've tried two different COM ports, CHIRP sees both.<br>
<br>
With Windows, there is no need to "try" different COM ports. You<br>
should use the Windows Device Manager application to determine exactly<br>
which COM port has been assigned to the programming cable.<br>
<br>
><br>
> The first time I tried this morning, Upload to Radio keyed the trx on the HT, solid carrier until I turned the HT off. That's a clue to me that something odd is up.<br>
<br>
Causing a radio to go into transmit is an indication that either or<br>
more of the following are true...<br>
1 the USB end of the programming cable is not plugged into the computer<br>
2 the USB end of the programming cable is plugged into the computer<br>
but the device driver has not been loaded yet<br>
3 the USB end of the programming cable is plugged into the computer<br>
but the device driver that is loaded is not compatible with the chip<br>
in the programming<br>
<br>
The #3 cause above is most often the result when the programming cable<br>
was manufactured with an unauthorized copy (counterfeit) of the<br>
Prolific PL2303HXA USB-to-serial chip. Driver versions after<br>
v3.3.2.105 are intentionally designed to be incompatible with these<br>
unauthorized chip copies. So if someone or something upgrades a<br>
Prolific driver to the latest Windows version, any programming cables<br>
with a counterfeit Prolific chip will stop functioning.<br>
<br>
Since the majority of my 20+ programming cables that I have these<br>
unauthorized Prolific chip copies and I have been using them with<br>
Windows since getting my USB based programming cable back in 2012, I<br>
have been using the Prolific v3.2.0.0 driver with Windows 7, 8.1 and<br>
10 (v2.0.2.1 for Windows XP) to program my radios. When Windows on its<br>
own updates the driver, my programming cable stop working until I<br>
install and select the older v3.2.0.0 driver again.<br>
<br>
None of my programming cables with USB-to-Serial chips from other chip<br>
vendors (FTDI, Silicon Labs, WCH, etc) have this issue. So switching<br>
to a programming cable with a chip from a different chip vendor is<br>
also a solution if you want to avoid having to go through this again<br>
in the future.<br>
<br>
><br>
> My next step is to install CHIRP on a different W10 laptop and try there. Anybody BTDT?<br>
<br>
No programming cable can work without a complete and working<br>
connection between the radio and computer. It is the CHIRP user that<br>
must insure that this connection is complete and working.<br>
<br>
><br>
> Reno in Texas<br>
> Quis custodiet ipsos custodes?<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Reno Lamb at <a href="mailto:ceferino.lamb@gmail.com" target="_blank">ceferino.lamb@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>//CRL<br><span lang="la"><span>Quis</span> <span>custodiet ipsos</span> <span>custodes</span><span>?</span></span></div></div></div>