[chirp_users] I had a driver, then I lost it. (Mac OS issue)

Thu Jul 26 15:12:15 PDT 2018

Dennis.  With due respect, no, I don’t have to do any homework.  Using the USB cables I have, windows update NEVER screws with the cable drivers.  N-E-V-E-R.  I have several different cables, I think three cables for Yaesu and two for Icom, and only one cable for Wouxun.  All cables by RT-Systems.  All the cables use the exact same driver.  The driver is written by RT-Systems specifically for their cables.  Windows does not touch that driver.  As I mentioned earlier, I just moved platforms here, from Win-7 to Win-10.  I downloaded a fresh driver from RT-Systems, and it worked first time I plugged it in.  The only “difficulty” was figuring out which comm-port it was assigned to when I plugged in the various cables.

The cable DRIVER issue is only for those folks who take the route that leads them to the cloned chipset troubles.  And it is up to them to “do their homework”.  Each can decide if their time is worth the frustration and the few $$$$ saved with the cheaper cables.  I don’t need to program my radios often.  When I do, I just want it to work.  I don’t want to find out something broke and now I have to spend time figuring out what broke.  I don’t want to waste time “rolling back” until it works again.  I want to program the radio and get on with my project.  That is worth the extra cost of the cables to me.  That value may not apply to all, and that is fine.  It’s a personal choice after all.

For anyone interested in investigating RT-Systems cables after reading this, sign up for their newsletter.  Periodically they have sales, and you can save a few $$$ buying during the sale.

NOTE:  I have no connection with RT-Systems in any way.  I will not make a penny if you buy 100 cables.  I am just a satisfied customer.  Very satisfied since the Win-10 upgrade went so perfectly with that part of the changeover.  I just want it to work.  And it does.  Every time I plug in a cable - it works.  Looking forward to several years of painless use on Win-10 now.

Vy73 – Mike – KD5KC

El Paso, Texas – DM61rt

From: chirp_users-bounces at intrepid.danplanet.com <chirp_users-bounces at intrepid.danplanet.com> On Behalf Of Dennis Wage
Sent: Thursday, July 26, 2018 7:25 AM
To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
Subject: Re: [chirp_users] I had a driver, then I lost it. (Mac OS issue)

I have 3 cables. One I bought. The other two came in a box of stuff I bought.

On Windows 10 in Device Manager

#1 is recognized as:

With this driver:

These driver files:

------------------------------------------------------------------------

#2 is recognized as:

With this driver:

These driver files:

------------------------------------------------------------------------

#3 is recognized as:

With this driver:

These driver files:

They all work, you just have to do YOUR homework and install the right drivers.

Dennis M. Wage (W9BOQ)

245 Corum Hill Road

Castalian Springs, TN 37031

(615) 310-4242 Cell

(615) 562-5128 Home
 <http://hammondb3organ.net/> http://hammondb3organ.net

 <http://overdubs.net> http://overdubs.net

On Thu, Jul 26, 2018 at 7:38 AM, <mike-2007 at elp.rr.com <mailto:mike-2007 at elp.rr.com> > wrote:

My only suggestion, get a known good OEM cable, and never worry about the driver or an update again.  But that's just me.  Others seem to enjoy the challenge, I just want it to work when I need it.

Vy73 – Mike – KD5KC
El Paso, Texas – DM61rt

-----Original Message-----
From: chirp_users-bounces at intrepid.danplanet.com <mailto:chirp_users-bounces at intrepid.danplanet.com>  <chirp_users-bounces at intrepid.danplanet.com <mailto:chirp_users-bounces at intrepid.danplanet.com> > On Behalf Of T.E. Klamberg Klamberg via chirp_users
Sent: Wednesday, July 25, 2018 8:51 PM
To: chirp_users <chirp_users at intrepid.danplanet.com <mailto:chirp_users at intrepid.danplanet.com> >
Subject: [chirp_users] I had a driver, then I lost it. (Mac OS issue)

I had installed the driver for a USB cable from Valley Enterprise for my Yaesu FT-60. Three installs and it (Mac) finally recognized the driver and cable. That was six months back.
I acquired another cable for my Yaesu FT-29 2m radio. I must have got an OS update (High Sierra OS, version 10.13.6) that I cannot call up the drivers for either one (it should be only one driver upgrade). I haven’t even got to the part of trying to get Chirp to frustrate me!
I know there are folks out there that have more computer smarts than I, especially when it comes to Mac. Anyone have any ideas, short of becoming a programmer?
Thanks.

Tip
N9MVX
Mascoutah, IL
_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com <mailto:chirp_users at intrepid.danplanet.com> 
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to mike-2007 at elp.rr.com <mailto:mike-2007 at elp.rr.com>  at mike-2007 at elp.rr.com <mailto:mike-2007 at elp.rr.com>  To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com <mailto:chirp_users-unsubscribe at intrepid.danplanet.com> 

_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com <mailto:chirp_users at intrepid.danplanet.com> 
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Dennis Wage at dwage at dwage.com <mailto:dwage at dwage.com> 
To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com <mailto:chirp_users-unsubscribe at intrepid.danplanet.com> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1682 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2916 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0001.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4173 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1798 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0003.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2925 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0004.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2938 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 1693 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0006.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2992 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0007.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2924 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180726/66042fef/attachment-0008.png 