<div dir="rtl">updating cab be avoided</div><div class="gmail_extra"><br><div class="gmail_quote"><div dir="ltr">2017-11-29 11:04 GMT+02:00 Dave B <span dir="ltr"><<a href="mailto:g8kbv@uku.co.uk" target="_blank">g8kbv@uku.co.uk</a>></span>:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>It probably uses a fake Prolific chipset, all too common sadly.<br>
</p>
<p>Windows will not use those now, unless you roll back the driver,
but then Windows will "update" it to the latest again at the next
opportunity. If you turn Windows updates off, then you are
potentially vulnerable for other troubles as they are found later.<br>
</p>
<p>They still work OK on most Linux's though, as does Chirp just
fine.<br>
</p>
<p>Solution, use a FTDI based cable (if you can find a seller to
guarantee that they are genuine too) or build your own cable with
a known genuine USB<>Serial chip. The "Genuine" Prolific
chips are OK in Windows.<br>
</p>
<p>Silicon Lab's chips are OK too, but you'll have to install
drivers yourself for them, except on Linux, where they "just work"
without issue on most distro's.<br>
</p>
<p>Note: The "Fake" chips, are actually micro-controllers
programmed to emulate Prolific or FTDI chips. The emulations are
quite good, but can be detected by the "official" drivers. The
current official Prolific drivers will not use the Fakes.
Similarly, FTDI drivers will not use the fakes either. Earlier
FTDI drivers would "brick" them by resetting the VID/PID values to
zero. Caused a lot of bad press that did. (But they can be
un-bricked!)<br>
</p>
<p>The fake FDTI chips can be identified as being unable to
re-assign the auxiliary I/O pin functions. Well, the software is
happy, but the change doesn’t actually happen. That's how I found
one, I needed to invert the TXD line, but no change happened.<br>
</p>
<p>I have also personally come across a chip that was marked up as
FTDI, but identified itself to the PC as Prolific! I suspect
there are undocumented ways to "configure" the emulation.<br>
</p>
<p>Take care.<br>
</p>
<p>73.</p>
<p>Dave G0WBX.</p>
<p><br>
</p>
<br>
<div class="m_-3435214941004281498moz-cite-prefix">On 28/11/17 20:00,
<a class="m_-3435214941004281498moz-txt-link-abbreviated" href="mailto:chirp_users-request@intrepid.danplanet.com" target="_blank">chirp_users-request@intrepid.<wbr>danplanet.com</a> wrote:<br>
</div>
<blockquote type="cite">
<pre>Subject: Re: [chirp_users] Hesenate vhf/uhf
To: <a class="m_-3435214941004281498moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.<wbr>danplanet.com</a>
Message-ID: <a class="m_-3435214941004281498moz-txt-link-rfc2396E" href="mailto:15fff22b39a-171e-13cb3@webjas-vaa246.srv.aolmail.net" target="_blank"><15fff22b39a-171e-13cb3@<wbr>webjas-vaa246.srv.aolmail.net></a>
Content-Type: text/plain; charset="utf-8"
shows error under other devices usb port no drivers available. I will have to find a driver for the cable.
Ray</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to amnon at <a href="mailto:amnon.zohar@gmail.com">amnon.zohar@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Amnon</div>
</div>