NOTE: RTSystems has recently been shipping cables intentionally handicapped to prevent their use with third party software, and to prevent use of third party cables with their software. Beware that if you buy their software/cable package, you will not be able to use their cables with CHIRP!

That is just pure mean spirited.  Why should anyone sell a cable that is intentionally buggered so it doesn't work with other types of software.

That's almost evil.

DR 
David J. Ring, Jr., N1EA  Radio-Officers Group -- Join CW email list -- Historic Morse Recordings 
Gopher Hole:  gopher://sdf.org/1/users/djringjr/ (native or with Firefox's Overbite extension) or via http to gopher gateway
Chat Skype: djringjr MSN: djringjr@msn.com AIM: N1EA icq: 27380609

=30=



On Fri, Sep 28, 2012 at 5:55 PM, Robert Terzi <rct@r-t.org> wrote:
On 9/28/2012 5:12 PM, Tom Hayward wrote:>
> It sounds to me like you got bit by the Prolific drivers and possibly
> counterfeit Prolific chips (seems to be about 90% of the topics on
> this mailing list).

Unfortunately, it seems like it's almost every ham group that I read has
this on-going saga.

In case it helps any one else, Valley Enterprises is in the process of
converting all the cables they sell to be FTDI based.  Their site generally
mentions FTDI and Windows 7 in the description of the cable so you can tell
what you are ordering.  They are also available through Amazon.

I added a link to Chirp's Cable Guide on the Wiki:
http://chirp.danplanet.com/projects/chirp/wiki/CableGuide








_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users