[chirp_users] Help needed, can't write to Yaesu FT-60

[chirp.cordless at xoxy.net]

I think we're in agreement. After trying three different drivers,
and at least two of them working for other folks, and no debug
tools immediately available, I think another cable is the most
reasonable / expeditious thing to try. Grumble...

Ordered one from Kawamall half an hour ago. I thought about
getting one with a different (FTDI) chip, but everyone else seems to
get Prolific cables to work, so I'll try this first.

Booting into linux to program my radio is not where I want to end up.
If the cable doesn't fix it, I'll give it some further thought.

No $1 bet, I'm betting "bad cable" too. I will post results.

Thanks and regards,

-dan

On Sep 22, 2012, at 5:18 PM, D.J.J. Ring Jr. - n1ea at arrl.net <+chirp+cordless+7d3f38247a.n1ea#arrl.net at spamgourmet.com> wrote:
> Right about now, I'd either use another computer in the household or as I mentioned before, use a Ubuntu Live CD which was written for Mac then install CHIRP to it and try that Operating System.
> 
> It's not CHIRP, it 'might be the driver' but that's looking "not so much", on Linux I would guess it would be permissions and user groups, but I suspect you have a bad cable.  Low budget shops usually don't have the automated testing facilities they need to make sure stuff works and still sell it at a low price.  They probably spot test a batch, not each one.
> 
> I'd go to a friend's house with radio, cable and load CHIRP onto their computer.  Certainly a family member has a computer or a friend?
> 
> I bet a buck on "bad cable".
> 
> 73
> 
> DR