[chirp_users] Windows 8
kd4tjx at yahoo.com
Mon Feb 10 09:33:07 PST 2014
OT for anyone who is interested…
there is no drm, per-se.. it's simply a few extra ways that genuine pl2303 chips respond differently compared to the copies.
It's been known for some time, plus a simple decompilation and trace through the driver code shows what is causing the issue…
Here is a few year old blog post that explains some of the differences ;)
If it weren't for the fact that the workaround is so simple (use older version) with no appreciable loss of features, someone might be inclined to package a modified driver ;)
Actually I'm quite surprised the counterfeiters havent modified the chips to react the same as genuine chips. Probably a combination of factors (mainly that old drivers work fine ;)
From: "Nigel Johnson, MIEEE" <nw.johnson at ieee.org>
To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
Sent: Monday, February 10, 2014 7:49 AM
Subject: Re: [chirp_users] Windows 8
-----BEGIN PGP SIGNED MESSAGE-----
Or you could use linux, Mike. The day that prolific publishes the source code for its DRM function is the day that the counterfeiters will change their design to get around it!
73 de Nigel ve3id
On 02/10/2014 08:42 AM, Michael Walker wrote:
> I also believe that the current FTDI chipset will remember its com port
> number even if you plug it into a different USB port which is nice and you
> aren't plugging the cable in only to tell you it is Com54. :) Hence the
> reason you might want to clean up your old ports with what I sent earlier.
> It is hard to solve if you only get the USB to radio programming cable and
> you have no choice but to back rev their driver.
> If you go for the RS232 to radio programming cable, then you do have the
> option of using a USB certified RS232 port. Going back to the RS232 (DB9
> connector) is my failsafe that always works.
> Mike va3mw
> On Mon, Feb 10, 2014 at 6:06 AM, Jim Unroe <rock.unroe at gmail.com> wrote:
>> On Mon, Feb 10, 2014 at 12:00 AM, kc6iih <kc6iih at aol.com> wrote:
>>> The exclamation mark means you have a conflict. Fix your port settings.
>>> Jock KC6IIH
>> You are partially correct.
>> The exclamation mark is because there is a conflict with the driver and
>> the chip in the programming cable.
>> Most inexpensive programming cables have an unauthorized copy of
>> Prolific's USB-to-Serial chip in them. These copied chips use the same
>> Prolific driver that the genuine Prolific chips require. Prolific
>> eventually changed their drivers after v22.214.171.124 to not function (hence
>> the error) with the unauthorized copies.
>> Windows Vista and newer (ie: 7, 8 & 8.1), will automatically install the
>> latest driver when a USB cable with a Prolific type chip is plugged into a
>> USB port that doesn't already have a driver configured. If the cable has an
>> unauthorized chip, the driver installation is guaranteed to fail.
>> The only fix that will eliminate the conflict with an unauthorized
>> Prolific chip is to downgrade the driver to at least v126.96.36.199. Some of
>> the Chinese programming software have a conflict with the v188.8.131.52 or
>> v184.108.40.206 Prolific driver versions (CHIRP has no such issues and runs
>> fine) so the general recommendation is to downgrade to the v220.127.116.11 driver.
>> Windows XP does not automatically install the latest driver, but is
>> recommended that v18.104.22.168 is the driver version to install to avoid a
>> conflict with an unauthorized copy of the Prolific chip.
>> Other solutions would be to purchase and use a programming cable with
>> genuine Prolific chip or a programming cable with another brand of chip
>> (FTDI for example).
>> Jim KC9HI
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
Amateur Radio, the origin of the open-source concept!
You can reach me by voice on Skype: TILBURY2591
If time travel ever will be possible, it already is. Ask me again yesterday
This e-mail is not and cannot, by its nature, be confidential. En route from me to you, it will pass across the public Internet, easily readable by any number of system administrators along the way.
Nigel Johnson <nw.johnson at ieee.org>
Please consider the environment when deciding if you really need to print this message
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
chirp_users mailing list
chirp_users at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users