That wasn't called for...
The OP had a cable, it worked fine, the. His OS upgraded, and the cable didn't work.
He asked why.
His question was valid, and the fix is straight-forward, as described by myself & others.
I'm not sure why you felt the need to get up on your soap box and preach your "it's cheaper to buy quality products the first time" sermon - many, many manufacturers got 'stung' with counterfeit chips that worked fine until the vendor dropped support for them, requiring unsuspecting buyers to learn about counterfeit chips and installing older drivers.
Now the vendor has convinced MS to bundle a driver with its OS that not only refuses to operate with counterfeit chips, it also announces in the device description that they do not support the particular chip - even genuine chips - under Win 10 or Win 11.
The cable is fine, using it is fine, and "serial-chip shaming" fellow hams is not cool.
Take care,
Ken, N2VIP
On Apr 5, 2023, at 14:27, Dave B via chirp_users chirp_users@intrepid.danplanet.com wrote:
Or... Buy a proper "Genuine" FTDI based cable. No more problems after that.
If your supplier/seller cannot guarantee a genuine FTDI based product, look elsewhere. (Or build the cable assembly yourself.)
If you use out of date hardware and drivers, & then have to stop Windows from updating, you are leaving yourself wide open to all sorts of other possible problems.
If your PC then gets hit with something nasty, then others on the same network might be liable to getting bad stuff too. Just how much domestic trouble can you survive?
You buy cheap, you often get poor quality. End of.
(Why do some Ham's pay top$£€ etc for some rig's, then penny pinch on accessories?)
Dave G8KBV
Who followed the instructions on the website, and now have the new version of Chirp happily running on a fresh install of LMDE* just fine. Many thanks to whoever put those instructions together. VERY much appreciated.
(* Linux Mint Debian Edition.)
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ken Hansen at ken@n2vip.org To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com