<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
As documented in my original post, the OS is LINUX MINT 12 -- not
Ubuntu. <br>
<br>
If the directions on the webpage that says how to get the daily
build are incorrect, shouldn't they be updated? <br>
<br>
The DB9 serial cable was purchased from Yaesu and is specifically
made for this radio. This cable worked fine when programming the
FT-60 using the same laptop, with Windows XP Professional and the
3rd party programming software supplied by Yaesu. The cable and rig
have not changed in any way. I don't suspect any fault with the
cable.<br>
<br>
I will try the real daily build when I find the energy. <br>
<br>
Thanks,<br>
Marcia NU6N<br>
<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 05/27/2013 10:39 AM, Dan Smith
wrote:<br>
</div>
<blockquote cite="mid:20130527103913.03e0d348@theine.danplanet.com"
type="cite">
<blockquote type="cite">
<pre wrap="">I see you are receiving the 15 March build when using apt-get. Don't
use apt-get, go directly to this web page
<a class="moz-txt-link-freetext" href="http://trac.chirp.danplanet.com/chirp_daily/LATEST/">http://trac.chirp.danplanet.com/chirp_daily/LATEST/</a> and download the
tar.gz file. That will get you the 24 May build - or later if it gets
updated before you get around to downloading. Run the chirpw file from
the directory created when you unpack the daily build, not the one
in /usr/bin.
</pre>
</blockquote>
<pre wrap="">
The reason she's getting the older build is because she's running an
old and unsupported version of Ubuntu (Oneiric 11.10). Using the PPA
(via apt-get) _is_ the proper and preferred way for Ubuntu users to
receive the builds.
</pre>
<blockquote type="cite">
<pre wrap="">If you still get a failure, at least you can say you've
tried the latest build.
</pre>
</blockquote>
<pre wrap="">
Nothing has changed in the FT-60 driver or supporting code in a very
long time, so I do not expect any difference by upgrading to the latest
version. I expect that the problem is, as others have noted, related to
the cable and/or USB hardware being used here.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
chirp_users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a>
<a class="moz-txt-link-freetext" href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a>
</pre>
</blockquote>
<br>
</body>
</html>