<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:14pt;color:#000000;font-family:Verdana, Geneva, sans-serif;" dir="ltr">
<p>Regarding the LYT Q-18 Radio, check inside the Radio and on the Battery for where it was manufactured (probably China) and it should say which Company made it (it will not be LYT, that is just a Brand name), then research that Company on the Internet.</p>
<p><br>
</p>
<p>If you find the Company email their Customer Service all the details including Serial # and Photos of it. More than likely it was made under contract and re-labelled for a Customer.</p>
<p><br>
</p>
<p>This happened to me once and some Korean Company contracted 1,000s of HTs and re-labelled them. Not the original Model # at all. A little bit of Detective work for you. And they even found the original programming software for me too.</p>
<p><br>
</p>
<div id="Signature">
<div class="BodyFragment"><font size="2"><span style="font-size:10pt;">
<div class="PlainText"><span style="font-size: 14pt;">Kenneth Strom VA3KRS</span><br>
<br>
<br>
<br>
</div>
</span></font></div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> chirp_users-bounces@intrepid.danplanet.com <chirp_users-bounces@intrepid.danplanet.com> on behalf of chirp_users-request@intrepid.danplanet.com
<chirp_users-request@intrepid.danplanet.com><br>
<b>Sent:</b> November 21, 2016 3:00 PM<br>
<b>To:</b> chirp_users@intrepid.danplanet.com<br>
<b>Subject:</b> chirp_users Digest, Vol 95, Issue 14</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send chirp_users mailing list submissions to<br>
chirp_users@intrepid.danplanet.com<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" id="LPlnk377936" previewremoved="true">
http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
or, via email, send a message with subject or body 'help' to<br>
chirp_users-request@intrepid.danplanet.com<br>
<br>
You can reach the person managing the list at<br>
chirp_users-owner@intrepid.danplanet.com<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of chirp_users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Hello and Confusion (Jim Unroe)<br>
2. LYT Q-18 (dursr@sasktel.net)<br>
3. Re: Hello and Confusion (Jeff Butler)<br>
4. Re: Hello and Confusion (Jim Unroe)<br>
5. Re: Baofeng 888s cable issue (Garth Robinson)<br>
6. Re: Baofeng 888s cable issue (Jim Unroe)<br>
7. Re: Baofeng 888s cable issue (Kent Eichstaedt)<br>
8. Re: Baofeng 888s cable issue (Jim Unroe)<br>
9. Re: Baofeng 888s cable issue (Jardy Dawson)<br>
10. Re: Baofeng 888s cable issue (kc6iih@aol.com)<br>
11. Re: Baofeng 888s cable issue (Jim Unroe)<br>
12. Re: Baofeng 888s cable issue (David Ranch)<br>
13. Re: Baofeng 888s cable issue (Amnon Zohar)<br>
14. Re: Baofeng 888s cable issue (Amnon Zohar)<br>
15. Re: Baofeng 888s cable issue (jl_wilkerson@att.net)<br>
16. Unknown clones (dursr@sasktel.net)<br>
17. Re: Unknown clones (Jim Unroe)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 20 Nov 2016 15:32:08 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Hello and Confusion<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U5iwG8MZJ3Uw8xUaVZE0-itTnMq95-DzUPepLkhJch=ag@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hi Jeff,<br>
<br>
> Just landed at Chirp. Using it for programming the Baofend BF888s. We use<br>
> about 30 of them at a sporting event. I was intending to make some<br>
> programming changes but find that some of the radios will enter programming<br>
> mode and some will not. Wondering if you have heard of this before?<br>
<br>
Yes. I have heard of this before. This won't be easy to resolve unless<br>
the owners of one of these radios that won't enter programming mode<br>
would help to determine what is different about them. So far there<br>
hasn't been much assistance in that regard. The only other way would<br>
be to get one of these radios into the hands of a developer so the<br>
issue can be studied directly.<br>
<br>
Do all of the radios program OK with the same Baofeng software?<br>
If they require a different software, which software?<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 20 Nov 2016 14:40:01 -0600<br>
From: dursr@sasktel.net<br>
Subject: [chirp_users] LYT Q-18<br>
To: chirp_users@intrepid.danplanet.com<br>
Message-ID: <20161120144001.pzz7n0wfswsoswws@webmail.sasktel.net><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
It seems I have two obscure radios. ?Has anyone encountered the LYT Q-18? ?Perhaps it is a clone of a supported radio?<br>
?<br>
Ron<br>
?<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 20 Nov 2016 17:36:39 -0500<br>
From: "Jeff Butler" <jeffbutler@cogeco.ca><br>
Subject: Re: [chirp_users] Hello and Confusion<br>
To: "'Discussion of CHIRP'" <chirp_users@intrepid.danplanet.com><br>
Message-ID: <000301d2437e$8f2877e0$ad7967a0$@ca><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi Jim:<br>
I have all the radios with me. They were all bought together just weeks<br>
ago. I will try backdating my USB driver to the one recommended and then<br>
give it a try. I have only tried CHIRPS daily at this time but might try<br>
the BAOfeng software to see if it makes a difference.<br>
<br>
Cheers<br>
Jeff<br>
VE3JBX<br>
<br>
-----Original Message-----<br>
From: chirp_users-bounces@intrepid.danplanet.com<br>
[<a href="mailto:chirp_users-bounces@intrepid.danplanet.com">mailto:chirp_users-bounces@intrepid.danplanet.com</a>] On Behalf Of Jim Unroe<br>
Sent: November-20-16 3:32 PM<br>
To: Discussion of CHIRP<br>
Subject: Re: [chirp_users] Hello and Confusion<br>
<br>
Hi Jeff,<br>
<br>
> Just landed at Chirp. Using it for programming the Baofend BF888s. We use<br>
> about 30 of them at a sporting event. I was intending to make some<br>
> programming changes but find that some of the radios will enter <br>
> programming mode and some will not. Wondering if you have heard of this<br>
before?<br>
<br>
Yes. I have heard of this before. This won't be easy to resolve unless the<br>
owners of one of these radios that won't enter programming mode would help<br>
to determine what is different about them. So far there hasn't been much<br>
assistance in that regard. The only other way would be to get one of these<br>
radios into the hands of a developer so the issue can be studied directly.<br>
<br>
Do all of the radios program OK with the same Baofeng software?<br>
If they require a different software, which software?<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jeff at jeffbutler@cogeco.ca To unsubscribe, send<br>
an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 20 Nov 2016 17:53:06 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Hello and Confusion<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U6a9UOw2fK0sfB8Dk7Mtj5ALXrQOgArfDc+6ttYuqgxHA@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Sun, Nov 20, 2016 at 5:36 PM, Jeff Butler <jeffbutler@cogeco.ca> wrote:<br>
> Hi Jim:<br>
> I have all the radios with me. They were all bought together just weeks<br>
> ago. I will try backdating my USB driver to the one recommended and then<br>
> give it a try. I have only tried CHIRPS daily at this time but might try<br>
> the BAOfeng software to see if it makes a difference.<br>
><br>
> Cheers<br>
> Jeff<br>
> VE3JBX<br>
<br>
Great. It will help to know if the same radios fail with the Baofeng<br>
software or is the same software does them all.<br>
<br>
Jim<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 21 Nov 2016 16:37:51 +1300<br>
From: Garth Robinson <soundtek@vodafone.co.nz><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID: <cf21d45f-24cc-f038-0208-1a8589b7c198@vodafone.co.nz><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
Hi Jim,<br>
<br>
..... so, how can one guarantee ( without dismantling the cable ) that <br>
there is a genuine chip within the cable? I'm even suspect of the <br>
Baofeng cables.<br>
<br>
Garth. zl1tue ..... an still shakin'<br>
<br>
<br>
On 11/19/2016 11:14 AM, Jim Unroe wrote:<br>
> On Fri, Nov 18, 2016 at 4:15 PM, Garth Robinson <soundtek@vodafone.co.nz> wrote:<br>
>> Hi, s'cuse me butting in but.......<br>
>><br>
>> will these work under windoze 10 ?<br>
>><br>
>> I noticed that the webpage only mentioned xp, vista, 2000, win7 etc. in<br>
>> other words do you still have to use the backdated driver?<br>
>><br>
>><br>
>> Garth, zl1 tue<br>
>><br>
> When using a Prolific type chip based programming cable with Windows,<br>
> you might as well count on using the backdated driver because the<br>
> majority of these chips are counterfeit. The device driver auto<br>
> installed by Windows has been incompatible with counterfeit chips<br>
> since around 2008. The backdated driver will work no matter if the<br>
> chip is genuine or not.<br>
><br>
> V2.0.2.1: Windows XP<br>
> V3.2.0.0: Windows Vista, 2000, 7, 8.x and 10<br>
><br>
> Both drivers can be obtained from links on the miklor.com website.<br>
><br>
> Jim KC9HI<br>
> _______________________________________________<br>
> chirp_users mailing list<br>
> chirp_users@intrepid.danplanet.com<br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
> This message was sent to Garth at soundtek@vodafone.co.nz<br>
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
><br>
<br>
-- <br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/16e01151/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/16e01151/attachment-0001.html</a>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: IMAGE0003e.jpg<br>
Type: image/jpeg<br>
Size: 30952 bytes<br>
Desc: not available<br>
Url : <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/16e01151/attachment-0001.jpg">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/16e01151/attachment-0001.jpg</a>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Mon, 21 Nov 2016 09:19:28 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U5M+Ph+wYFAXgGovW+bVUbNNmyudSLJnHENu+_kTH3BwQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<br>
<soundtek@vodafone.co.nz> wrote:<br>
> Hi Jim,<br>
><br>
> ..... so, how can one guarantee ( without dismantling the cable ) that there<br>
> is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
><br>
> Garth. zl1tue ..... an still shakin'<br>
<br>
About 4 years ago I downloaded every version of Prolific driver for<br>
Windows I could find. I installed them one by one from the most recent<br>
to the oldest to find out exactly which driver was the absolute latest<br>
that would work with a counterfeit Prolific chip. The answer was<br>
v3.3.2.105. But although this driver works great with CHIRP, it is<br>
incompatible with most programming software written for Chinese<br>
radios.<br>
<br>
So my testing continued. It wasn't until I got to the Prolific<br>
v3.2.0.0 driver that it would work with all of my programming<br>
software. And it works with the latest Prolific chips as well.<br>
<br>
As you can see from the attached screen capture, I have 4 Prolific<br>
drivers installed in my Windows 7 64-bit computer. I can switch<br>
between these driver versions at will to determine if a Prolific type<br>
chip is genuine.<br>
<br>
So if you have a programming cable with a Prolfic type chip, there is<br>
no need to test if it is genuine or not. Genuine Prolific chips are<br>
rare. Out of some 20+ Prolific type chip based cables that I have<br>
here, I only have 2 that know are genuine.<br>
<br>
One came from a now out of business dealer. The description stated<br>
that it contained a genuine Prolfic chip. It cost $10 more than the<br>
non-genuine version that they also sold. The second came with (but was<br>
purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
a USA dealer.<br>
<br>
So if you run Windows XP or above, the non-destructive test to<br>
determine if the Prolific type chip in your programming cable is<br>
genuine is pretty simple. Plug it into the USB port and wait for the<br>
latest Prolific driver to install. Then try it out. then if it works<br>
(not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
likely) it has a counterfeit chip.<br>
<br>
But if you already have the programming cable, it is too late to worry<br>
about which type of Prolific chip is in it (genuine or counterfeit).<br>
Just download, install and select the older Prolific driver (it works<br>
for both).<br>
<br>
v2.0.2.1 Windows XP<br>
v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
<br>
If the idea is to avoid the hassle of dealing with counterfeit<br>
Prolific type chips, then note the following.<br>
<br>
A genuine Baofeng (the radio manufacturer based in China) programming<br>
cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
<br>
If the listing states that the programming cable only works with older<br>
versions of Windows or states that it does not work with the latest<br>
versions of Windows, it is a good bet that is will have a counterfeit<br>
Prolific chip. The same goes for listings where there is no mention of<br>
the chip the programming cable contains.<br>
<br>
So the best thing to do to avoid the driver hassle is to look for a<br>
cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
even the counterfeit chips currently work with the latest available<br>
device drivers.<br>
<br>
Although I mostly use Prolific type chips here, I do have some with<br>
genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
(the radio dealer based in the USA).<br>
<br>
Jim KC9HI<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: ProlificDrivers2.jpg<br>
Type: image/jpeg<br>
Size: 161541 bytes<br>
Desc: not available<br>
Url : <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/4ff1bc3c/attachment-0001.jpg">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/4ff1bc3c/attachment-0001.jpg</a>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Mon, 21 Nov 2016 09:07:15 -0600<br>
From: Kent Eichstaedt <kent.eichstaedt@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CAHjkhkWVBw898O2+kfJ4MaKOC_+DS8gft-_Bz65-xMzdeh5esg@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I would suggest buying BaoFeng stuff from BaoFeng Tech (on Amazon) . They<br>
are a US company and will back up their products in the US. The cable you<br>
need is at<br>
<a href="https://www.amazon.com/Authentic-Genuine-Programming-Cable-BaoFeng/dp/B00HUB0ONK/ref=pd_bxgy_107_img_2?_encoding=UTF8&psc=1&refRID=GQTCEKK5J4S4NCMP3EH3">https://www.amazon.com/Authentic-Genuine-Programming-Cable-BaoFeng/dp/B00HUB0ONK/ref=pd_bxgy_107_img_2?_encoding=UTF8&psc=1&refRID=GQTCEKK5J4S4NCMP3EH3</a><br>
There is also a "red cable" that works but I forgot what brand it is. The<br>
market was flooded with counterfeit chips so the manufacturers changed the<br>
chip and programming so that the old chips don't work. Expect to pay $20+.<br>
The $10 ones probably won't work without finding an old driver. I used the<br>
BF-Tech one with Windows 10 a few days ago with CHIRP and it worked fine,<br>
no problems. One tip: CHIRP prompts you to save your setup. When I went to<br>
the saved file (an .img file) and clicked on it, it said "the file is<br>
corrupted". After a couple of frustrating hours I tried opening the saved<br>
file by clicking on 'file', 'open' in the CHIRP program, and the saved<br>
image file opened OK.<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Sun, Nov 20, 2016 at 9:37 PM, Garth Robinson <soundtek@vodafone.co.nz><br>
wrote:<br>
<br>
> Hi Jim,<br>
><br>
> ..... so, how can one guarantee ( without dismantling the cable ) that<br>
> there is a genuine chip within the cable? I'm even suspect of the Baofeng<br>
> cables.<br>
><br>
> Garth. zl1tue ..... an still shakin'<br>
><br>
> On 11/19/2016 11:14 AM, Jim Unroe wrote:<br>
><br>
> On Fri, Nov 18, 2016 at 4:15 PM, Garth Robinson <soundtek@vodafone.co.nz> <soundtek@vodafone.co.nz> wrote:<br>
><br>
> Hi, s'cuse me butting in but.......<br>
><br>
> will these work under windoze 10 ?<br>
><br>
> I noticed that the webpage only mentioned xp, vista, 2000, win7 etc. in<br>
> other words do you still have to use the backdated driver?<br>
><br>
><br>
> Garth, zl1 tue<br>
><br>
><br>
> When using a Prolific type chip based programming cable with Windows,<br>
> you might as well count on using the backdated driver because the<br>
> majority of these chips are counterfeit. The device driver auto<br>
> installed by Windows has been incompatible with counterfeit chips<br>
> since around 2008. The backdated driver will work no matter if the<br>
> chip is genuine or not.<br>
><br>
> V2.0.2.1: Windows XP<br>
> V3.2.0.0: Windows Vista, 2000, 7, 8.x and 10<br>
><br>
> Both drivers can be obtained from links on the miklor.com website.<br>
><br>
> Jim KC9HI<br>
> _______________________________________________<br>
> chirp_users mailing listchirp_users@intrepid.danplanet.comhttp://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>
> This message was sent to Garth at soundtek@vodafone.co.nz<br>
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
><br>
><br>
> --<br>
><br>
><br>
> ------------------------------<br>
> [image: Avast logo] <<a href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a>><br>
><br>
> This email has been checked for viruses by Avast antivirus software.<br>
> <a href="http://www.avast.com">www.avast.com</a> <<a href="https://www.avast.com/antivirus">https://www.avast.com/antivirus</a>><br>
><br>
><br>
> _______________________________________________<br>
> chirp_users mailing list<br>
> chirp_users@intrepid.danplanet.com<br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
> This message was sent to Kent at kent.eichstaedt@gmail.com<br>
> To unsubscribe, send an email to chirp_users-unsubscribe@<br>
> intrepid.danplanet.com<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/9c6cc645/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/9c6cc645/attachment-0001.html</a>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: IMAGE0003e.jpg<br>
Type: image/jpeg<br>
Size: 30952 bytes<br>
Desc: not available<br>
Url : <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/9c6cc645/attachment-0001.jpg">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/9c6cc645/attachment-0001.jpg</a>
<br>
<br>
------------------------------<br>
<br>
Message: 8<br>
Date: Mon, 21 Nov 2016 10:23:15 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U64WF1929eNb=NNNQMsm3jKLhxq62b+2yTrb4Ve5gQUFg@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Kent,<br>
<br>
> problems. One tip: CHIRP prompts you to save your setup. When I went to the<br>
> saved file (an .img file) and clicked on it, it said "the file is<br>
> corrupted". After a couple of frustrating hours I tried opening the saved<br>
> file by clicking on 'file', 'open' in the CHIRP program, and the saved image<br>
> file opened OK.<br>
<br>
By default Windows associates the ".img" extension with CD burning<br>
software. So when you double-click a saved CHIRP Radio Images (*.img)<br>
file, Window tries to load it into that CD burning software (for which<br>
that software the file being loaded is truly corrupt). You either have<br>
to load it from within CHIRP (like you did) or change the association<br>
of the ".img" extension to CHIRP so you can double-click on it to load<br>
it into CHIRP by default (but then you won't be able to double-click<br>
on CD "image" files) to automatically load then into the CD burning<br>
software.<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
Message: 9<br>
Date: Mon, 21 Nov 2016 07:46:32 -0800<br>
From: Jardy Dawson <jardy72@yahoo.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID: <13068987-74F6-492A-AA50-9A4307466C3A@yahoo.com><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Jim,<br>
<br>
I am like you, having numerous cables that have the fake chips in them. Once I learned what to do with them, through you and the Miklor site, it only takes about 2 minutes to roll back the driver, if I have to. When Windows 8 first came out, I spent 3-4 months
fighting with cables not working. After learning what to do, I don't worry about it anymore. The nice thing is, is that I have cables for many different radios, but once you get the right driver installed, it works for all of them. I am not going to go
out and spend money I don't have to, just to save me 2 minutes of work. I also do not have the skill set, tools, or time, to make my own cables out of earphones and some other chip.<br>
<br>
I really do appreciate your testing the theories of why the cables are 'not compatible with Windows 10', etc. and coming up with the proper solution. It is just NOT THAT HARD TO DEAL WITH, when you know what to do.<br>
<br>
Thank you. <br>
<br>
Jardy Dawson<br>
WA7JRD Ham Radio<br>
<br>
Message relayed from secret Hillary Clinton server, located in the basement of her house. OOPS, you aren't supposed to know that!<br>
<br>
On Nov 21, 2016, at 06:19, Jim Unroe <rock.unroe@gmail.com> wrote:<br>
<br>
On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<br>
<soundtek@vodafone.co.nz> wrote:<br>
> Hi Jim,<br>
> <br>
> ..... so, how can one guarantee ( without dismantling the cable ) that there<br>
> is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
> <br>
> Garth. zl1tue ..... an still shakin'<br>
<br>
About 4 years ago I downloaded every version of Prolific driver for<br>
Windows I could find. I installed them one by one from the most recent<br>
to the oldest to find out exactly which driver was the absolute latest<br>
that would work with a counterfeit Prolific chip. The answer was<br>
v3.3.2.105. But although this driver works great with CHIRP, it is<br>
incompatible with most programming software written for Chinese<br>
radios.<br>
<br>
So my testing continued. It wasn't until I got to the Prolific<br>
v3.2.0.0 driver that it would work with all of my programming<br>
software. And it works with the latest Prolific chips as well.<br>
<br>
As you can see from the attached screen capture, I have 4 Prolific<br>
drivers installed in my Windows 7 64-bit computer. I can switch<br>
between these driver versions at will to determine if a Prolific type<br>
chip is genuine.<br>
<br>
So if you have a programming cable with a Prolfic type chip, there is<br>
no need to test if it is genuine or not. Genuine Prolific chips are<br>
rare. Out of some 20+ Prolific type chip based cables that I have<br>
here, I only have 2 that know are genuine.<br>
<br>
One came from a now out of business dealer. The description stated<br>
that it contained a genuine Prolfic chip. It cost $10 more than the<br>
non-genuine version that they also sold. The second came with (but was<br>
purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
a USA dealer.<br>
<br>
So if you run Windows XP or above, the non-destructive test to<br>
determine if the Prolific type chip in your programming cable is<br>
genuine is pretty simple. Plug it into the USB port and wait for the<br>
latest Prolific driver to install. Then try it out. then if it works<br>
(not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
likely) it has a counterfeit chip.<br>
<br>
But if you already have the programming cable, it is too late to worry<br>
about which type of Prolific chip is in it (genuine or counterfeit).<br>
Just download, install and select the older Prolific driver (it works<br>
for both).<br>
<br>
v2.0.2.1 Windows XP<br>
v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
<br>
If the idea is to avoid the hassle of dealing with counterfeit<br>
Prolific type chips, then note the following.<br>
<br>
A genuine Baofeng (the radio manufacturer based in China) programming<br>
cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
<br>
If the listing states that the programming cable only works with older<br>
versions of Windows or states that it does not work with the latest<br>
versions of Windows, it is a good bet that is will have a counterfeit<br>
Prolific chip. The same goes for listings where there is no mention of<br>
the chip the programming cable contains.<br>
<br>
So the best thing to do to avoid the driver hassle is to look for a<br>
cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
even the counterfeit chips currently work with the latest available<br>
device drivers.<br>
<br>
Although I mostly use Prolific type chips here, I do have some with<br>
genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
(the radio dealer based in the USA).<br>
<br>
Jim KC9HI<br>
<ProlificDrivers2.jpg><br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jardy at jardy72@yahoo.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/4022b34b/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/4022b34b/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 10<br>
Date: Mon, 21 Nov 2016 10:55:47 -0500<br>
From: kc6iih@aol.com<br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: chirp_users@intrepid.danplanet.com<br>
Message-ID: <1588799b4b8-78f-ecf0@webprd-m55.mail.aol.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The only cables I buy are from RTSYSTEMS.<br>
They work every time.<br>
Yes they cost more but you go cheap you buy problems .<br>
<br>
Jock Soutar KC6IIH<br>
Sent via Samsung Galaxy S7 <br>
on AT&T 4G LTE Smartphone<br>
<br>
On Monday, November 21, 2016 Jardy Dawson via chirp_users <chirp_users@intrepid.danplanet.com> wrote:<br>
<br>
Jim,<br>
<br>
<br>
I am like you, having numerous cables that have the fake chips in them. ?Once I learned what to do with them, through you and the Miklor site, it only takes about 2 minutes to roll back the driver, if I have to. ?When Windows 8 first came out, I spent 3-4 months
fighting with cables not working. ?After learning what to do, I don't worry about it anymore. ?The nice thing is, is that I have cables for many different radios, but once you get the right driver installed, it works for all of them. ?I am not going to go
out and spend money I don't have to, just to save me 2 minutes of work. ?I also do not have the skill set, tools, or time, to make my own cables out of earphones and some other chip.<br>
<br>
<br>
I really do appreciate your testing the theories of why the cables are 'not compatible with Windows 10', etc. and coming up with the proper solution. ?It is just NOT THAT HARD TO DEAL WITH, when you know what to do.<br>
<br>
<br>
Thank you.?<br>
<br>
<br>
Jardy Dawson<br>
<br>
WA7JRD Ham Radio<br>
<br>
<br>
Message relayed from secret Hillary Clinton server, located in the basement of her house. ?OOPS, you aren't supposed to know that!<br>
<br>
<br>
On Nov 21, 2016, at 06:19, Jim Unroe <rock.unroe@gmail.com> wrote:<br>
<br>
On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<br>
<soundtek@vodafone.co.nz> wrote:<br>
<br>
Hi Jim,<br>
<br>
<br>
..... so, how can one guarantee ( without dismantling the cable ) that there<br>
<br>
is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
<br>
<br>
Garth. zl1tue ?..... an still shakin'<br>
<br>
<br>
About 4 years ago I downloaded every version of Prolific driver for<br>
Windows I could find. I installed them one by one from the most recent<br>
to the oldest to find out exactly which driver was the absolute latest<br>
that would work with a counterfeit Prolific chip. The answer was<br>
v3.3.2.105. But although this driver works great with CHIRP, it is<br>
incompatible with most programming software written for Chinese<br>
radios.<br>
<br>
So my testing continued. It wasn't until I got to the Prolific<br>
v3.2.0.0 driver that it would work with all of my programming<br>
software. And it works with the latest Prolific chips as well.<br>
<br>
As you can see from the attached screen capture, I have 4 Prolific<br>
drivers installed in my Windows 7 64-bit computer. I can switch<br>
between these driver versions at will to determine if a Prolific type<br>
chip is genuine.<br>
<br>
So if you have a programming cable with a Prolfic type chip, there is<br>
no need to test if it is genuine or not. Genuine Prolific chips are<br>
rare. Out of some 20+ Prolific type chip based cables that I have<br>
here, I only have 2 that know are genuine.<br>
<br>
One came from a now out of business dealer. The description stated<br>
that it contained a genuine Prolfic chip. It cost $10 more than the<br>
non-genuine version that they also sold. The second came with (but was<br>
purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
a USA dealer.<br>
<br>
So if you run Windows XP or above, the non-destructive test to<br>
determine if the Prolific type chip in your programming cable is<br>
genuine is pretty simple. Plug it into the USB port and wait for the<br>
latest Prolific driver to install. Then try it out. then if it works<br>
(not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
likely) it has a counterfeit chip.<br>
<br>
But if you already have the programming cable, it is too late to worry<br>
about which type of Prolific chip is in it (genuine or counterfeit).<br>
Just download, install and select the older Prolific driver (it works<br>
for both).<br>
<br>
v2.0.2.1 Windows XP<br>
v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
<br>
If the idea is to avoid the hassle of dealing with counterfeit<br>
Prolific type chips, then note the following.<br>
<br>
A genuine Baofeng (the radio manufacturer based in China) programming<br>
cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
<br>
If the listing states that the programming cable only works with older<br>
versions of Windows or states that it does not work with the latest<br>
versions of Windows, it is a good bet that is will have a counterfeit<br>
Prolific chip. The same goes for listings where there is no mention of<br>
the chip the programming cable contains.<br>
<br>
So the best thing to do to avoid the driver hassle is to look for a<br>
cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
even the counterfeit chips currently work with the latest available<br>
device drivers.<br>
<br>
Although I mostly use Prolific type chips here, I do have some with<br>
genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
(the radio dealer based in the USA).<br>
<br>
Jim KC9HI<br>
<br>
<ProlificDrivers2.jpg><br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jardy at jardy72@yahoo.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jock at kc6iih@aol.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/e279c631/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/e279c631/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 11<br>
Date: Mon, 21 Nov 2016 10:58:19 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Jardy Dawson <jardy72@yahoo.com>, Discussion of CHIRP<br>
<chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U7hL_VPyBsWhNkuueMgJDHUi_3bYEGckCwO1OHkqZJAtg@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Since I deal with many radios, I actually prefer the Prolific type<br>
chip. It has the advantage that once a USB port is setup with the<br>
older, compatible with all Prolific chips, driver, I can plug in any<br>
one of my Prolific chip bases programming cables and it will always<br>
have the same COM port assigned to it.<br>
<br>
By default, each FTDI based programming cable gets it's own separate<br>
COM port (something else I would have to keep track of). I know there<br>
is a Windows registry hack that can be done so that FTDI cables will<br>
behave the same way, but I haven't bothered since all of my radios<br>
have at least 1 Prolific chip based programming cable and only a very<br>
few radios have FTDI based programming cables.<br>
<br>
Jim<br>
<br>
<br>
------------------------------<br>
<br>
Message: 12<br>
Date: Mon, 21 Nov 2016 08:20:17 -0800<br>
From: David Ranch <chirp@trinnet.net><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID: <fc8a9918-c658-646a-d001-cf8c873bf3d5@trinnet.net><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
<br>
Great email Jim. Any chances you can turn this into a FAQ answer on the <br>
Chirp wiki?<br>
<br>
--David<br>
KI6ZHD<br>
<br>
<br>
On 11/21/2016 06:19 AM, Jim Unroe wrote:<br>
> On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<br>
> <soundtek@vodafone.co.nz> wrote:<br>
>> Hi Jim,<br>
>><br>
>> ..... so, how can one guarantee ( without dismantling the cable ) that there<br>
>> is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
>><br>
>> Garth. zl1tue ..... an still shakin'<br>
> About 4 years ago I downloaded every version of Prolific driver for<br>
> Windows I could find. I installed them one by one from the most recent<br>
> to the oldest to find out exactly which driver was the absolute latest<br>
> that would work with a counterfeit Prolific chip. The answer was<br>
> v3.3.2.105. But although this driver works great with CHIRP, it is<br>
> incompatible with most programming software written for Chinese<br>
> radios.<br>
><br>
> So my testing continued. It wasn't until I got to the Prolific<br>
> v3.2.0.0 driver that it would work with all of my programming<br>
> software. And it works with the latest Prolific chips as well.<br>
><br>
> As you can see from the attached screen capture, I have 4 Prolific<br>
> drivers installed in my Windows 7 64-bit computer. I can switch<br>
> between these driver versions at will to determine if a Prolific type<br>
> chip is genuine.<br>
><br>
> So if you have a programming cable with a Prolfic type chip, there is<br>
> no need to test if it is genuine or not. Genuine Prolific chips are<br>
> rare. Out of some 20+ Prolific type chip based cables that I have<br>
> here, I only have 2 that know are genuine.<br>
><br>
> One came from a now out of business dealer. The description stated<br>
> that it contained a genuine Prolfic chip. It cost $10 more than the<br>
> non-genuine version that they also sold. The second came with (but was<br>
> purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
> a USA dealer.<br>
><br>
> So if you run Windows XP or above, the non-destructive test to<br>
> determine if the Prolific type chip in your programming cable isHey<br>
> genuine is pretty simple. Plug it into the USB port and wait for the<br>
> latest Prolific driver to install. Then try it out. then if it works<br>
> (not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
> likely) it has a counterfeit chip.<br>
><br>
> But if you already have the programming cable, it is too late to worry<br>
> about which type of Prolific chip is in it (genuine or counterfeit).<br>
> Just download, install and select the older Prolific driver (it works<br>
> for both).<br>
><br>
> v2.0.2.1 Windows XP<br>
> v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
><br>
> If the idea is to avoid the hassle of dealing with counterfeit<br>
> Prolific type chips, then note the following.<br>
><br>
> A genuine Baofeng (the radio manufacturer based in China) programming<br>
> cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
><br>
> If the listing states that the programming cable only works with older<br>
> versions of Windows or states that it does not work with the latest<br>
> versions of Windows, it is a good bet that is will have a counterfeit<br>
> Prolific chip. The same goes for listings where there is no mention of<br>
> the chip the programming cable contains.<br>
><br>
> So the best thing to do to avoid the driver hassle is to look for a<br>
> cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
> even the counterfeit chips currently work with the latest available<br>
> device drivers.<br>
><br>
> Although I mostly use Prolific type chips here, I do have some with<br>
> genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
> (the radio dealer based in the USA).<br>
><br>
> Jim KC9HI<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/79221dc3/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/79221dc3/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 13<br>
Date: Mon, 21 Nov 2016 18:25:38 +0200<br>
From: Amnon Zohar <amnon.zohar@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CAN5HzcQ=-WRVKeEinfQpkhpbVHfL_2iK9CUEKRAPz0qD-MGPBg@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I bought cheap no problem. Price gap worth the risk (to my mind)<br>
<br>
?????? 21 ????' 2016 6:22 PM,? "David Ranch" <chirp@trinnet.net> ???:<br>
<br>
><br>
> Great email Jim. Any chances you can turn this into a FAQ answer on the<br>
> Chirp wiki?<br>
><br>
> --David<br>
> KI6ZHD<br>
><br>
><br>
> On 11/21/2016 06:19 AM, Jim Unroe wrote:<br>
><br>
> On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<soundtek@vodafone.co.nz> <soundtek@vodafone.co.nz> wrote:<br>
><br>
> Hi Jim,<br>
><br>
> ..... so, how can one guarantee ( without dismantling the cable ) that there<br>
> is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
><br>
> Garth. zl1tue ..... an still shakin'<br>
><br>
><br>
> About 4 years ago I downloaded every version of Prolific driver for<br>
> Windows I could find. I installed them one by one from the most recent<br>
> to the oldest to find out exactly which driver was the absolute latest<br>
> that would work with a counterfeit Prolific chip. The answer was<br>
> v3.3.2.105. But although this driver works great with CHIRP, it is<br>
> incompatible with most programming software written for Chinese<br>
> radios.<br>
><br>
> So my testing continued. It wasn't until I got to the Prolific<br>
> v3.2.0.0 driver that it would work with all of my programming<br>
> software. And it works with the latest Prolific chips as well.<br>
><br>
> As you can see from the attached screen capture, I have 4 Prolific<br>
> drivers installed in my Windows 7 64-bit computer. I can switch<br>
> between these driver versions at will to determine if a Prolific type<br>
> chip is genuine.<br>
><br>
> So if you have a programming cable with a Prolfic type chip, there is<br>
> no need to test if it is genuine or not. Genuine Prolific chips are<br>
> rare. Out of some 20+ Prolific type chip based cables that I have<br>
> here, I only have 2 that know are genuine.<br>
><br>
> One came from a now out of business dealer. The description stated<br>
> that it contained a genuine Prolfic chip. It cost $10 more than the<br>
> non-genuine version that they also sold. The second came with (but was<br>
> purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
> a USA dealer.<br>
><br>
> So if you run Windows XP or above, the non-destructive test to<br>
> determine if the Prolific type chip in your programming cable isHey<br>
> genuine is pretty simple. Plug it into the USB port and wait for the<br>
> latest Prolific driver to install. Then try it out. then if it works<br>
> (not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
> likely) it has a counterfeit chip.<br>
><br>
> But if you already have the programming cable, it is too late to worry<br>
> about which type of Prolific chip is in it (genuine or counterfeit).<br>
> Just download, install and select the older Prolific driver (it works<br>
> for both).<br>
><br>
> v2.0.2.1 Windows XP<br>
> v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
><br>
> If the idea is to avoid the hassle of dealing with counterfeit<br>
> Prolific type chips, then note the following.<br>
><br>
> A genuine Baofeng (the radio manufacturer based in China) programming<br>
> cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
><br>
> If the listing states that the programming cable only works with older<br>
> versions of Windows or states that it does not work with the latest<br>
> versions of Windows, it is a good bet that is will have a counterfeit<br>
> Prolific chip. The same goes for listings where there is no mention of<br>
> the chip the programming cable contains.<br>
><br>
> So the best thing to do to avoid the driver hassle is to look for a<br>
> cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
> even the counterfeit chips currently work with the latest available<br>
> device drivers.<br>
><br>
> Although I mostly use Prolific type chips here, I do have some with<br>
> genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
> (the radio dealer based in the USA).<br>
><br>
> Jim KC9HI<br>
><br>
><br>
><br>
> _______________________________________________<br>
> chirp_users mailing list<br>
> chirp_users@intrepid.danplanet.com<br>
> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
> This message was sent to amnon at amnon.zohar@gmail.com<br>
> To unsubscribe, send an email to chirp_users-unsubscribe@<br>
> intrepid.danplanet.com<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/7da7f586/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/7da7f586/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 14<br>
Date: Mon, 21 Nov 2016 18:26:31 +0200<br>
From: Amnon Zohar <amnon.zohar@gmail.com><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CAN5HzcS5tMFy9mOo1QrHRNmM5fLcOLY_sYRgraa111ZyuMhSBQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
High price of the "good" cables are actualy a rip off!<br>
<br>
?????? 21 ????' 2016 6:25 PM,? "Amnon Zohar" <amnon.zohar@gmail.com> ???:<br>
<br>
> I bought cheap no problem. Price gap worth the risk (to my mind)<br>
><br>
> ?????? 21 ????' 2016 6:22 PM,? "David Ranch" <chirp@trinnet.net> ???:<br>
><br>
>><br>
>> Great email Jim. Any chances you can turn this into a FAQ answer on the<br>
>> Chirp wiki?<br>
>><br>
>> --David<br>
>> KI6ZHD<br>
>><br>
>><br>
>> On 11/21/2016 06:19 AM, Jim Unroe wrote:<br>
>><br>
>> On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<soundtek@vodafone.co.nz> <soundtek@vodafone.co.nz> wrote:<br>
>><br>
>> Hi Jim,<br>
>><br>
>> ..... so, how can one guarantee ( without dismantling the cable ) that there<br>
>> is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
>><br>
>> Garth. zl1tue ..... an still shakin'<br>
>><br>
>><br>
>> About 4 years ago I downloaded every version of Prolific driver for<br>
>> Windows I could find. I installed them one by one from the most recent<br>
>> to the oldest to find out exactly which driver was the absolute latest<br>
>> that would work with a counterfeit Prolific chip. The answer was<br>
>> v3.3.2.105. But although this driver works great with CHIRP, it is<br>
>> incompatible with most programming software written for Chinese<br>
>> radios.<br>
>><br>
>> So my testing continued. It wasn't until I got to the Prolific<br>
>> v3.2.0.0 driver that it would work with all of my programming<br>
>> software. And it works with the latest Prolific chips as well.<br>
>><br>
>> As you can see from the attached screen capture, I have 4 Prolific<br>
>> drivers installed in my Windows 7 64-bit computer. I can switch<br>
>> between these driver versions at will to determine if a Prolific type<br>
>> chip is genuine.<br>
>><br>
>> So if you have a programming cable with a Prolfic type chip, there is<br>
>> no need to test if it is genuine or not. Genuine Prolific chips are<br>
>> rare. Out of some 20+ Prolific type chip based cables that I have<br>
>> here, I only have 2 that know are genuine.<br>
>><br>
>> One came from a now out of business dealer. The description stated<br>
>> that it contained a genuine Prolfic chip. It cost $10 more than the<br>
>> non-genuine version that they also sold. The second came with (but was<br>
>> purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
>> a USA dealer.<br>
>><br>
>> So if you run Windows XP or above, the non-destructive test to<br>
>> determine if the Prolific type chip in your programming cable isHey<br>
>> genuine is pretty simple. Plug it into the USB port and wait for the<br>
>> latest Prolific driver to install. Then try it out. then if it works<br>
>> (not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
>> likely) it has a counterfeit chip.<br>
>><br>
>> But if you already have the programming cable, it is too late to worry<br>
>> about which type of Prolific chip is in it (genuine or counterfeit).<br>
>> Just download, install and select the older Prolific driver (it works<br>
>> for both).<br>
>><br>
>> v2.0.2.1 Windows XP<br>
>> v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
>><br>
>> If the idea is to avoid the hassle of dealing with counterfeit<br>
>> Prolific type chips, then note the following.<br>
>><br>
>> A genuine Baofeng (the radio manufacturer based in China) programming<br>
>> cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
>><br>
>> If the listing states that the programming cable only works with older<br>
>> versions of Windows or states that it does not work with the latest<br>
>> versions of Windows, it is a good bet that is will have a counterfeit<br>
>> Prolific chip. The same goes for listings where there is no mention of<br>
>> the chip the programming cable contains.<br>
>><br>
>> So the best thing to do to avoid the driver hassle is to look for a<br>
>> cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
>> even the counterfeit chips currently work with the latest available<br>
>> device drivers.<br>
>><br>
>> Although I mostly use Prolific type chips here, I do have some with<br>
>> genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
>> (the radio dealer based in the USA).<br>
>><br>
>> Jim KC9HI<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> chirp_users mailing list<br>
>> chirp_users@intrepid.danplanet.com<br>
>> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
>> This message was sent to amnon at amnon.zohar@gmail.com<br>
>> To unsubscribe, send an email to chirp_users-unsubscribe@intrep<br>
>> id.danplanet.com<br>
>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/830a7101/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/830a7101/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 15<br>
Date: Mon, 21 Nov 2016 17:56:30 GMT<br>
From: jl_wilkerson@att.net <jl_wilkerson@att.net><br>
Subject: Re: [chirp_users] Baofeng 888s cable issue<br>
To: chirp_users@intrepid.danplanet.com<br>
Message-ID: <000f4242.028c09b2647172d3@att.net><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Cp2102. ?Retrofit cheap cable. ?Beat FTDI.<br>
<br>
<br>
<br>
------ Original message------From: Jock via chirp_users Date: Mon, Nov 21, 2016 10:56 AMTo: chirp_users@intrepid.danplanet.com;Subject:Re: [chirp_users] Baofeng 888s cable issue<br>
The only cables I buy are from RTSYSTEMS.<br>
They work every time.<br>
Yes they cost more but you go cheap you buy problems .Jock Soutar KC6IIH<br>
Sent via Samsung Galaxy S7 <br>
on AT&T 4G LTE Smartphone<br>
<br>
On Monday, November 21, 2016 Jardy Dawson via chirp_users <chirp_users@intrepid.danplanet.com> wrote:<br>
<br>
Jim,<br>
I am like you, having numerous cables that have the fake chips in them. ?Once I learned what to do with them, through you and the Miklor site, it only takes about 2 minutes to roll back the driver, if I have to. ?When Windows 8 first came out, I spent 3-4 months
fighting with cables not working. ?After learning what to do, I don't worry about it anymore. ?The nice thing is, is that I have cables for many different radios, but once you get the right driver installed, it works for all of them. ?I am not going to go
out and spend money I don't have to, just to save me 2 minutes of work. ?I also do not have the skill set, tools, or time, to make my own cables out of earphones and some other chip.<br>
I really do appreciate your testing the theories of why the cables are 'not compatible with Windows 10', etc. and coming up with the proper solution. ?It is just NOT THAT HARD TO DEAL WITH, when you know what to do.<br>
Thank you.?<br>
Jardy DawsonWA7JRD Ham Radio<br>
Message relayed from secret Hillary Clinton server, located in the basement of her house. ?OOPS, you aren't supposed to know that!<br>
On Nov 21, 2016, at 06:19, Jim Unroe <rock.unroe@gmail.com> wrote:<br>
<br>
On Sun, Nov 20, 2016 at 10:37 PM, Garth Robinson<br>
<soundtek@vodafone.co.nz> wrote:<br>
Hi Jim,<br>
<br>
..... so, how can one guarantee ( without dismantling the cable ) that there<br>
is a genuine chip within the cable? I'm even suspect of the Baofeng cables.<br>
<br>
Garth. zl1tue ?..... an still shakin'<br>
<br>
About 4 years ago I downloaded every version of Prolific driver for<br>
Windows I could find. I installed them one by one from the most recent<br>
to the oldest to find out exactly which driver was the absolute latest<br>
that would work with a counterfeit Prolific chip. The answer was<br>
v3.3.2.105. But although this driver works great with CHIRP, it is<br>
incompatible with most programming software written for Chinese<br>
radios.<br>
<br>
So my testing continued. It wasn't until I got to the Prolific<br>
v3.2.0.0 driver that it would work with all of my programming<br>
software. And it works with the latest Prolific chips as well.<br>
<br>
As you can see from the attached screen capture, I have 4 Prolific<br>
drivers installed in my Windows 7 64-bit computer. I can switch<br>
between these driver versions at will to determine if a Prolific type<br>
chip is genuine.<br>
<br>
So if you have a programming cable with a Prolfic type chip, there is<br>
no need to test if it is genuine or not. Genuine Prolific chips are<br>
rare. Out of some 20+ Prolific type chip based cables that I have<br>
here, I only have 2 that know are genuine.<br>
<br>
One came from a now out of business dealer. The description stated<br>
that it contained a genuine Prolfic chip. It cost $10 more than the<br>
non-genuine version that they also sold. The second came with (but was<br>
purchased separately) a Wouxun KG-UV6D V2 radio that I purchased from<br>
a USA dealer.<br>
<br>
So if you run Windows XP or above, the non-destructive test to<br>
determine if the Prolific type chip in your programming cable is<br>
genuine is pretty simple. Plug it into the USB port and wait for the<br>
latest Prolific driver to install. Then try it out. then if it works<br>
(not likely) it has a genuine Prolific chip. If it doesn't work (very<br>
likely) it has a counterfeit chip.<br>
<br>
But if you already have the programming cable, it is too late to worry<br>
about which type of Prolific chip is in it (genuine or counterfeit).<br>
Just download, install and select the older Prolific driver (it works<br>
for both).<br>
<br>
v2.0.2.1 Windows XP<br>
v3.2.0.0 Windows Vista, 7, 8, 8.1 and 10<br>
<br>
If the idea is to avoid the hassle of dealing with counterfeit<br>
Prolific type chips, then note the following.<br>
<br>
A genuine Baofeng (the radio manufacturer based in China) programming<br>
cable is virtually guaranteed to have a counterfeit Prolific chip.<br>
<br>
If the listing states that the programming cable only works with older<br>
versions of Windows or states that it does not work with the latest<br>
versions of Windows, it is a good bet that is will have a counterfeit<br>
Prolific chip. The same goes for listings where there is no mention of<br>
the chip the programming cable contains.<br>
<br>
So the best thing to do to avoid the driver hassle is to look for a<br>
cable with an FTDI type chip. Even FTDI chips can be counterfeit, but<br>
even the counterfeit chips currently work with the latest available<br>
device drivers.<br>
<br>
Although I mostly use Prolific type chips here, I do have some with<br>
genuine FTDI chips. My source for the last few has been Baofeng Tech<br>
(the radio dealer based in the USA).<br>
<br>
Jim KC9HI<br>
<ProlificDrivers2.jpg>_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jardy at jardy72@yahoo.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jock at kc6iih@aol.com<br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/a1cd7f1b/attachment-0001.html">
http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20161121/a1cd7f1b/attachment-0001.html</a>
<br>
<br>
------------------------------<br>
<br>
Message: 16<br>
Date: Mon, 21 Nov 2016 12:00:44 -0600<br>
From: dursr@sasktel.net<br>
Subject: [chirp_users] Unknown clones<br>
To: chirp_users@intrepid.danplanet.com<br>
Message-ID: <20161121120044.fe3zn26y9s08sg4w@webmail.sasktel.net><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Assuming I have an appropriate data cable how do I get Chirp to talk to an unknown clone radio?<br>
?<br>
Ron<br>
<br>
<br>
------------------------------<br>
<br>
Message: 17<br>
Date: Mon, 21 Nov 2016 14:42:40 -0500<br>
From: Jim Unroe <rock.unroe@gmail.com><br>
Subject: Re: [chirp_users] Unknown clones<br>
To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>
Message-ID:<br>
<CADnO8U7Pa3+t3Uid543YjKE==CYg35CMPB3FasVb=+uYWVrsVw@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Mon, Nov 21, 2016 at 1:00 PM, <dursr@sasktel.net> wrote:<br>
> Assuming I have an appropriate data cable how do I get Chirp to talk to an unknown clone radio?<br>
><br>
> Ron<br>
<br>
What do you mean by "unknown clone"? Do you mean a radio this is a<br>
variant of a similar CHIRP supported radio? Or do you mean a radio<br>
that is not supported by CHIRP at all?<br>
<br>
Jim KC9HI<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
chirp_users@intrepid.danplanet.com<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br>
<br>
End of chirp_users Digest, Vol 95, Issue 14<br>
*******************************************<br>
</div>
</span></font></div>
</div>
</body>
</html>