[chirp_users] R: chirp_users Digest, Vol 71, Issue 22

y_61 at libero.it
Mon Dec 1 11:35:48 PST 2014



i use this cable with windows xp for  4-5 months and work very well !!!

i NOT update the driver, and not update by windows !

why NOW not work my cable?


with CHIRP and  linux  it say error no2 ... what is ?

in how mode i TEST in windows or  CHIRP  linux if the cable porgramming is 
good 

or fault ???    

73



>----Messaggio originale----
>Da: chirp_users-request at intrepid.danplanet.com
>Data: 30-nov-2014 21.00
>A: <chirp_users at intrepid.danplanet.com>
>Ogg: chirp_users Digest, Vol 71, Issue 22
>
>Send chirp_users mailing list submissions to
>	chirp_users at intrepid.danplanet.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>or, via email, send a message with subject or body 'help' to
>	chirp_users-request at intrepid.danplanet.com
>
>You can reach the person managing the list at
>	chirp_users-owner at intrepid.danplanet.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of chirp_users digest..."
>
>
>Today's Topics:
>
>   1. Re: chirp_users Digest, Vol 71, Issue 21 (Bob Fk)
>   2. Re: chirp_users Digest, Vol 71, Issue 21 (Dennis Smith)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sun, 30 Nov 2014 11:01:32 +1100
>From: Bob Fk <vk2byf at gmail.com>
>Subject: Re: [chirp_users] chirp_users Digest, Vol 71, Issue 21
>To: "chirp_users at intrepid.danplanet.com"
>	<chirp_users at intrepid.danplanet.com>
>Message-ID:
>	<CAN=fXRthw8cU9_XiWqJ-pin0hxmzP7FvQg9UB34ipbuXze8r1A at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>RE: IS IT MY CABLE OR MY TVR?
>
>Most Problems with Chirp are a problem with the USB cable driver.
>Use the driver which came with the cable.
>Do NOT allow Windows to update the USB driver when you plug in the
>USB cable and Windows loads the USB driver.
>
>This is an attempt by Microsoft to stop people using cloned USB cables.
>
>73 Bob VK2BYF
>
>On 30 November 2014 at 07:00, <chirp_users-request at intrepid.danplanet.com>
>wrote:
>
>> Send chirp_users mailing list submissions to
>>         chirp_users at intrepid.danplanet.com
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> or, via email, send a message with subject or body 'help' to
>>         chirp_users-request at intrepid.danplanet.com
>>
>> You can reach the person managing the list at
>>         chirp_users-owner at intrepid.danplanet.com
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of chirp_users digest..."
>>
>> Today's Topics:
>>
>>    1. chirp linux and cable to programm (y_61 at libero.it)
>>
>>
>> ---------- Forwarded message ----------
>> From: "y_61 at libero.it" <y_61 at libero.it>
>> To: chirp_users at intrepid.danplanet.com
>> Cc:
>> Date: Sat, 29 Nov 2014 15:32:32 +0100 (CET)
>> Subject: [chirp_users] chirp linux and cable to programm
>>
>> hi,
>>
>> my cable to programm baofeng uv-5R not work or is fault my rtx uv-5r ?
>>
>> in how mode i test is faut the rtx or the cable ????
>>
>>
>>
>> i create the *CHIRP  cd-live on usb boot pen...*. but if i download to
>> rtx it say ERROR no 2.... what is ?
>>
>> in how mode i TEST the cable is not dead ???
>>
>>
>> best 73
>>
>>
>>
>>
>>
>> i try to connect  th cable via  *CHIRP CD LIVE*  (linux ?)  and I think
>> the cable is recognized?
>>
>>
>>
>> but I not very shure it is effectly recognized ?there isn?t a TEST  to
>> know this ?
>>
>>
>>
>> I open CHIRP  and select ?downolad?  is  say this :
>>
>>
>>
>> AN ERROR HS OCCURRED   and :
>>
>>
>>
>> Could open  Port/dev/ttyUSB0    [ ERRORno2 ]
>>
>>
>>
>> No  file or directory /dev/ttyusb0
>>
>>
>>
>>
>>
>> ?..is correct  that use this  TTYUSB0  ? the others ports is not  called
>> ?usb? ?.
>>
>>
>>
>> And  what is this ERROR no 2  ?
>>
>>
>>
>> Is  FAULT and dead  my usb cable or my  rtx UV-5R ?
>>
>>
>>
>> Thanks very muche for help me, best 73
>>
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>>
>
>
>-- 
>*The miracle of life is that it exists despite everything it's got going
>against it.*
>*Bob *
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://intrepid.danplanet.
com/pipermail/chirp_users/attachments/20141130/86abc43e/attachment-0001.html 
>
>------------------------------
>
>Message: 2
>Date: Sun, 30 Nov 2014 00:28:49 +0000
>From: Dennis Smith <m1dlguk at gmail.com>
>Subject: Re: [chirp_users] chirp_users Digest, Vol 71, Issue 21
>To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
>Message-ID:
>	<CANn6+eK=mRRVaUNCLuy3DsQ_qXLtvhGf6J2FC3_QYLC5sbvoHA at mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Microsoft has nothing to gain from doing what you suggest. What you
>refer to incorrectly relates to drivers provided by FTDI of recent,
>and from Prolific last year as a method to combat counterfeit chips as
>they call it. Prolific have made there drivers capable of identifying
>the illicit IC's and will not allow them to run on those PC's. FTDI
>can also identify the IC's that work equally as well as their own but
>are also identifying themselves as FTDI's when they are not so a few
>months back FTDI updated their drivers to corrupt the IC and
>effectively bricking them. The PR following this move caused FTDI to
>revoke those drivers and now they don't brick any more, they just
>refuse to work instead. The drivers provided by Windows update are
>uploaded by FTDI or Prolific or whatever company has paid to have a
>VID and PID number attached to their chips, and not usually provided
>by Microsoft directly. Microsoft was not happy with the actions of
>FTDI because of the bad PR and the idea that M$ allowed rogue drivers
>to damage hardware on it's network.
>
>Whilst you are right, the best drivers in this instance is not the
>Windows update drivers, the reason isn't the one you gave. There is a
>small possibility the bricking drivers are floating the internet and
>may be installed in error and these can deliberately damage your
>cable, but this is a 0.01% chance because no one would want these
>drivers to float about in the wild if they could help it.
>
>If you do install newer drivers than you want, or possibly corrupted
>drivers then you should go to hardware manager and uninstall and
>delete the newer ones before forcing the older ones to run.
>
>Dennis Smith
>M1DLG
>
>On 30 November 2014 at 00:01, Bob Fk <vk2byf at gmail.com> wrote:
>> RE: IS IT MY CABLE OR MY TVR?
>>
>> Most Problems with Chirp are a problem with the USB cable driver.
>> Use the driver which came with the cable.
>> Do NOT allow Windows to update the USB driver when you plug in the
>> USB cable and Windows loads the USB driver.
>>
>> This is an attempt by Microsoft to stop people using cloned USB cables.
>>
>> 73 Bob VK2BYF
>>
>> On 30 November 2014 at 07:00, <chirp_users-request at intrepid.danplanet.com>
>> wrote:
>>>
>>> Send chirp_users mailing list submissions to
>>>         chirp_users at intrepid.danplanet.com
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>         http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> or, via email, send a message with subject or body 'help' to
>>>         chirp_users-request at intrepid.danplanet.com
>>>
>>> You can reach the person managing the list at
>>>         chirp_users-owner at intrepid.danplanet.com
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of chirp_users digest..."
>>>
>>> Today's Topics:
>>>
>>>    1. chirp linux and cable to programm (y_61 at libero.it)
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: "y_61 at libero.it" <y_61 at libero.it>
>>> To: chirp_users at intrepid.danplanet.com
>>> Cc:
>>> Date: Sat, 29 Nov 2014 15:32:32 +0100 (CET)
>>> Subject: [chirp_users] chirp linux and cable to programm
>>>
>>> hi,
>>>
>>> my cable to programm baofeng uv-5R not work or is fault my rtx uv-5r ?
>>>
>>> in how mode i test is faut the rtx or the cable ????
>>>
>>>
>>>
>>> i create the CHIRP  cd-live on usb boot pen.... but if i download to rtx
>>> it say ERROR no 2.... what is ?
>>>
>>> in how mode i TEST the cable is not dead ???
>>>
>>>
>>> best 73
>>>
>>>
>>>
>>>
>>>
>>> i try to connect  th cable via  CHIRP CD LIVE  (linux ?)  and I think the
>>> cable is recognized?
>>>
>>>
>>>
>>> but I not very shure it is effectly recognized ?there isn?t a TEST  to
>>> know this ?
>>>
>>>
>>>
>>> I open CHIRP  and select ?downolad?  is  say this :
>>>
>>>
>>>
>>> AN ERROR HS OCCURRED   and :
>>>
>>>
>>>
>>> Could open  Port/dev/ttyUSB0    [ ERRORno2 ]
>>>
>>>
>>>
>>> No  file or directory /dev/ttyusb0
>>>
>>>
>>>
>>>
>>>
>>> ?..is correct  that use this  TTYUSB0  ? the others ports is not  called
>>> ?usb? ?.
>>>
>>>
>>>
>>> And  what is this ERROR no 2  ?
>>>
>>>
>>>
>>> Is  FAULT and dead  my usb cable or my  rtx UV-5R ?
>>>
>>>
>>>
>>> Thanks very muche for help me, best 73
>>>
>>>
>>>
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>
>>
>>
>>
>> --
>> The miracle of life is that it exists despite everything it's got going
>> against it.
>> Bob
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>
>
>
>------------------------------
>
>_______________________________________________
>chirp_users mailing list
>chirp_users at intrepid.danplanet.com
>http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
>End of chirp_users Digest, Vol 71, Issue 22
>*******************************************
>





More information about the chirp_users mailing list