Okay, I gave it a try. No joy, with either the FT-60 or FT-8800. Same "bad cable?" error. I have to go back to 2013-10-27 to find a build that doesn't generate this error.
Basil KE5GAE
On Fri, Jan 31, 2014 at 2:13 PM, Milton Hywatt mhywattt@yahoo.com wrote:
There was a new build notification in my mail box today. Give that a try.
*From:* Basil Copeland blcjr2@gmail.com *To:* hewat@freenetname.co.uk; Discussion of CHIRP < chirp_users@intrepid.danplanet.com> *Sent:* Friday, January 31, 2014 11:43 AM
*Subject:* Re: [chirp_users] Chirp & FT-8800
Are you using Windows? In another thread, Jen seems to have narrowed the problem down to a change made in the 2013-10-31 build, that seems to affect only Windows, not Linux.
Basil KE5GAE
On Fri, Jan 31, 2014 at 3:01 AM, Andy hewat@freenetname.co.uk wrote:
I've been using the latest build for programming the FT-8800 over the last two weeks. No problem at all. For windows the only issue I've ever had is drivers being updated automatically for the programming cable. Do not allow Windows to do this!
Regards, Andy - G8NTH
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users